3 ms·
This seems to have been supported in nightly for over a year and behind a feature flag even longer but it's still nowhere near ready for GA. Meanwhile Safari d
by hnbad 6y ago
This seems to have been supported in nightly for over a year and behind a feature flag even longer but it's still nowhere near ready for GA.
Meanwhile Safari doesn't support it at all.
The stats on caniuse are skewed by Chromium as usual.
- deleted 6y ago[deleted]
- inopinatus 6y agoOn the contrary. It’s very usable in FF nightly right now, including dialog forms, and I know this first-hand because I’m using it. Safari TP support is developmental, not absent.
- hnbad 6y agoI'm not saying it's not usable in FF nightly, I'm saying there are major blockers for it to go into GA. As far as I can tell the rendering is currently hacky (i.e. it doesn't follow the spec but achieves the same visual result) and the implementation is supposed to be tied to the `inert` attribute, which isn't currently implemented in FF. This may not matter to most users but if left as-is would result in cross-browser compatibility issues.
- inopinatus 6y agoThis scuttlebutt is misdirection. No GA browser has release support for the inert attribute, which sits behind an experimental feature flag for both Chrome and FF. The inert subtree work is ongoing, and notably, inert support is not showing as a release blocker. Yes, it'll be great to have, but it's far from mandatory. The significant outstanding blocker for FF is re. focus twiddling for better a11y, per recent discussion at whatwg/html#5678, c.f. bugzilla#1660271 & #1701230, and this is hardly boiling-the-oceans stuff. I'm excited for <dialog>, it's a survivor, and a great simplifier - particularly of dev conversations - and I recommend it (even with interim polyfill) to all and sundry.