A product I worked on turned up problems in an accessibility audit, one of them amounted to the modal <Dialog> from a major framework not really hiding the rest of the page from screen readers whereas <dialog> does that with great certainty. We are are still using older framework versions but looking at the source code, few are using <dialog> in their latest versions.
Our own <ModalDialog> based on <dialog> instead of a. <Portal> works great but we are still dealing with problems such as MUI’s <Select> computing the coordinates of the <Popover> wrong which I think is not so hard to fix but all of that adds up to people being slow to adopt <dialog> but so much amounts to the edge-triggered paradigm in React not really matching the simple ‘call a freaking method on the <dialog> API’.
That <output> would be really cool with framework support to calculate formulas like a spreadsheet.
PaulHoule•6h ago
Our own <ModalDialog> based on <dialog> instead of a. <Portal> works great but we are still dealing with problems such as MUI’s <Select> computing the coordinates of the <Popover> wrong which I think is not so hard to fix but all of that adds up to people being slow to adopt <dialog> but so much amounts to the edge-triggered paradigm in React not really matching the simple ‘call a freaking method on the <dialog> API’.
That <output> would be really cool with framework support to calculate formulas like a spreadsheet.