Disable the Payment Request UI and tests by default on Nightly
Categories
(Firefox :: WebPayments UI, enhancement, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox66 | --- | verified |
People
(Reporter: MattN, Assigned: MattN)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete, Whiteboard: [webpayments])
Attachments
(1 file, 1 obsolete file)
The path to shipping the PaymentRequest UI is still being determined so we should disable the UI by default. We will also disable the tests to reduce the short-term maintenance cost (e.g. intermittent test failure fixes) of the component.
Assignee | ||
Comment 1•5 years ago
|
||
I will leave enabling/disabling the DOM code to the DOM team. Marcos, do you need to give a heads up to anyone at the W3C before I land this? Since the DOM code and pref to enable the UI will still be available, it will still be possible to test our implementation.
Comment 2•5 years ago
|
||
I’m meeting with Ian from W3C in a few hours. Please go ahead and disable.
Assignee | ||
Comment 3•5 years ago
|
||
Cindy, can you check with Nick to see if it's fine to disable-by-default (currently it's enabled on MacOS/Windows in Nightly)? We don't want this to have a negative impact on partner discussions.
Assignee | ||
Comment 4•5 years ago
|
||
Hi Matt, As long as we can flip the pref to turn it on for testing purposes. I don't see there's a problem turning it off by default.
Updated•5 years ago
|
Pushed by mozilla@noorenberghe.ca: https://hg.mozilla.org/integration/autoland/rev/3ee226bda683 Disable the Payment Request UI and tests by default on Nightly. r=jaws,baku
Assignee | ||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3ee226bda683
Comment hidden (off-topic) |
Comment 9•5 years ago
|
||
Verified as fixed on Firefox Nightly 66.0a1 (2018-12-20) on Windows 10 x 64 and Mac OS X 10.13.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 10•5 years ago
•
|
||
This is something that needs a quick documentation checkup...
Comment 11•5 years ago
|
||
I've tweaked the text in the https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features to note that the UI is not currently working after breaking sometime after the tests were disabled.
Comment 12•5 years ago
|
||
Thanks :sheppy.
Comment 13•5 years ago
|
||
:mattn, this has been disabled for 4 months- should we delete the tests? For example the tests pass 10/10 times for windows 10 opt/debug +- qr. Is this worth reenabling?
Assignee | ||
Comment 14•5 years ago
|
||
This bug is about the feature AND tests. My understanding is that the project may be un-pausing "soon". The plan was to wait until end of Q2 to delete if there is no plan to re-enable.
Comment 15•5 years ago
|
||
so if the tests pass, there is no need to run them now; but assuming we fix this feature, the tests will be useful again.
Assignee | ||
Comment 16•5 years ago
|
||
Yes, we don't want to deal with intermittent (or really any) failures while nobody is working on this feature since it's not shipping code. The front-end doesn't even build outside of Nightly.
Description
•