Status check...

[marcoscaceres]

Given the active implementations and continued collaboration amongst implementers on AOM, I'm wondering if we should start thinking of "graduating" this to a W3C Working Group? We don't have to, but it feels like there is enough momentum behind these ideas to warrant moving this to the W3C for formal standardization. If yes, we'd need to find a home for it 🏡.

cc @WICG/chairs

[travisleithead]

My understanding is that there's a variety of different features brewing under the AOM umbrella. Some indeed might be ready to move on, but others probably less likely. @alice likely has the most context on the general state of the world here.

[alice]

Conveniently, I "recently" updated the "Can I Use" document to show the implementation and spec state of the various pieces.

Specifically, the things closest to "maturity" are the "phase 1" projects:

• Custom element semantics on ElementInternals (currently being implemented in Chrome)
• ARIA property reflection (string-based reflection shipping in Safari, implemented in Chrome; element reflection currently being implemented in Chrome [watch for i2i shortly] and planned to be shipped together with string-based reflection as a whole system)

Later phases aren't really ready to go yet; next on my radar is the fallback event/input event spec.

[LJWatson]

Could phase 1 migrate without the rest?

[roelvangils]

Would it already be safe to use (or recommend using) ARIA reflection (using feature detection) in real projects? Browser support does not equal full AT support in this case yet, I suppose?

[marcoscaceres]

@asurkov, what's the status on the Firefox side?

[asurkov]

@asurkov, what's the status on the Firefox side?

my understanding is that there's no active AOM development in Firefox these days, I didn't look into the project for a while, @jcsteh should be in a better position to answer this question.

[marcoscaceres]

Confirmed with @jcsteh that we (Firefox) are not currently working on this.