Closed Bug 1476889 Opened 6 years ago Closed 6 years ago

Update autoplay exceptions copy

Categories

(Firefox :: Settings UI, defect, P1)

defect

Tracking

()

VERIFIED FIXED
Firefox 63
Tracking Status
firefox63 --- verified

People

(Reporter: daleharvey, Assigned: daleharvey)

References

Details

Attachments

(1 file)

The copy for the autoplay exceptions dialog needs updated
Assignee: nobody → dharvey
Bryant if you could update here when you get it, thanks
Flags: needinfo?(bmao)
You mean the dialog in about:preferences, right?
Component: Site Identity and Permission Panels → Preferences
Yup, cheers
(In reply to Dale Harvey (:daleharvey) from comment #1) > Bryant if you could update here when you get it, thanks Sure, below is the updated copy For exception dialog https://mozilla.invisionapp.com/share/N2MD6ZV8CMG#/306583373_6-3 1.Description: "You can specify which websites are always or never allowed to autoplay media with sound. Type the address of the site you want to manage and then click Block or Allow." 2.Buttons below the address bar: [Block] [Allow] 3.Website status: [Block] or [Allow] For global settings https://mozilla.invisionapp.com/share/N2MD6ZV8CMG#/306583372_6-2 1.Combo box: [Allow Autoplay] or [Always Ask] or [Don't Autoplay]
Flags: needinfo?(bmao)
Flod, in the above spec those strings are being changed to "Allow Autoplay" | "Dont allow" https://mozilla.invisionapp.com/share/N2MD6ZV8CMG#/screens/306583371 From your comment in 1477231 would Allow | Dont allow be better (same as webrtc), the other uses of autoplay dont have the same size issues as far as I can tell
Flags: needinfo?(francesco.lodolo)
(In reply to Dale Harvey (:daleharvey) from comment #6) > From your comment in 1477231 would Allow | Dont allow be better (same as > webrtc), the other uses of autoplay dont have the same size issues as far as > I can tell Likely yes, since there's no "autoplay". But IMO we should also fix the underlying layout issue, which is letting the button label wrap.
Flags: needinfo?(francesco.lodolo)
Hey Bryant, could you confirm with the copywriter that |Allow| |Don't Allow| would be suitable for the doorhanger buttons @ https://mozilla.invisionapp.com/share/N2MD6ZV8CMG#/screens/306583371 Cheers
Flags: needinfo?(bmao)
Priority: -- → P1
So as far as I can tell we cant actually wrap text here since its inside a xul:button, we could replace the fact they are buttons but that would be a bigger change and dont allow | allow is consistent with other uses of the doorhanger so I dont think its a large problem
Comment on attachment 8994162 [details] Bug 1476889 - Update autoplay copy. https://reviewboard.mozilla.org/r/258774/#review265654 Unfortunately all string IDs need to change at this point https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_content_best_practices#Changing_existing_strings ::: browser/locales/en-US/browser/preferences/permissions.ftl:104 (Diff revision 1) > ## Exceptions - Autoplay Media > > permissions-exceptions-autoplay-media-window = > .title = Allowed Websites - Autoplay > .style = { permissions-window.style } > -permissions-exceptions-autoplay-media-desc = You can specify which websites are allowed to automatically play media elements. Type the exact address of the site you want to allow and then click Allow. > +permissions-exceptions-autoplay-media-desc = You can specify which websites are always or never allowed to autoplay media with sound. Type the address of the site you want to manage and then click Block or Allow. Need a new ID. I guess permissions-exceptions-autoplay-media-desc would work here. ::: browser/locales/en-US/browser/preferences/preferences.ftl:857 (Diff revision 1) > > autoplay-option-ask = > .label = Always Ask > autoplay-option-allow = > .label = Allow Autoplay > autoplay-option-block = Need a new ID: autoplay-option-dont seems to work ::: browser/locales/en-US/chrome/browser/browser.properties:962 (Diff revision 1) > midi.shareSysexWithFile.message = Will you allow this local file to access your MIDI devices and send/receive SysEx messages? > # LOCALIZATION NOTE (midi.shareSysexWithSite.message): %S is the name of the site URL (https://...) requesting MIDI access > midi.shareSysexWithSite.message = Will you allow %S to access your MIDI devices and send/receive SysEx messages? > > -autoplay.Allow.label = Allow Autoplay > +autoplay.Allow.label = Allow > autoplay.Allow.accesskey = A Both label and accesskey need a new ID, e.g. autoplay.Allow2.label and autoplay.Allow2.accesskey
Attachment #8994162 - Flags: review?(francesco.lodolo) → review-
(In reply to Francesco Lodolo [:flod] from comment #11) > ::: browser/locales/en-US/browser/preferences/permissions.ftl:104 > (Diff revision 1) > > ## Exceptions - Autoplay Media > > > > permissions-exceptions-autoplay-media-window = > > .title = Allowed Websites - Autoplay > > .style = { permissions-window.style } > > -permissions-exceptions-autoplay-media-desc = You can specify which websites are allowed to automatically play media elements. Type the exact address of the site you want to allow and then click Allow. > > +permissions-exceptions-autoplay-media-desc = You can specify which websites are always or never allowed to autoplay media with sound. Type the address of the site you want to manage and then click Block or Allow. > > Need a new ID. I guess permissions-exceptions-autoplay-media-desc would work > here. I have no clue what's going on with comments on mozreview these days. I meant "permissions-exceptions-autoplay-media-desc2" here, tried to comment on mozreview, and it didn't publish.
Ah apologies, I assumed (optimistically) that we only needed new id's after a release, updated
Comment on attachment 8994162 [details] Bug 1476889 - Update autoplay copy. https://reviewboard.mozilla.org/r/258774/#review265782 Thanks, looks good. A change of ID is needed as soon as the string lands in mozilla-central, since we moved all language to Nightly for localization.
Attachment #8994162 - Flags: review?(francesco.lodolo) → review+
Bryant is on PTO, so going to say this is ok
Flags: needinfo?(bmao)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
Verified as fixed on Nightly 63.0a1(20180816220128).
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: