Closed
Bug 1201611
Opened 10 years ago
Closed 10 years ago
Possible improvements for Push FAQ page
Categories
(www.mozilla.org :: Pages & Content, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Coce, Assigned: pascalc)
References
()
Details
Attachments
(1 file)
As per the exchange here <https://groups.google.com/forum/#!topic/mozilla.dev.l10n.web/coVwWCauQHk> there are two possible improvements to the Push FAQ page:
(1)
> On Firefox for desktop, the push service is operated by Mozilla. Firefox uses the same Google Cloud Messaging platform and infrastructure that your other Android applications use.
The second sentence refers to Firefox for Android. Possibly the sentence should specifically mention that (e.g. „Firefox for Android uses the same […]“).
(2)
> Set the Receive Push Notifications to Block. The site will not be able to send you messages or ask for access to Push.
This section refers to completely disabling the said feature, yet it refers to „the site“ (singular). If it said „Websites will not/no longer be able […]“ it might be clearer that this action refers to all websites.
Thanks for considering.
Comment 1•10 years ago
|
||
CC'ing Martin Thomson.
Comment 2•10 years ago
|
||
These are good. Thanks.
| Assignee | ||
Comment 3•10 years ago
|
||
Attachment #8656763 -
Flags: review?(agibson)
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → pascalc
Comment 4•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/bedrock
https://github.com/mozilla/bedrock/commit/7420718eb954b2bbc0b352f889ce7b472a3e94e4
Bug 1201611: wording improvements for Push FAQ page
https://github.com/mozilla/bedrock/commit/c4d18787a8e3eed46986072508f0c09bfc9d2944
Merge pull request #3279 from pascalchevrel/bug1201611_pushFAQ_wording_change
Bug 1201611: wording improvements for Push FAQ page
Updated•10 years ago
|
Attachment #8656763 -
Flags: review?(agibson) → review+
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 5•10 years ago
|
||
Thank you!
You need to log in
before you can comment on or make changes to this bug.
Description
•