Add the mobile-web-app-capable meta tag to the website's PWA configuration
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- web-dev
Research direction
Open website/docusaurus.config.ts and find the existing apple-mobile-web-app-capable meta tag. Add the standard mobile-web-app-capable tag with content: 'yes' alongside it, then build or run the website and inspect the page source or Chrome console. Done when both tags are present and the deprecation warning is gone.
Written by the indexing model from the issue text.
Description
Have you read the Contributing Guidelines on issues?
- I have read the Contributing Guidelines on issues.
Prerequisites
- I'm using the latest version of Docusaurus.
- I have tried the
npm run clearoryarn clearcommand. - I have tried
rm -rf node_modules yarn.lock package-lock.jsonand re-installing packages. - I have tried creating a repro with https://new.docusaurus.io.
- I have read the console error message carefully (if applicable).
Description
Description
The Docusaurus website's PWA configuration includes the apple-mobile-web-app-capable meta tag, which triggers a deprecation warning in Chrome.
The browser console reports:
(index):1 <meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes">
The existing configuration is in website/docusaurus.config.ts and includes the Apple-specific meta tag with content: 'yes'.
Adding the standard mobile-web-app-capable meta tag alongside the existing Apple-specific tag may resolve this warning while preserving compatibility with Apple devices.
I would be happy to investigate and implement this change if the maintainers consider it appropriate.
Reproducible demo
Steps to reproduce
- Visit https://docusaurus.io/.
- Open Chrome Developer Tools.
- Select the Console tab.
- Reload the page.
- Observe the deprecation warning for
apple-mobile-web-app-capable.
Expected behavior
The website should include the standard mobile-web-app-capable meta tag with content="yes" alongside the Apple-specific tag, if retaining both is appropriate, so that Chrome no longer reports this deprecation warning.
Actual behavior
Chrome displays the following warning in the browser console:
<meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes">
Your environment
- Public source code: https://github.com/facebook/docusaurus
- Public site URL: https://docusaurus.io/
- Docusaurus version used: Not verified
- Environment name and version (e.g. Chrome 89, Node.js 16.4): Google Chrome (exact version not recorded)
- Operating system and version (e.g. Ubuntu 20.04.2 LTS): macOS (exact version not recorded)
Self-service
- I'd be willing to fix this bug myself.
- Dominant language
- TypeScript
- Stars
- 66.5k
- Forks
- 10.1k
- Avg merge
- 23h 6m
- Merged PRs (30d)
- 159
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from facebook/docusaurus
-
Playground cards have inconsistent heightsPossibly taken A pull request linked to this issue is open or already merged. Openbug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facebook/docusaurus#12739 · 1 comment ·
Maintainers usually reply within 1 day
-
Page title drops a trailing # from the heading, e.g. # Learn C# becomes "Learn C" (AI-assisted)Possibly taken @lx3133584 claimed this 7 days ago. Openbug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facebook/docusaurus#12644 · 1 comment ·
Maintainers usually reply within 1 day
-
docusaurus serve: static assets 404 when baseUrl is not "/" and trailingSlash is truePossibly taken @Shashank01729 claimed this 28 days ago. Openbug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
facebook/docusaurus#12476 · 4 comments ·
Maintainers usually reply within 1 day
-
Firefox clips descenders in documentation sidebar labels on WindowsPossibly taken @xusnitdinov claimed this 95 days ago. Openbug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
facebook/docusaurus#12299 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
facebook/docusaurus#10490 · 10 comments · 5 reactions ·
Maintainers usually reply within 1 day
All issues in facebook/docusaurus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
paperclipai/paperclip#17151 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
AgoraIO-Extensions/agent-infra#3159 ·
Maintainers usually reply within 1 day
-
blocklist addition
Difficulty 1/5 Under an hour Newbie friendliness 66/100
MetaMask/eth-phishing-detect#304596 ·
Maintainers usually reply within 1 day
-
friction
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
kentcdodds/kody#4142 ·
-
[Bug] Statistics | Task statistics are always empty on MikroORM with MySQL or SQLitePossibly taken @NdekoCode claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ever-co/ever-gauzy#11214 ·
Maintainers usually reply within 1 day