Site Permissions dropdown appears blank
Categories
(Core :: Web Painting, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | unaffected |
firefox91 | --- | unaffected |
firefox92 | --- | fixed |
firefox93 | --- | fixed |
People
(Reporter: jib, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
533.59 KB,
image/png
|
Details |
STR:
- Open https://jsfiddle.net/jib1/59og5vhn/ in two tabs without hitting Allow in either
- Hit Allow in first tab
- Go to the second tab
- Go back to the first tab
- Click the red microphone icon to display the Site Permissions dropdown
- With the the Site Permissions dropdown visible, go to the second tab
- Got back to the first tab
- Click the red microphone icon once more to display the Site Permissions dropdown
15:04.38 INFO: Last good revision: ae11d50c40266fd3413ee79ef86e6ccb1dbbed9c
15:04.38 INFO: First bad revision: e505fffd43c3663a2ed608907ed17830cc526ec9
15:04.38 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=ae11d50c40266fd3413ee79ef86e6ccb1dbbed9c&tochange=e505fffd43c3663a2ed608907ed17830cc526ec9
Notes
- When the prompt goes blank, I can still click on it to activate buttons, so it appears to be a refresh problem only.
Workaround
- Drag the tab into its own window makes the prompt become visible again.
Reporter | ||
Comment 1•3 years ago
•
|
||
I was going to file this on Site Permissions until I found the regression range. Paul can you set the correct component?
Comment 2•3 years ago
|
||
Thanks for filing! Since the regressing bug is also in Web Painting , I think we can leave it here.
Matt, could you please take a look at this regression?
Updated•3 years ago
|
Comment 3•3 years ago
|
||
Set release status flags based on info from the regressing bug 1722258
Comment 4•3 years ago
|
||
Paul, were you able to reproduce this also? If so, is it fixed in today's Nightly? Bug 1724848 may have resolved this issue too.
Comment 5•3 years ago
|
||
I don't have a macOS machine at hand to test this. Also, I can't reproduce the original issue on my Ubuntu machine. Tested via mach mozregression --bad 2021-08-10 --find-fix
.
Comment 6•3 years ago
|
||
I can reproduce this issue on my mac in the affected versions.
Mozregression GUI won't let me investigate because the browser would crash every time (mozregression showed error: "process exited with code 5")
Mozregression CLI results:
26:47.93 INFO: No more integration revisions, bisection finished.
26:47.93 INFO: First good revision: dfe79026c965af369e35ed128c5045a8d48418b6
26:47.93 INFO: Last bad revision: 2e53567a367c832efbcc653d84a28ef060a5bf37
26:47.93 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2e53567a367c832efbcc653d84a28ef060a5bf37&tochange=dfe79026c965af369e35ed128c5045a8d48418b6
As the other regression of bug 1722258, it is most probably fixed by the fix in bug 1724848.
This no longer reproduces in the latest Nighty v93.0a1 from 2021-08-13 or Beta v92.0b3.
Please set the status accordingly, Thank you.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•