| 18:27 | <annevk> | If people could double check https://github.com/whatwg/url/issues/415#issuecomment-626195881 that’d be great! |
| 20:49 | <shu> | annevk: i apologize for ljharb being unproductive |
| 20:50 | <shu> | annevk: i'd be happy to review the IsHTMLL PR next week if you'd like to reopen it and just ignore his comments, if he comments more |
| 23:42 | <MikeSmith> | wow https://stackoverflow.com/questions/61672829/how-does-chrome-decide-what-to-highlight-when-you-double-click-japanese-text |
| 23:42 | <MikeSmith> | pretty cool |
| 23:47 | <MikeSmith> | > it turns out v8 has a non-standard multi-language word segmenter and it handles Japanese |
| 23:47 | <MikeSmith> | > Windows already have the ability to select the correct word when double clicking on a Japanese word. You don't even need Chrome for this |
| 23:48 | <MikeSmith> | bravo ICU |
| 23:51 | <devsnek> | fetch can use h2c right? |
| 23:54 | <MikeSmith> | devsnek: the fetch spec doesn’t say anything about it, right? |
| 23:54 | <devsnek> | i don't think so |
| 23:55 | <MikeSmith> | I guess it would be orthogonal to fetch behavior |
| 23:55 | <MikeSmith> | I mean, I don’t think there’s anything in specified fetch requirements/behavior that would prevent it |
| 23:55 | <devsnek> | yeah i don't think there's a technical limitation |
| 23:56 | <devsnek> | but i know lately browsers have been limiting things to https |
| 23:56 | <MikeSmith> | ah |
| 23:56 | <MikeSmith> | limiting to secure contexts |
| 23:57 | <MikeSmith> | ..which is some cases can be non-https |
| 23:57 | <MikeSmith> | e.g, localhost case |
| 23:58 | <MikeSmith> | or rather, the 127.0.0.1 case I guess |