| 13:43 | <sefeng> | can someone help me to understand the correct behaviour of sequential focusing when the current focused element is not in Document's sequential navigation order. I've filed a bug https://bugzilla.mozilla.org/show_bug.cgi?id=1824805 |
| 13:47 | <sefeng> | I think this eventually fits into Let candidate be the first suitable sequentially focusable area in the home document following starting point, if any; or else null , however I don't understand what following starting point means |
| 14:26 | <annevk> | sefeng: I think that's worth filing an issue on |
| 14:26 | <annevk> | sefeng: following could mean node tree following, but could also mean some implementation-defined thing that potentially looks at the layout tree, I suppose |
| 14:27 | <sefeng> | okay, thanks! I am confused. I'll file one |
| 14:28 | <annevk> | sefeng: I'm also not sure I even understand how to navigate that table |
| 14:39 | <sefeng> | Filed https://github.com/whatwg/html/issues/9081 |
| 15:15 | <bkardell: away March 27> | hmm... I just noticed that custom elements are not listed as a means of extenisbility for html (where all the others are https://html.spec.whatwg.org/#extensibility)... seems strange to me, but...is there a reason? I tried searching issues to see if I could see it discussed, but I couldn't find anything, so I'm curious.. |
| 15:20 | <annevk> | More context on my earlier HTML parser test comment: https://github.com/web-platform-tests/wpt/issues/27868#issuecomment-1487094289 |
| 15:21 | <annevk> | bkardell: away March 27: we lacked Ian Hickson's holistic knowledge of the HTML Standard when adding custom elements most likely; please file? |
| 15:36 | <bkardell: away March 27> | https://github.com/whatwg/html/issues/9082 |
| 16:44 | <annevk> | bkardell: feel free to PR stuff like that btw |