Bogus window controls are displayed behind pinned tabs with high contrast turned on
Categories
(Core :: Widget: Win32, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox65 | --- | unaffected |
| firefox66 | --- | unaffected |
| firefox67 | --- | affected |
People
(Reporter: hyacoub, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
140.41 KB,
image/png
|
Details |
pinned tabs.png
[Affected versions]:
Nightly 67.0a1
[Affected platforms]:
Platforms: Windows 10 x 64
[Steps to reproduce]:
- Enable a high contrast theme:
- Windows: Go to Personalise> Themes> Theme Settings and activate a High
Contrast Theme.
- Windows: Go to Personalise> Themes> Theme Settings and activate a High
- Open Firefox and go to youtube.com
- Open several videos in background tabs without focusing them
- Pin any of the unfocused tabs by:
-right click on each tab -> select Pin Tab
-right click on each tab -> hit P key - Observe all pinned tabs
- Click on any of the pinned tabs and play the video
- Keep the video playing and change the focus by clicking on any of the open tabs
[Expected result]:
No extra characters should be displayed on pinned tabs with high contrast turned on
[Actual result]:
Unknown characters are displayed on pinned tabs with high contrast theme
|
Reporter | |
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
Hi Hani, is this problem unique to ARM64 builds? Also can you check a beta66 arm64 build? I am surprised why 66 is marked as unaffected. Thanks!
|
|
Reporter | |
Comment 2•5 years ago
|
||
Yes, this problem is unique to ARM64 builds. When we started testing ARM64 builds, I wasn't aware from where you could download ARM64 builds.
I tried to check if the issue is reproducible on Firefox 66.0b14 ARM64 builds but I couldn't reproduce it, I couldn't reproduce it neither on the latest Firefox Nightly 67.0a1 (2019-03-06).
More investigation should be done here before closing it.
|
|
||
Comment 3•5 years ago
|
||
(In reply to Hani Yacoub from comment #2)
More investigation should be done here before closing it.
What kind of investigation?
|
|
Reporter | |
Comment 4•5 years ago
|
||
I guess I wanted to know how exactly it was fixed.
I'm closing this issue since it's not reproducible any more on Firefox Nightly 68.0a1 (2019-03-24).
Thanks.
Description
•