-
Notifications
You must be signed in to change notification settings - Fork 842
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
EuiInputPopover
docs
#2269
EuiInputPopover
docs
#2269
Conversation
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.
I don't think we need a Beta label. It's not that experimental and I think your paragraph about focus keyboard nav is explanation enough.
Just had a few notes.
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.
Just a couple spelling mistakes and you still need a changelog entry
Co-Authored-By: Caroline Horn <[email protected]>
Co-Authored-By: Caroline Horn <[email protected]>
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, just a nit on the CL
Co-Authored-By: Caroline Horn <[email protected]>
* first pass * snippet * comments * more spacing before window edge * Update src-docs/src/views/popover/popover_example.js Co-Authored-By: Caroline Horn <[email protected]> * Update src-docs/src/views/popover/popover_example.js Co-Authored-By: Caroline Horn <[email protected]> * CL * Update CHANGELOG.md Co-Authored-By: Caroline Horn <[email protected]>
Summary
The beginnings of
EuiInputPopover
were merged so thatEuiSuggest
and a compressed variant ofEuiRange
could use them in their respective feature branches.For the most part, it's a preconfigured
EuiPopover
with some resizing hooks. Focus/a11y is largely dependent on the nature of the input provided, so no real assumptions have been made. With that in mind, I'm considering adding thebeta
tag to this. It's in master, but unused and undocumented. Adding documentation means it needs to provide some sense of its stability, and it's hard to tell with so few known and upcoming use cases; I could see the API changing a bit.Checklist
- [ ] Checked in dark mode- [ ] Checked in mobile- [ ] Checked in IE11 and Firefox- [ ] Added or updated jest tests- [ ] Checked for breaking changes and labeled appropriately- [ ] Checked for accessibility including keyboard-only and screenreader modes