-
Notifications
You must be signed in to change notification settings - Fork 839
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
Normalize button moz-focus-inner #2445
Conversation
CHANGELOG.md
Outdated
@@ -1,6 +1,8 @@ | |||
## [`master`](https://github.com/elastic/eui/tree/master) | |||
|
|||
- Added ability for `EuiColorStops` to accept user-defined range bounds ([#2396](https://github.com/elastic/eui/pull/2396)) | |||
- Added ability for `EuiColorStops` to accept user-defined range bounds ([#2396](https://github.com/elastic/eui/pull/2396)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think you got an extra CL in here
I setup a reduced test case because I'm not sure what other styles are having an effect inside EUI but Seems like |
I don't think it hurts to have both. Normalize uses both. https://github.com/necolas/normalize.css/blob/fc091cce1534909334c1911709a39c22d406977b/normalize.css#L202-L223 But in @myasonik's codepen, the |
Not sure what's happening on that codepen but I've tested with
|
Well it seems there are inconsistencies between browser versions for support. Perhaps it is just best to support both. |
I've added
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and there doesn't seem to be any adverse affects.
I think you just need to rebase with master to put the CL item in the right place and then you're good to merge.
Summary
Remove border that shows up when tabbing through components in Firefox. Covers #2373
Checklist
- [ ] Checked in dark mode- [ ] Checked in mobile- [ ] Props have proper autodocs- [ ] Added documentation examples- [ ] Added or updated jest tests- [ ] Checked for breaking changes and labeled appropriately- [ ] Checked for accessibility including keyboard-only and screenreader modes