| 03:26 | <TabAtkins> | bkardell: Yeah, the <c-> elements were the shortest possible way to write the highlighting markup, which is important when you've got 54k of them in the spec. ^_^ A single additional character adds 50k to the single-page spec! |
| 03:27 | <TabAtkins> | All told I saved nearly a megabyte from the single-page versus my old <span class> markup. |
| 07:11 | <annevk> | mkwst: I think you meant to tag naskooskov not nasko |
| 07:31 | annevk | decided to edit in place |
| 09:24 | <hsivonen> | in it a known problem that the wpt.fyi numbers are very broken, at the moment? https://wpt.fyi/results/?label=experimental |
| 09:44 | <Ms2ger> | That's weird, 98a2a02 is in a PR, not on master |
| 09:44 | <Ms2ger> | foolip, ^ |
| 10:46 | <foolip> | hsivonen: you have to add &label=master |
| 10:48 | <foolip> | hsivonen: or better just go to wpt.fyi/ to get the default query, which is now experimental Chrome, Firefox and Safari and stable Edge |
| 11:12 | <hsivonen> | foolip: thanks |
| 11:40 | <annevk> | foolip: I see something weird |
| 11:40 | <annevk> | foolip: https://wpt.fyi/results/encoding?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned |
| 11:40 | <annevk> | foolip: the encodeInto test is failing in Chrome, but it does pass all IDL tests |
| 11:40 | <annevk> | foolip: that combination should be impossible |
| 11:41 | <annevk> | foolip: (and testing it locally I cannot reproduce) |
| 11:41 | <foolip> | annevk: it says CRASH for Chrome |
| 11:42 | <foolip> | annevk: so that's not a contradiction at least. does it work with `./wpt run` locally? |
| 11:42 | <annevk> | foolip: I just opened it |
| 11:42 | <annevk> | foolip: thanks for clarifying |
| 11:43 | <annevk> | foolip: I don't have enough software installed for ./wpt run |
| 14:16 | <bkardell> | tabatkins: yeah, I get the basic idea... I'm curious tho... those savings are pre-gzip, right? how real are the savings/where are they post gzipping? It seems to me they should gzip pretty similarly? Are there memory savings somehow? Seems like strings for tag names would all point to the same memory... because we store the source whole original source maybe? |
| 14:39 | <annevk> | MikeSmith: ^^ |
| 16:59 | <jwalden> | does anyone know how different browser and OS networking stacks determine an encoding for PAC scripts? I know what modern Firefox does, but I'm not sure what anything else uses, except that wholly ASCII scripts are all but guaranteed to be interpreted as ASCII |
| 17:35 | <annevk> | jwalden: if you think we should have a definition, file an issue against whatwg/fetch with a description for Fx? I can take it from there later |
| 17:35 | annevk | only learned about this rather weird thing the other week |
| 17:35 | <jwalden> | annevk: this was for approximately vague curiosity, I was going to update Wikipedia's mentioning of its encoding if anyone knew more than I did :-) |
| 17:36 | <jwalden> | I changed Gecko to allow PAC scripts to be UTF-8 semi-recently (and if they don't validate as UTF-8 they get treated as Latin-1), and Wikipedia til half an hour ago just said UTF-8 wasn't really supported |
| 17:37 | <jwalden> | none of this is really all that important in reality, I expect |
| 17:37 | <annevk> | Until someone depends on it and we cannot unship… |
| 17:38 | <jwalden> | well, PAC is a networking stack-level thing, it's sort of beneath anything the web sees |
| 17:38 | <jwalden> | an IETF RFC would be the rough place for it if it were going to be truly formalized somewhere, I think |
| 17:39 | <annevk> | Fair |