Luke Warlow

Web App Manifest New Note URL - Missing

1

#### What information was incorrect, unhelpful, or incomplete? There's no entry for [Note Taking New Note URL](https://wicg.github.io/manifest-incubations/index.html#note_taking-member). #### What did you expect to see? An entry for it, with support...

WIP dialog closedby attribute spec

2

FIxes #9373 This is a very rough WIP draft at this. Needs linting etc. - [ ] At least two implementers are interested (and none opposed): * Chromium * …...

Use close watcher when supported in place of escape key handlers

3

# Pull Request ## 📖 Description This PR uses the CloseWatcher API [1][2] in place of escape key listeners where it's supported. This allows components such as dialog to be...

# 🙋 Feature Request Use the new CloseWatcher API [1][2] (where supported) instead of an escape keydown event listener. This means you can dismiss these components using Android back gestures/button...

[interest invokers] Should el.interestTargetElement return null when not supported?

1

Similar question applies to el.invokeTargetElement. If I put `interesttarget` on a div and then do div.interestTargetElement which should it return? Currently invokeTargetElement "works" for submit buttons in so much as...

[interest invokers] Should interesttarget work on disabled form controls?

4

@keithamus mentioned this during review of the initial implementation. Disabled buttons right now can't be focused (at least using the tab key with the default `Foo` markup). So interest might...

Related to #908 but specific to `` elements. These were left out of the original resolution: https://github.com/openui/open-ui/issues/839#issuecomment-1739848561 but I feel like they're close enough to anchor tags to warrant another...

Currently the [interest invokers](https://open-ui.org/components/interest-invokers.explainer/) explainer doesn't include an `interestaction` attribute. While this makes sense as it's always "toggle"/"auto" for v1 browser actions, doesn't that preclude custom actions and also go...

[focusgroup] Functionality defered to (abandoned?) CSS Toggles Proposal

3

Currently the focusgroup proposal defers some functionality to the [CSS Toggles Proposal](https://tabatkins.github.io/css-toggle/) However, based on the final comment on the [Chrome bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1250716&q=CSS%20Toggles%20Proposal&can=2) and the [linked document](https://docs.google.com/document/d/10JxXgeDAJ5zerOdxoWM9ZU9d5iMOdzGJt0EhlhkOkxM/edit#heading=h.dgwo5ekohooq) it would seem that...

Standardise the anatomy of input[type=number]

6

`` elements display spinners in most desktop browsers to increase/decrease the number value. These cannot be styled. There is the non-standard ::-webkit-inner-spin-button and ::-webkit-outer-spin-button, but these are limited and don't...