Open
Bug 1598614
Opened 4 years ago
Updated 2 years ago
[aarch 64] The browser controls are not correctly displayed while using high contrast theme
Categories
(Core :: Graphics: Layers, defect, P3)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox71 | --- | wontfix |
firefox72 | --- | wontfix |
firefox73 | --- | fix-optional |
People
(Reporter: obotisan, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(2 files)
Differential Revision: https://phabricator.services.mozilla.com/D36579
Affected versions
- Firefox 71.0b12
*Nightly 72.0a1
Affected platforms
- Windows 10 x64 (aarch64)
Prerequisites
- Set a High Contrast Theme.
Steps to reproduce
- Open Firefox and make sure that the Default theme is selected in the browser.
- Look at the browser controls.
Expected result
- The controls are correctly displayed.
Actual result
- It seems like the controls are doubled.
Regression range
- First bad: 2019-07-09
- Last good: 2019-07-08
- Potentially regressed by: Mozregression concluded that Bug 1562847 - Disable double buffering with compositor when device reset happens, might have caused the issue.
But I am not sure about that fact, because the build from and before 2019-07-08 it's black and the controls can't be seen properly.
Additional notes
- As far as I can tell this issue is not reproducing using Light Theme or Dark Theme.
- Please look at the attached image.
Reporter | ||
Comment 1•4 years ago
|
||
On one of the profiles the issue was really evident.
Updated•4 years ago
|
Has Regression Range: --- → yes
Has STR: --- → yes
Comment 2•4 years ago
|
||
Too late for 71.
Updated•4 years ago
|
Component: Theme → Graphics: Layers
Product: Firefox → Core
Comment 3•4 years ago
|
||
Wait, is this actually exclusive to our ARM Windows builds? That's not a typo?
Blocks: wr-72
Flags: needinfo?(oana.botisan)
Comment 4•4 years ago
|
||
I managed to reproduce it on 73 as well, updating the flag accordingly.
status-firefox73:
--- → affected
Reporter | ||
Comment 5•4 years ago
|
||
Hi Alexis,
Sorry for not responding sooner, but I was on a sick-leave. No, it's not a typo. I only managed to reproduce the issue on arm builds.
Flags: needinfo?(oana.botisan)
Comment 6•4 years ago
|
||
The priority flag is not set for this bug.
:jbonisteel, could you have a look please?
For more information, please visit auto_nag documentation.
Flags: needinfo?(jbonisteel)
Updated•4 years ago
|
Updated•4 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•