| 07:02 | <annevk> | I think we generally make events bubble, but it might be worth investigating some other recent introductions. |
| 07:02 | <annevk> | But also, I wish we'd focus on fixing all the existing issues with customizable <select>. There's way too many. |
| 09:27 | <Noam Rosenthal> | Generallly events that relate to interaction bubble (click, keydown, change, submit) and other events (media progress, load, error, formdata) don't. though this has some exceptions that are not always obvious. "beforefillter" should perhaps bubble if you want to be able to handle it at the form level for example. |
| 09:38 | <Noam Rosenthal> | (this is by judging from existing events, not from some official guidance) |
| 11:31 | <Noam Rosenthal> | annevk: mind looking at https://github.com/whatwg/html/pull/12266 when you get a chance? It has been ready for review for a while and is quite small |
| 11:43 | <annevk> | Looks good modulo nit. |
| 19:43 | <nektro> | does the note "no elements will be added to HTML, SVG, or MathML with hyphen-containing local names going forward" apply to attribute names as well? |
| 19:44 | <nektro> | ie is it html's purview to leave unhyphenated attributes to html and hyphenated attributes to devs as well? |
| 19:46 | <Noam Rosenthal> | aria and svg have hyphenated attribute names. The official userspace for attribute is data-* afaik |
| 19:48 | <Noam Rosenthal> | but there is a "consistency" somewhat unofficial rule to keep names concatenated without a separator, see https://www.w3.org/TR/design-principles/#casing-rules |
| 19:57 | <Luke Warlow> | aria and svg have hyphenated attribute names. The official userspace for attribute is I think we generally shouldn't add new hyphenated ones as built-ins personally. |
| 20:15 | <Noam Rosenthal> | Yea I agree that making that semi-official API design principle something more official can be useful (with aria- being an exception) |
| 20:16 | <Noam Rosenthal> | (Also http-equiv and accept-charset if we want to be archeological about it) |