Closed
Bug 1693950
Opened 4 years ago
Closed 4 years ago
test_menulist_position.xhtml fails on macOS with the non-native theme enabled
Categories
(Core :: Widget: Cocoa, defect, P2)
Core
Widget: Cocoa
Tracking
()
RESOLVED
FIXED
88 Branch
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: spohl, Assigned: spohl)
References
Details
(Whiteboard: [mac:nonnativetheme])
Attachments
(2 files)
No description provided.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
This test probably never tested what it was pretending to. It looks like the test was trying to verify that button b1
does not show a focus ring after being clicked by comparing the appearance of button b1
that was just clicked to another button b2
. However, the test then expects the snapshots to not match, which basically means the test was expecting a focus ring after all. The reason why this test didn't fail before is because there is some consistent fuzziness in the two snapshots when using the native theme that disappears when we switch to the non-native theme.
I have manually created this log file to upload to our Reftest analyzer to visualize the differences between native theme and non-native theme.
Assignee | ||
Updated•4 years ago
|
Attachment #9204358 -
Attachment mime type: application/octet-stream → text/plain
Updated•4 years ago
|
Attachment #9204356 -
Attachment description: Bug 1693950: Fix test_menulist_position.xhtml to pass on macOS with the non-native theme enabled. r=emilio,mstange → Bug 1693950: Ensure that chrome tests continue to use the native theme to not lose test coverage since we do not intend to enable the non-native theme in chrome at this time. r=emilio,mstange
Pushed by spohl@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/74607627d1da
Ensure that chrome tests continue to use the native theme to not lose test coverage since we do not intend to enable the non-native theme in chrome at this time. r=mstange
Comment 4•4 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox88:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 88 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•