-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
Popover v11 #1896
Comments
If this one is blocking Happy to give it a crack with the Popover API. Have been wanting an excuse to have a proper look at it anyway. |
I'm opposed to using the popover API, it's not even in Firefox yet (only nightly). |
It's been in every other major browser since September 2023. How long is reasonable to wait for Mozilla to catch up? (genuine question)
I think we could add a |
I would not use anything that hasn't been in all major browsers at least half a year, no matter how long it takes. One year would be even better. Also, the main issue is often Safari because its updates are bound to the OS, which is just plain horrible; the update cadence is low and on older OS versions you may not even be able to get the latest Safari at all. Regarding hover, I don't think
In v11 there are changes to tooltips that need to be addressed:
Note from spec:
In the React version,
|
All good points. As a side note, it would be great if we could test attributes and CSS features in Playwright with a browserslist file for compatibility. I updated the criteria above. Ideally, most of this is achievable with CSS, but the styles provided may not already work that way. Here's a handy guide: https://inclusive-components.design/tooltips-toggletips/
|
Spun off from #1629
Maybe implement the new no-JS Popover API now that it's near-baseline 👀 https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/popoveruse JS and implement appropriate timings fortouchstart
andmouseover
The text was updated successfully, but these errors were encountered: