Need to create a WebXR permission info page
Categories
(Core :: WebVR, task, P2)
Tracking
()
People
(Reporter: kip, Unassigned)
References
Details
We will need to create and deploy a WebXR permission info page to be linked from the WebXR permission prompt. This would be similar to the page used for the geolocation api:
https://www.mozilla.org/en-US/firefox/geolocation/
The new page would be at the URL:
https://www.mozilla.org/%LOCALE%/firefox/webxr/
Where %LOCALE% is sensitive to the locale, for example:
https://www.mozilla.org/en_US/firefox/webxr/
This URL will be configurable by a pref:
browser.xr.warning.infoURL
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
Please note that the permission UI has landed, with the link formatted as described.
SUMO page created here: https://support.mozilla.org/kb/webxr-permission-info-page. It's currently hidden from search. Let us know when you'd like to make it public.
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to Joni Chan from comment #2)
SUMO page created here: https://support.mozilla.org/kb/webxr-permission-info-page. It's currently hidden from search. Let us know when you'd like to make it public.
This page looks great, thanks to everyone for putting it together!
Would it be possible to make the page public, at the URL linked in the Firefox UI?
https://www.mozilla.org/en_US/firefox/webxr/
Hi @kip, we don't manage the mozilla.org pages and are unable to redirect from there. Not sure who owns the content there now. Maybe Meridel Walkington would know?
Comment 6•5 years ago
|
||
(In reply to Joni Chan from comment #2)
SUMO page created here: https://support.mozilla.org/kb/webxr-permission-info-page. It's currently hidden from search. Let us know when you'd like to make it public.
I made some edits to the article, marked it ready to localize and made it public. Joni, please take a look in case other edits are needed,
I looked over and it looks good. Thanks, Alice.
Comment 8•5 years ago
|
||
Would it be possible to make the page public, at the URL linked in the Firefox UI?
https://www.mozilla.org/en_US/firefox/webxr/
If you click the geolocation page link in comment 0, you'll see it redirects to SUMO. SUMO is purpose-built to deliver this kind of content in a durable, maintainable way[0], while the marketing website has different work to do, generally. So we moved the geolocation page and most others like it to SUMO some time ago.
We maintain a redirect for it, because the original link was out in the wild already in all those old clients. It looks like the XR URL is out there in the wild now, too. Is it in a pre-release version or the release channel?
- If in pre-release, we should change the URL in product to the SUMO URL Joni provided in comment 2 before release.
- If it is in release, we will have to build another redirect on www to redirect users to the SUMO content. Anyone can file an issue to do so at https://github.com/mozilla/bedrock/issues/new?template=bug_report.md.
[0] E.g. building this content on SUMO does not require a design process; a taxonomy decision; or any custom coding; which means leaving it on SUMO does not create nearly as much content, brand, and technical debt as designing, copywriting and coding a new marketing page does. SUMO is the right tool for this job.
Comment 9•5 years ago
|
||
In the bug report at https://bugzilla.mozilla.org/show_bug.cgi?id=1606238 the user's browser is listed as Fx73, so it looks like this is in the wild, in release.
I filed https://github.com/mozilla/bedrock/issues/8596 for the redirect.
Updated•5 years ago
|
Reporter | ||
Comment 10•5 years ago
|
||
Would we like to update the link in the dialogue to point directly to SUMO and let this ride the train to release later? Or should we just leave the redirect up like for Geolocation prompts?
Comment 11•5 years ago
|
||
If we can update the link to point at SUMO in future releases, we'll minimize the need for an eternal redirect. I filed bug 1618310 to that end.
Reporter | ||
Comment 12•5 years ago
|
||
Excellent, thanks! I'll close this bug and follow up in Bug 1618310 with a patch to change the link.
Reporter | ||
Updated•5 years ago
|
Description
•