Closed Bug 1346440 Opened 7 years ago Closed 7 years ago

[e10s] Background or text color of options in drop-down defined by web page are not respected (sometimes)

Categories

(Core :: Layout: Form Controls, defect)

52 Branch
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox53 + unaffected
firefox54 + fixed
firefox55 --- fixed

People

(Reporter: 684sigma, Assigned: jaws)

References

Details

(Keywords: testcase)

Attachments

(2 files)

I have a problem with Firefox Beta 52. It doesn't happen on Firefox ESR 45.
Sometimes background or text color of options in drop-down defined by web page are not respected.
It happens unpredictably, however, I noticed one specific scenario when it happens

1. Open this url (text between quotes is url): "data:text/html,<style>option{background-color:black!important;color:white!important;}</style><select><option>Bob</option><option>Alice</option></select>"
2. Click on text "Bob" on the page

Result: options have white background, black text color
Expected: black background, white text color

I found this bug on a site, but was able to replicate is locally, so I don't have to tell you the site.
Although it's like a duplicate of bug 910022, but I see an unusual paint in 55.0a1 (2017-03-10) (32-bit) with e10s on. Feel free to update the summary.
Blocks: 910022
Has STR: --- → yes
Component: Untriaged → Layout: Form Controls
Keywords: testcase
Product: Firefox → Core
Summary: Regression Background or text color of options in drop-down defined by web page are not respected (sometimes) → [e10s] Background or text color of options in drop-down defined by web page are not respected (sometimes)
Yes, styling < select> broken with e10s is bug 910022 (which is only fixed in 54+). But, there is still a remaining issue with unselected options staying invisible with black background in the dropdown list.
[Tracking Requested - why for this release]: visible UI regression in content related to bug 910022
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Sticking a 53 tracking flag on this as well in case we end up uplifting this and stuff from bug 910022 to 53 beta.
Attachment #8846760 - Flags: review?(mconley) → review?(dtownsend)
Comment on attachment 8846760 [details]
Bug 1346440 - Force the user-agent styles to apply when sampling the colors.

https://reviewboard.mozilla.org/r/119760/#review122578
Attachment #8846760 - Flags: review?(dtownsend) → review+
Pushed by jwein@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2801d6d63979
Force the user-agent styles to apply when sampling the colors. r=mossop
https://hg.mozilla.org/mozilla-central/rev/2801d6d63979
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Depends on: 1348617
Comment on attachment 8846760 [details]
Bug 1346440 - Force the user-agent styles to apply when sampling the colors.

Approval Request Comment
[Feature/Bug causing the regression]: regression from bug 910022
[User impact if declined]: some select menus may not show the text and background color as the same and thus unreadable
[Is this code covered by automated tests?]: yes
[Has the fix been verified in Nightly?]: no
[Needs manual test from QE? If yes, steps to reproduce]: no
[List of other uplifts needed for the feature/fix]: none
[Is the change risky?]: no
[Why is the change risky/not risky?]: contained fix to the <select> menus when custom colors are set by the page
[String changes made/needed]: none
Attachment #8846760 - Flags: approval-mozilla-aurora?
Comment on attachment 8846760 [details]
Bug 1346440 - Force the user-agent styles to apply when sampling the colors.

Fix an UI regression related to select menus. Aurora54+.
Attachment #8846760 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
jaws, do you want to uplift this and the work from bug 910022 to beta as well ? Worth the risk?
Flags: needinfo?(jaws)
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #14)
> jaws, do you want to uplift this and the work from bug 910022 to beta as
> well ? Worth the risk?

We're still getting new bugs filed against the feature every couple days so I'd hold off at this point. blinky, you've been amazing at finding bugs. Has it been getting harder to find new bugs with the feature?
Flags: needinfo?(jaws) → needinfo?(over68)
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #15)
> Has it been getting harder to find new bugs with the feature?

It has gotten harder to find new bugs.
Flags: needinfo?(over68)
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #14)
> jaws, do you want to uplift this and the work from bug 910022 to beta as
> well ? Worth the risk?

Over the weekend blinky found a couple more bugs. Though it has gotten harder to find new bugs, the amount of follow-up from bug 910022 and the rate at which new bugs are being found is concerning regarding uplift to 53. At this point I'm confident that we should not uplift to 53.
setting 53 back to unaffected based on comment 17, since we won't be uplifting 910022.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: