| 08:38 | <Ms2ger> | - RESOLVED: Add a new url function that accepts only <string>, name tbd (Issue #451: Add url() alias that does not accept unquoted URLs) |
| 08:40 | <annevk> | I'm pretty sure they thought they had already resolved this |
| 08:41 | annevk | whispers something about tests, reviewed PRs, and implementer signoff |
| 08:52 | <annevk> | Domenic: any idea why https://pthatcherg.github.io/web-transport/ invents new stream types? |
| 13:09 | <Domenic> | annevk: not really sure... I think they have the feedback that it's bad and won't get far, but I haven't seen much movement on the spec level. |
| 13:11 | <annevk> | kk |
| 23:14 | <hyspace> | Hello everyone |
| 23:14 | <hyspace> | I have a question about html tokenization |
| 23:16 | <hyspace> | In https://html.spec.whatwg.org/multipage/parsing.html#decimal-character-reference-state, we need to Multiply the character reference code by 10. Add a numeric version of the current input character (subtract 0x0030 from the character's code point) to the character reference code. |
| 23:16 | <hyspace> | The spec did not say what if the range is beyond range of int32 |
| 23:17 | <hyspace> | if we keep multiply, it is possible that the character reference code will go back to Unicode range |
| 23:20 | <hyspace> | For example, if we use Int32 type for character reference code, we can craft a input as � which will beyond the range of Int32 and goback to Unicode range and become 'P' character |
| 23:46 | <Domenic> | hyspace: I haven't looked at this particular instance, but in general the spec operates on mathematical numbers, so there's no wrapping. |
| 23:47 | <Domenic> | Thus you end up in the "If the number is greater than 0x10FFFF" state |
| 23:49 | <hyspace> | Domenic: In https://html.spec.whatwg.org/multipage/parsing.html#hexadecimal-character-reference-state chapter we do not check range, so when we are in Numeric character reference end state, we will end up using overflowed number |
| 23:49 | <Domenic> | hyspace: there is no such thing as an overflowed number, in the spec |
| 23:50 | <Domenic> | I understand you might be implementing this in a language that has finite storage, but the spec does not :) |
| 23:54 | <hyspace> | Domenic: Thanks |