2021-12-01 [20:20:16.0746] Hi guys, is this room appropriate to ask questions regarding the HTML spec? [20:21:42.0914] I'll ask for now, but feel free to delete it if it's not allowed, so here is my question: [20:21:53.0439] * I'll ask for now, but feel free to delete it if it's not allowed, so here is my question: [20:29:54.0931] In the HTML parsing section, specifically the "Named character reference state", we have the following info: >>> Consume the maximum number of characters possible, where the consumed characters are one of the identifiers in the first column of the named character references table. Append each character to the temporary buffer when it's consumed. >>[If there is a match]: If the character reference was consumed as part of an attribute, and the last character matched is not a U+003B SEMICOLON character (;), and the next input character is either a U+003D EQUALS SIGN character (=) or an ASCII alphanumeric, then, for historical reasons, flush code points consumed as a character reference and switch to the return state. >>[Otherwise:] If the last character matched is not a U+003B SEMICOLON character (;), then this is a missing-semicolon-after-character-reference parse error. Set the temporary buffer to the empty string. Append one or two characters corresponding to the character reference name (as given by the second column of the named character references table) to the temporary buffer. Flush code points consumed as a character reference. Switch to the return state. [20:33:50.0109] At what point do I decide to stop consuming? It's not clear , I know I can lookahead and stop matching when I encounter a semi-colon but the spec doesn't make that clear [20:35:09.0154] devsrealmguy: I think you basically stop consuming when there’s no match [20:35:20.0976] no substring match [20:38:40.0369] so if you get `&h`, keep consuming, `&he`, keep consuming, `&hel`, `&hell`, `&helli`, still consuming [20:39:28.0815] because those all are substring matches of valid character references [20:40:07.0990] but if you hit `&helliq`, stop consuming — because that is not a substring match of any valid character reference [20:41:01.0746] Thanks for replying, I appreciate it a lot. I am on mobile, so, it's really hard to write and my sight is really poor, so, sorry if I my grammar is wrong. And yes, that is exactly what I am doing, what if you have ¬ and ¬in? [20:44:06.0282] > but if you hit `&helliq`, stop consuming — because that is not a substring match of any valid character reference Brilliant, I was looking to stop consuming when I encounter a semi-colon but you just nailed it. [20:54:43.0723] Never mind with the ¬it and ¬in. Got it, thanks 😊 [23:29:26.0200] morning annevk, I think https://github.com/whatwg/fetch/pull/1311 is reviewable again, and I have two other pending ones (preload & controller), when you get the chance to look [06:48:50.0645] I think I am done with covering the tokenization state, the only state that is a bit difficult is the "Named Character Reference State". Just to confirm I didn't mess things up, this point says: 1) If the last character matched is not a U+003B SEMICOLON character (;), then this is a missing-semicolon-after-character-reference parse error. 2) Set the temporary buffer to the empty string. Append one or two characters corresponding to the character reference name (as given by the second column of the named character references table) to the temporary buffer" An example of point 1 is this: "James & his brother went for launch". It is clear that the & is missing a semi-colon, so, is the point 2 saying to correct it to & (with the semi-colon) or is it saying to swap it with the codepoint which is U+00026 as that is what is given in the second column table which the point 2 is referring to. I was curious enough to check how other libraries did theirs, some are converting the codepoint to a character, some are appending the semi-colon and many ignored it. I can see why it trips people of. Where should I sail to? [06:49:13.0307] * I think I am done with covering the tokenizationstate, the only state that is a bit difficult is the "Named Character Reference State". Just to confirm I didn't mess things up, this point says: 1) If the last character matched is not a U+003B SEMICOLON character (;), then this is a missing-semicolon-after-character-reference parse error. 2) Set the temporary buffer to the empty string. Append one or two characters corresponding to the character reference name (as given by the second column of the named character references table) to the temporary buffer" An example of point 1 is this: "James & his brother went for launch". It is clear that the & is missing a semi-colon, so, is the point 2 saying to correct it to & (with the semi-colon) or is it saying to swap it with the codepoint which is U+00026 as that is what is given in the second column table which the point 2 is referring to. I was curious enough to check how other libraries did theirs, some are converting the codepoint to a character, some are appending the semi-colon and many ignored it. I can see why it trips people of. Where should I sail to? [06:49:33.0671] * I think I am done with covering the tokenization state, the only state that is a bit difficult is the "Named Character Reference State". Just to confirm I didn't mess things up, this point says: 1) If the last character matched is not a U+003B SEMICOLON character (;), then this is a missing-semicolon-after-character-reference parse error. 2) Set the temporary buffer to the empty string. Append one or two characters corresponding to the character reference name (as given by the second column of the named character references table) to the temporary buffer" An example of point 1 is this: "James & his brother went for launch". It is clear that the & is missing a semi-colon, so, is the point 2 saying to correct it to & (with the semi-colon) or is it saying to swap it with the codepoint which is U+00026 as that is what is given in the second column table which the point 2 is referring to. I was curious enough to check how other libraries did theirs, some are converting the codepoint to a character, some are appending the semi-colon and many ignored it. I can see why it trips people of. Where should I sail to? [06:51:51.0877] * I think I am done covering the tokenization state, the only state that is a bit difficult is the "Named Character Reference State". Just to confirm I didn't mess things up, this point says: 1) If the last character matched is not a U+003B SEMICOLON character (;), then this is a missing-semicolon-after-character-reference parse error. 2) Set the temporary buffer to the empty string. Append one or two characters corresponding to the character reference name (as given by the second column of the named character references table) to the temporary buffer" An example of point 1 is this: "James & his brother went for launch". It is clear that the & is missing a semi-colon, so, is the point 2 saying to correct it to & (with the semi-colon) or is it saying to swap it with the codepoint which is U+00026 as that is what is given in the second column table which the point 2 is referring to. I was curious enough to check how other libraries did theirs, some are converting the codepoint to a character, some are appending the semi-colon and many ignored it. I can see why it trips people of. Where should I sail to? [06:57:09.0409] Step 1 is just "the author screwed up" - you should ignore the step completely unless you surface parse errors somehow [06:59:28.0394] `&` without the semicolon is in the table, so you just parsed an "&" [07:00:12.0195] Did that help or just confuse more? :) [07:00:28.0904] You mean, I should add the "&" to the temporary buffer? [07:02:23.0453] Yes, it seems like that's the result [07:02:41.0652] /me was unaware of this particular ugly corner of the parser [07:03:38.0426] Okay, thanks. I spent tons of time on just that state than the rest of the states combined 😂 [07:03:52.0913] * Okay, thanks. I spent tons of time on just that states than the rest of the state combined 😂 [07:04:32.0147] * Okay, thanks. I spent tons of time on just that state than the rest of the state combined 😂 [07:04:44.0168] * Okay, thanks. I spent tons of time on just that state than the rest of the states combined 😂 [09:02:29.0923] At some point we should blog about the fact that we've added/are adding a bunch of new standards: Web IDL, Test Utils, WebSockets, and File System [09:02:36.0599] I guess I will try to draft something quick [11:28:57.0652] Posted https://blog.whatwg.org/new-living-standards-2021 and tweeted https://twitter.com/WHATWG/status/1466126880344616966 [14:38:01.0032] I seem to remember there was a tool that lists all Web IDL interfaces, where they are defined and where they are used in other specifications. Anyone knows what it was called again? [14:38:57.0710] https://dontcallmedom.github.io/webidlpedia/index.html ? [14:39:28.0920] Yep, that's it. Thanks! 😁 [14:40:00.0280] There's also https://github.com/w3c/webref/tree/main/ed/idl 2021-12-02 [22:24:31.0155] Anybody knows of specific implementation difficulties with the `search` element in any of the 3 browsers? [22:33:36.0773] Are there hotkeys on whatpr.org? [22:35:09.0197] * Are there hotkeys on whatpr.org? Yep, J.K. Rowling [22:37:18.0708] Is there a way to filter seciton number changes from the diffs? [02:28:00.0895] Andreu Botella (he/they): care to review https://github.com/whatwg/fetch/pull/1364? (very small) [02:28:23.0773] Oh maybe wait, build is still failing [06:50:31.0079] The triage meeting will take place here on matrix? [07:02:17.0802] No, it's a video call [07:02:56.0741] I don't find any info about what software is used for the call. [07:05:31.0215] What's the conferencing software used? [07:07:28.0895] I think it's Google Meet, no software needed other than a browser [07:07:48.0296] and a google account ;-) [07:08:38.0607] I don't think so [07:09:27.0847] oh, great how is the meeting link/code shared? [07:11:30.0750] Unless you are different from Kaleidea on GitHub I think past mentioned they will get you an invite? [07:12:15.0265] Yes, I was wondering, how he'll do it. [07:12:45.0177] Presumably via a calendar invite [07:31:15.0651] kaleidea: FWIW, the fundamental problem with inheritance for HTML elements is that engine logic is based on local name, not type of class; this is also why custom elements has the is="" hack (which in retrospect I wish we never shipped) [07:32:03.0459] The other problem with a new element for navigation is bad XSS filters and just overall complexity. [07:36:27.0547] > <@annevk:mozilla.org> kaleidea: FWIW, the fundamental problem with inheritance for HTML elements is that engine logic is based on local name, not type of class; this is also why custom elements has the is="" hack (which in retrospect I wish we never shipped) HTMLFormElement is a final class (all HTML*Elements are), so inheritance quickly fell out as a solution. I've made a HTMLFormElement, distinguished only by qualified name (namespace incl.). This is the same solution that's used for

,

, etc. - and would be used for the div-based -, but with HTMLElement being the instantiated class. [07:37:09.0603] However, being a HTMLFormElement, all the form logic also applies without additional effort. [07:37:48.0174] Right, I'm saying that's false. [07:38:20.0112] Where does it fail? [07:39:04.0682] I recommend reading up on the web component discussions around inheritance, maybe that will help clear it up. [07:39:23.0696] Sure, do you have a link handy? [07:42:24.0881] Or a starting point. Is it all in the GH issues? [07:48:58.0849] I'll investigate this clue, might take a day or more. https://github.com/whatwg/html/issues?q=is%3Aissue+custom+element+inheritance is not immediately useful. If you find any pointers in the meantime, I'll appreciate it. [07:49:29.0946] * I'll investigate this clue, might take a day or more. https://github.com/whatwg/html/issues?q=is%3Aissue+custom+element+inheritance is not immediately useful. If you find any pointers in the meantime, I'll appreciate it. [07:53:00.0314] kaleidea: WICG/webcomponents is prolly a better starting point; you'll also run into it if you try to implement it in a browser [08:32:11.0469] /me wonders if mek is the one from Google 😊 [08:32:29.0401] /me is pretty close to having a working fork of File System [08:48:01.0552] Well, that went better than expected: https://whatpr.org/fs/1.html [08:50:23.0548] Domenic: I noticed PR Preview didn't have access to websockets yet; now fixed [08:54:17.0670] > * <@annevk:mozilla.org> wonders if mek is the one from Google 😊 yes, that's me. Figured I should finally figure out how this matrix thing works.... Sorry I didn't reply to your email yesterday [08:56:38.0347] mek: that's quite alright, I think I figured out a model that works, although entries are a tad underspecified so maybe not 🙂 [08:56:54.0019] annevk: oh dang, I did miss that step... thanks [08:57:42.0364] Oh I guess one thing that's missing still is a logo [08:59:56.0774] Storage already took the floppy disk :( [09:01:53.0573] mek: would a folder icon of sorts work? [09:02:25.0826] works for me [09:06:35.0206] I should have some time tomorrow / early next week. We need to wait a little longer anyway as one SG rep wanted to confirm something internally [10:42:54.0161] Domenic: Hi, are there WPT for shadow DOM delegatesFocus + autofocus yet? (not talking about