Skip to content

fix(material-experimental/chips): high contrast mode fixes #16811

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 21, 2019

Conversation

crisbeto
Copy link
Member

Fixes the following issues with the MDC-based chips in high contrast mode:

  • Chips blending in with the background because they don't have an outline or a border.
  • No focus indication being visible.
  • Chips being hidden completely on hover because we were using an RGBA overlay.

Fixes the following issues with the MDC-based chips in high contrast mode:
* Chips blending in with the background because they don't have an outline or a border.
* No focus indication being visible.
* Chips being hidden completely on hover because we were using an RGBA overlay.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent pr: merge safe target: patch This PR is targeted for the next patch release labels Aug 18, 2019
@crisbeto crisbeto requested a review from mmalerba as a code owner August 18, 2019 20:04
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 18, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we upstream these fixes to mdc web?

cc @abhiomkar


// Note that we use a `background` and `opacity`, instead of an `rgba` background, because
// `rgba` backgrounds get converted into solid colors in high contrast mode.
background: #000;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just black?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went with this since it's shorter.

@abhiomkar
Copy link

Could we upstream these fixes to mdc web?

cc @abhiomkar

That would be great! Thanks ..

@crisbeto
Copy link
Member Author

FWIW some of the changes here target the hover indication that we implemented ourselves because we aren't using the MDC ripples.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Feel free to upstream whatever makes sense

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: merge safe labels Aug 19, 2019
@jelbourn
Copy link
Member

(not merge-safe since the chips are actually used by one team now)

@andrewseguin andrewseguin merged commit ba3ec6c into angular:master Aug 21, 2019
@angular-automatic-lock-bot
Copy link

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 Sep 21, 2019
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 P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants