| 01:20 | <sideshowbarker> | sideshowbarker: i guess we could include some text for given entries in compat like, prefer this standard thing instead (not sure how useful that is, but it wouldn't be hard) |
| 03:38 | <karlcow> | Compat spec has been conceived as a transition document. Nothing in there should be considered the source of truth. It just attempts to document things that need to be taken elsewhere in a proper spec if the spec wants to take it on. |
| 03:39 | <karlcow> | And yes having section pointing to the right place when it has been described in a proper spec would be great. |
| 03:41 | <karlcow> | sideshowbarker:
|
| 03:41 | <karlcow> | do you mean on the authoring side of things? |
| 03:41 | <karlcow> | or implementation side of things? |
| 03:42 | <karlcow> | Definitely everything which is mentioned in compat spec should not be perceived as ok to write code. |
| 03:50 | <sideshowbarker> | howdy karlcow yeah I meant strictly the author side of things |
| 14:35 | <EveryOS> | My HTML parser is 1400 lines and still fails to implement a lot of the parsing spec. That is one really long spec xD. My parser is worth about 14% of my project's code. Wow, that spec is long |
| 14:44 | <jgraham> | Tokei tells me that html5lib-python is ~13,000 lines of Python code (exclusing comments, but including the test harness and so on) |
| 14:46 | <jgraham> | Weirdly html5ever has the same number of lines of Rust to within 2% |
| 14:47 | <jgraham> | (as html5lib has of Python) |
| 14:49 | <jgraham> | The validator.nu HTML parser seems to be about 28,000 lines of Java (also including infrastructure, etc.) |
| 14:49 | <EveryOS> | Wow, that's giant Looks like I got my work cut out. (I still need to learn Rust btw) |
| 14:52 | <EveryOS> | My unit tests also completely fail to exist So I will have to write those someday. |
| 14:54 | <jgraham> | You know about https://github.com/html5lib/html5lib-tests/ ? |
| 14:59 | <EveryOS> | You know about https://github.com/html5lib/html5lib-tests/ ? But I do know about https://wpt.live/ I'll have to star that other one. |
| 19:49 | <bkardell> | Domenic: fwiw on https://github.com/openui/open-ui/issues/380#issuecomment-894404741 I think this is referring to HTMLOptionsList |
| 20:42 | <Domenic> | Domenic: fwiw on https://github.com/openui/open-ui/issues/380#issuecomment-894404741 I think this is referring to HTMLOptionsList |
| 20:45 | <bkardell> | Domenic: the group had some decision to see if we could articulate principles about why we would choose to match or not and write them down, I think it was an attempt to summarize them.. it's possible I am wrong anyway- I was thinking that in the call it was brought up that you mentioned that, for example, the new select-like element should probably not reuse HTMLOptionsCollection... In fact, it is probably the comment you made on the issue https://github.com/openui/open-ui/issues/380#issuecomment-891268912 |
| 20:46 | <bkardell> | s/list/collection |
| 20:48 | <bkardell> | the group had some decision to see if we could articulate principles about why we would choose to match or not and write them down, I think it was an attempt to summarize them |
| 20:54 | bkardell | apologizes for multiple editing attempts to get that right if anyone was watching :) |
| 21:39 | <Domenic> | Yeah, to me it felt like reading the minutes they didn't really discuss the API at all... |