The <Dialog> Element

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com
HTML Whatwg Dialog Standard Polyfill

SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured

  • dialog-polyfill

    Polyfill for the HTML dialog element

    • > - Z-index has no effect in the top-layer. No need to compete for a higher z-index.

    This is the kind of boring feature that can end up saving huge amounts of developer time. Z-indexing in CSS is kind of annoying and I've seen projects just detach dialogs from their normal position in the DOM entirely to get around stacking errors before.

    ----

    Minor question:

    > - There is only one `top-layer` but it can have many children. Last opened === current element on top.

    Is this true? The spec says:

    > The top layer is an ordered set of elements, rendered in the order they appear in the set. The last element in the set is rendered last, and thus appears on top.

    I'm still playing around with `dialog` elements, so you may well be right, I'm just having trouble finding the actual spec rules about what happens when there are multiple dialogs and they're being simultaneously manipulated.

    ----

    > - Not supported in Safari <= 15.3

    Worth noting that there is a polyfill (https://github.com/GoogleChrome/dialog-polyfill), but that the polyfill comes with some fairly large limitations, specifically that they don't advise dialogs be used as children of elements with their own stacking context.

    This is reasonable, but also... my first thought when I originally ran into `dialog` was "finally I can stop worrying about which of my elements create new stacking contexts!" -- so it does decrease the usefulness quite a bit.

  • WHATWG HTML Standard

    HTML Standard

    • Here's a long conversation on it from 2016: https://github.com/whatwg/html/issues/1929

    It has something to do with interfering with automatic focus on the dialog when it pops up as a modal.

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo

  • kill-sticky

    Bookmarklet to remove sticky elements and restore scrolling to web pages!

    • In the meantime, NoScript[1] frequently avoids them entirely by just showing the page contents with no JS at all, and Kill Sticky[2] cleans up the ones that require JS to show you the content you actually want.

    [1] NoScript for Firefox & Chrome-based browsers: https://noscript.net/getit/

    [2] Kill Sticky bookmarklet for all browsers including mobile: https://github.com/t-mart/kill-sticky

    Or, a Firefox extension that adds a toolbar button: https://addons.mozilla.org/en-US/firefox/addon/kill-sticky/

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts