Mason Freed
Mason Freed
The explainer currently [says this](https://github.com/openui/open-ui/blob/main/research/src/pages/popup/popup.research.explainer.mdx#classes-of-ui---dismiss-behavior-and-interactions) about the behavior for `popup=hint` (which I'll call "tooltips" for clarity): > Hint/Tooltip (popup=hint) > - When opened, force-closes only other hints, but leaves all...
Akin to the [`` element's standardized styling](https://html.spec.whatwg.org/multipage/rendering.html#flow-content-3), I think it'd be helpful to authors to get a very basic set of standardized styles that the UA applies to pop-ups by...
In https://github.com/openui/open-ui/issues/470 we [resolved](https://github.com/openui/open-ui/issues/470#issuecomment-1138868669) to **a)** have a pseudo class that matches when a pop-up is in the top layer, and **b)** call it `:top-layer`. I [raised this issue](https://github.com/w3c/csswg-drafts/issues/7319) with...
Per the [resolution on 536](https://github.com/openui/open-ui/issues/536#issuecomment-1164737967), we will have `` come with default styles that are standardized. (These can be opted-out via `selectmenu {appearance:auto}` in CSS.) This issue is to brainstorm/bikeshed...
This issue was reported by @domenic [here](https://github.com/mfreed7/popup/issues/4), and is being moved to the OpenUI repo. --- Specifically the interaction with the dismissal behavior. `` has gotten away with just using...
This was raised by @emilio as part of the discussion of https://github.com/openui/open-ui/issues/470. We need to fully define the interactions between top layer element types. What happens when a popup is...
The [CSS Toggles](https://tabatkins.github.io/css-toggle/) API proposal ([explainer](https://css.oddbird.net/toggles/)) provides a way for "state" to be set on elements, and for that state to be modified by other elements. Should the change of...
I would like to re-open the topic of declarative Shadow DOM. This has been discussed in the past, [here on WHATWG](https://github.com/whatwg/dom/issues/510), in W3C [here](https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Declarative-Shadow-DOM.md) and [here](https://github.com/w3c/webcomponents/issues/71), and in [WICG](https://discourse.wicg.io/t/declarative-shadow-dom/1904/8). The...
The explainer for this feature is here: https://github.com/mfreed7/declarative-shadow-dom/blob/master/README.md The issue discussion is here: https://github.com/whatwg/dom/issues/831 There is a corresponding [Pull Request](https://github.com/whatwg/html/pull/5465) for the HTML spec that goes along with this PR....
In #831, there is a [rough consensus](https://github.com/whatwg/dom/issues/831#issuecomment-718157132) that, to protect against client-side XSS, the entry points to the [fragment parser](https://www.w3.org/TR/DOM-Parsing/) need to be guarded by a declarative Shadow DOM "opt-in"....