Closed
Bug 1468153
Opened 6 years ago
Closed 6 years ago
PaymentRequest dialog <button> strings
Categories
(Firefox :: WebPayments UI, enhancement, P1)
Firefox
WebPayments UI
Tracking
()
VERIFIED
FIXED
Firefox 63
Tracking | Status | |
---|---|---|
firefox63 | --- | verified |
People
(Reporter: MattN, Assigned: jaws)
References
Details
(Whiteboard: [webpayments] [user-testing])
User Story
* Update the strings for all buttons from the UI spec.
Attachments
(3 files)
My understanding is that we're supposed to use Photon styles[1] but those are usually only used in-content currently and are implemented in the in-content stylesheets. Should we import all in-content styles (think prefs, error pages, etc.) or move buttons styles to their own stylesheet to share? Note that we don't use Photon button styles in any other dialog e.g. Master Password, window close confirmation, etc. Perhaps we shouldn't be using Photon buttons and instead use native styles to match other dialogs? Using the in-content stylesheet also affects the background colour of the dialog I think. [1] https://design.firefox.com/photon/components/buttons.html
Flags: needinfo?(epang)
Comment 1•6 years ago
|
||
(In reply to Matthew N. [:MattN] (PM if requests are blocking you) from comment #0) > My understanding is that we're supposed to use Photon styles[1] but those > are usually only used in-content currently and are implemented in the > in-content stylesheets. > > Should we import all in-content styles (think prefs, error pages, etc.) or > move buttons styles to their own stylesheet to share? Note that we don't use > Photon button styles in any other dialog e.g. Master Password, window close > confirmation, etc. Perhaps we shouldn't be using Photon buttons and instead > use native styles to match other dialogs? Using the in-content stylesheet > also affects the background colour of the dialog I think. > > [1] https://design.firefox.com/photon/components/buttons.html Hey Matt, think we already covered this last week in person, but thought I would respond so it's here too. We should follow the in-context styles (like prefs). The reason behind this is because the web payments panel should feel like it's part of the chrome and not the platform it's on. For now it's odd since it's in a modal (on windows) but in the future we should have it more integrated to feel like part of the browser.
Flags: needinfo?(epang)
Reporter | ||
Comment 2•6 years ago
|
||
Oops, thanks. This ended up getting implemented in bug 1466720 so I will morph this bug to cover the updated button strings.
User Story: (updated)
Summary: PaymentRequest dialog <button> styles → PaymentRequest dialog <button> strings
Reporter | ||
Comment 3•6 years ago
|
||
We can use this bug to handle the button ordering like we discussed the other day. Can you clear the needinfo once you figure out what ordering we should use for the various states: * onboarding wizard * payment summary page * add/edit screens after coming from the summary page Consider that in Firefox the button order generally follows the platform conventions so, for example, on Windows the primary/affirmative button is normally on the left[1] when there is two buttons (both right-aligned) whereas it's on the right for macOS. [1] https://docs.microsoft.com/en-us/windows/desktop/uxguide/win-dialog-box
User Story: (updated)
Flags: needinfo?(epang)
Summary: PaymentRequest dialog <button> strings → PaymentRequest dialog <button> ordering and strings
Reporter | ||
Updated•6 years ago
|
Whiteboard: [webpayments] → [webpayments] [user-testing]
Reporter | ||
Comment 4•6 years ago
|
||
I'll move the ordering to a separate bug since it can be done in M4.
User Story: (updated)
Summary: PaymentRequest dialog <button> ordering and strings → PaymentRequest dialog <button> strings
Comment 5•6 years ago
|
||
Here's the ixd for the buttons. If needed the visuals can be found here: https://mozilla.invisionapp.com/d/main#/console/13422080/305451650/preview
Flags: needinfo?(epang)
Comment 6•6 years ago
|
||
Hey Matt, did you open a new bug for ordering? I posted the spec here, but can move it over if needed. Thanks!
Flags: needinfo?(MattN+bmo)
Reporter | ||
Comment 7•6 years ago
|
||
Hey Eric, we moved the ordering to bug 1478176 as we felt that wasn't needed for user testing.
Flags: needinfo?(MattN+bmo)
Reporter | ||
Comment 8•6 years ago
|
||
verification-steps |
QA can verify that all the strings match Eric's spec.
Flags: qe-verify+
QA Contact: hani.yacoub
Assignee | ||
Comment 9•6 years ago
|
||
(In reply to Eric Pang [:epang] UX from comment #5) > If needed the visuals can be found here: > https://mozilla.invisionapp.com/d/main#/console/13422080/305451650/preview Hey Eric, the link above doesn't work for me. Can you try to re-share it?
Flags: needinfo?(epang)
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Updated•6 years ago
|
Priority: P2 → P1
Comment hidden (mozreview-request) |
Comment 11•6 years ago
|
||
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #9) > (In reply to Eric Pang [:epang] UX from comment #5) > > If needed the visuals can be found here: > > https://mozilla.invisionapp.com/d/main#/console/13422080/305451650/preview > > Hey Eric, the link above doesn't work for me. Can you try to re-share it? give this a try, I'll also add a screenshot. The link is best though you can click to see the spacing spec; https://mozilla.invisionapp.com/share/S5FXRY0D8TZ#/305451650_9-1_UI_Components
Flags: needinfo?(epang)
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
mozreview-review |
Comment on attachment 8996030 [details] Bug 1468153 - Update the edit strings (Add/Update) and the failure strings to use the hostname. https://reviewboard.mozilla.org/r/260300/#review267662 Looks great. Thanks for hooking up the error page strings and hostname stuff.
Attachment #8996030 -
Flags: review+
Assignee | ||
Updated•6 years ago
|
Attachment #8996030 -
Flags: review?(MattN+bmo)
Comment 14•6 years ago
|
||
Pushed by jwein@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/946f0a8fe89e Update the edit strings (Add/Update) and the failure strings to use the hostname. r=sfoster
Comment 15•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/946f0a8fe89e
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox63:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 63
Comment 16•6 years ago
|
||
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Add/Update button: Verified fixed, the buttons are correctly displayed and functional in the Add/Edit screens (Windows 10 x64, Ubuntu 16.04, Mac OS 10.13) Worth mentioning that if "Edit" is clicked while there is no shipping address selected, in the Edit Shipping Adress screen, the "Add" button appears instead of "Update". I believe that this will be solved once with Bug 1463547. Failure strings: The Failure screen (paymnet fail) has the "Check your credit card has not expired." suggestion that should be corrected to "Check if your credit card has not expired." or "Check the expiration date on your credit card.". Otherwise, it is verified fixed on all OS. Waiting for confimration from Eric regarding the mentioned string before any bug status changes.
Flags: needinfo?(epang)
Comment 17•6 years ago
|
||
Actually, based on spec doc it should be "Check that your credit card is not expired".
Assignee | ||
Comment 18•6 years ago
|
||
(In reply to Timea Babos from comment #17) > Actually, based on spec doc it should be "Check that your credit card is not > expired". Can you please file a new bug for this and needinfo me?
Flags: needinfo?(epang) → needinfo?(timea.babos)
Comment 19•6 years ago
|
||
Here it is: https://bugzilla.mozilla.org/show_bug.cgi?id=1480707 Since I filed a new bug for it, I will close this issue as Verified - Fixed.
Status: RESOLVED → VERIFIED
Flags: qe-verify+
Flags: needinfo?(timea.babos)
You need to log in
before you can comment on or make changes to this bug.
Description
•