Skip to content

fix(material/input): incorrect color for select using the size attribute - #23734

Merged
andrewseguin merged 1 commit into
angular:masterfrom
crisbeto:inline-select-color
Oct 19, 2021
Merged

fix(material/input): incorrect color for select using the size attribute#23734
andrewseguin merged 1 commit into
angular:masterfrom
crisbeto:inline-select-color

Conversation

@crisbeto

Copy link
Copy Markdown
Member

Currently we don't apply the theme colors to native select elements, because it can the option text to blend in with the background for Windows users. Our current approach seems to break down for inline selects (with multiple or size attributes), because they don't have a dropdown, but are instead rendered inline.

These changes make it so the exclusion is only applied to select elements that have a dropdown.

Currently we don't apply the theme colors to native `select` elements, because it can the option text to blend in with the background for Windows users. Our current approach seems to break down for inline selects (with `multiple` or `size` attributes), because they don't have a dropdown, but are instead rendered inline.

These changes make it so the exclusion is only applied to `select` elements that have a dropdown.
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround G This is is related to a Google internal issue target: patch This PR is targeted for the next patch release labels Oct 12, 2021
@crisbeto
crisbeto requested a review from andrewseguin October 12, 2021 09:50
@crisbeto
crisbeto requested a review from a team October 12, 2021 09:50
@google-cla google-cla Bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 12, 2021
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 12, 2021
@andrewseguin
andrewseguin merged commit 032cb06 into angular:master Oct 19, 2021
andrewseguin pushed a commit that referenced this pull request Oct 19, 2021
…ute (#23734)

Currently we don't apply the theme colors to native `select` elements, because it can the option text to blend in with the background for Windows users. Our current approach seems to break down for inline selects (with `multiple` or `size` attributes), because they don't have a dropdown, but are instead rendered inline.

These changes make it so the exclusion is only applied to `select` elements that have a dropdown.

(cherry picked from commit 032cb06)
andrewseguin pushed a commit that referenced this pull request Oct 19, 2021
…ute (#23734)

Currently we don't apply the theme colors to native `select` elements, because it can the option text to blend in with the background for Windows users. Our current approach seems to break down for inline selects (with `multiple` or `size` attributes), because they don't have a dropdown, but are instead rendered inline.

These changes make it so the exclusion is only applied to `select` elements that have a dropdown.

(cherry picked from commit 032cb06)
forsti0506 pushed a commit to forsti0506/components that referenced this pull request Oct 22, 2021
…ute (angular#23734)

Currently we don't apply the theme colors to native `select` elements, because it can the option text to blend in with the background for Windows users. Our current approach seems to break down for inline selects (with `multiple` or `size` attributes), because they don't have a dropdown, but are instead rendered inline.

These changes make it so the exclusion is only applied to `select` elements that have a dropdown.
@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Nov 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement G This is is related to a Google internal issue P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants