Diana Broeders
Diana Broeders
The workaround @DRiFTy17 made works really nicely (for now 😉 ) but are there still plans to include this fix in future versions of Floating-ui? I noticed that the same...
In the acceptance criteria there is mention of a(n optional) button, i don't see that in the code (examples).
There is quite some discussion about what the correct behaviour is. Researching this I came across 3 options: 1. Keep as is (popover is always on top of everything else)...
We found a 4th option :D Something that is proposed in the W3C specs; keep the popover open until the trigger is no longer visible: https://drafts.csswg.org/css-anchor-position-1/#position-visibility I'll try and implement...
There will eventually be a native solution using [position-visibility: anchors-visible](https://caniuse.com/mdn-css_properties_position-visibility_anchors-visible), but that doesn’t work cross-browser yet and also doesn’t work in the polyfill we use right now. I tried to...
add a "dateStatusChanged" property to `.json` so we can show a dot or star, or something else to indicate that the STATUS of the component has changed: Coming->Preview->Stable. To trigger...
https://www.chromatic.com/blog/story-modes-are-here/
https://role-components-git-konnorrogers-650642-konnor-rogers-projects.vercel.app/components/combobox/#list-autocomplete-combobox
Some interesting thoughts on toggle buttons, especially with regards to the labeling https://inclusive-components.design/toggle-button/
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-pressed