Perma browser/components/pioneer/test/browser/browser_pioneer_ui.js | after clicking enrollment, consent dialog is open. - when Gecko 80 merges to Beta on 2020-07-27
Categories
(Firefox :: Pioneer, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | --- | unaffected |
firefox80 | + | verified |
firefox81 | --- | verified |
People
(Reporter: aryx, Assigned: rhelmer)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 obsolete file)
Log: https://treeherder.mozilla.org/logviewer.html#?job_id=310842160&repo=try
[task 2020-07-23T13:21:25.018Z] 13:21:25 INFO - TEST-PASS | browser/components/pioneer/test/browser/browser_pioneer_ui.js | before enrollment, Pioneer toolbar button is hidden. -
[task 2020-07-23T13:21:25.019Z] 13:21:25 INFO - Buffered messages finished
[task 2020-07-23T13:21:25.019Z] 13:21:25 INFO - TEST-UNEXPECTED-FAIL | browser/components/pioneer/test/browser/browser_pioneer_ui.js | after clicking enrollment, consent dialog is open. -
[task 2020-07-23T13:21:25.020Z] 13:21:25 INFO - Stack trace:
[task 2020-07-23T13:21:25.020Z] 13:21:25 INFO - chrome://mochikit/content/browser-test.js:test_ok:1299
[task 2020-07-23T13:21:25.020Z] 13:21:25 INFO - chrome://mochitests/content/browser/browser/components/pioneer/test/browser/browser_pioneer_ui.js:testAboutPage:90
Assignee | ||
Comment 1•4 years ago
•
|
||
Ah shoot the <dialog>
element is still experimental (it has been released on other browsers but experimental only in Firefox for years apparently but there's recent activity): https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features
Google has a polyfill that looks OK and is under a liberal license: https://github.com/GoogleChrome/dialog-polyfill
Mark, wdyt about using a polyfill vs. implementing this a different way? IIRC Preferences uses XUL but I'd rather avoid it if possible.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Assignee | ||
Comment 4•4 years ago
|
||
(In reply to Cosmin Sabou [:CosminS] from comment #3)
Awesome, thanks for the confirmation! Bringing in a polyfill for this is kind of annoying, but I think it's better than using XUL or something custom... it'll be easy to remove it if/when Firefox ships the latest <dialog>
standard.
Updated•4 years ago
|
Reporter | ||
Comment 5•4 years ago
|
||
If Mark is busy or on PTO, can a different person review the patch?
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 7•4 years ago
|
||
The plan to unblock this is to enabled <dialog> for chrome-only code in Firefox 80, the primary reason it's disabled with now is an a11y issue (bug 1200896). However, we can work around this issue for 80 with a JS focus hack. I'll set the bug blocking when it's filed / I find it :)
Assignee | ||
Comment 8•4 years ago
|
||
The problem with the current patch is that this polyfill has the same a11y problem, so there's not really any point to doing this vs. just enabling native <dialog> for chrome-only code, so I am going to abandon this and will have a new one ASAP.
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 9•4 years ago
|
||
Given bug 1657163 is now in 80, can we close this one?
Reporter | ||
Comment 10•4 years ago
|
||
Verified fixed with yesterday's central-as-beta simulation and on beta with https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel%2Crunnable&revision=3649c4dd0f883b3487fa307b1fd036349a09209e
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Updated•3 years ago
|
Description
•