Joey Arhar

The current work on CloseWatcher integration with the dialog element should implement the desired behavior here, right?

For "first tabbable" I am planning on using the "sequentially focusable" term in the HTML spec because it seems to refer to things you can focus to by pressing tab:...

I think some of the test cases in dialog-focus-shadow.html seem contradictory now that I've finally gotten around to implementing all this dialog shadowdom focus stuff: ```html Non-focusable Focusable Non-focusable Focusable...

I think we also need tests for potentially focusable elements being slotted into shadowroots in the dialog. I can propose some behavior and provide test cases like I did in...

Ah I also just finished my test changes here: https://github.com/web-platform-tests/wpt/pull/36498 I'm happy to add my changes after yours are merged, it sounds like they should be compatible

> So I think we should call this resolved, and that sentence should be included in the PR Great! How do I make a conformance requirement/guidance? Is there an example...

> I think it's about just keeping the sentence mentioned in the OP That sentence is now in the PR

> That might be blocked on browser engineers giving a definite answer on whether they plan to implement a soft navigation trap of the sort discussed in the OP? I...

Would it be helpful if I added a console message when dialog.show() is called saying that we are planning to remove it and to come here if you'd like it...

Here is the status of chrome's behavior: @dtapuska tried to [fire mouse events on disabled form controls](https://bugs.chromium.org/p/chromium/issues/detail?id=696686) years ago, and this behavior is still enabled in experimental web platform features...