| 09:22 | <Ms2ger> | annevk, ping re wpt #7574 |
| 09:23 | <annevk> | Ms2ger: yeah? |
| 09:24 | <Ms2ger> | You think it makes sense to land with my edit? I'm not sure how well-specified stuff is with the window after removing the iframe? |
| 09:25 | <Ms2ger> | Or should I just land the document parts and leave the new test until we figured out the right behaviour |
| 09:25 | <annevk> | Ms2ger: I think for window.location it is defined, but I also think it's already tested per that issue I pointed to |
| 09:25 | <annevk> | Ms2ger: it's just that only Firefox implements it so far and other browsers haven't really investigated whether they can align |
| 09:26 | <annevk> | Ms2ger: so I'm not sure we need that new test, the other parts look okay |
| 09:28 | <Ms2ger> | Even better |
| 10:43 | <annevk> | So many MIME type parser bugs |
| 10:43 | <Ms2ger> | So very unsurprised |
| 11:21 | <gsnedders> | In other news, Scotland is overcast. |
| 12:28 | <annevk> | hsivonen: is there a canonical document for the UTF-16 being superior to UTF-8 due to size argument? |
| 13:15 | <annevk> | So, I've written a MIME type parser: https://github.com/whatwg/mimesniff/pull/36 |
| 13:15 | <annevk> | I also have some ideas about how to refine how we define MIME types (basically copy what we do for URLs) |
| 13:16 | <annevk> | Input appreciated, including "fine, please proceed", "no, you should do X", etc. |
| 13:16 | nox | files bug because annevk's parser isn't written in Rust. |
| 13:17 | <annevk> | nox: I'd love to see the one written for Servo |
| 13:18 | <nox> | annevk: There is one, which had massive breaking changes in its last major version so Servo still lags behind. :( |
| 13:18 | <nox> | https://docs.rs/mime |
| 13:24 | <annevk> | nox: that library looks too strict for the web |
| 13:25 | <nox> | annevk: On which part? |
| 13:27 | <annevk> | nox: throwing parse errors when there's something wrong with a parameter |
| 13:28 | <nox> | annevk: I've heard at least once that we weren't too sure whether that is supposed to be an error or not. |
| 13:43 | <annevk> | nox: not sure if you all keep track of such a list, but I would expect any dependency that doesn't have reverse engineering of other browsers involved in it somehow to probably not be suitable |
| 13:44 | <annevk> | nox: in particular any IETF RFC tends to not reflect implementation reality |
| 13:45 | <nox> | Yeah I know that. |
| 17:38 | <Domenic> | TabAtkins: for my own edification, why are UA stylesheets better "when a particular value isn't good globally"? I don't really understand the functional difference between initial value and UA stylesheet. |
| 17:40 | <annevk> | Domenic: e.g., when you want <b> to be blue, but normally you want things to be black |
| 17:40 | <annevk> | Domenic: if we actually want it for *|*:root in this case though and the thing inherits, I'm not sure what the difference is |
| 17:41 | <annevk> | Domenic: well, I guess *|*:root would not apply to shadow trees, but not sure if that's a feature or not |
| 17:42 | <Domenic> | I think UA stylesheets apply to shadow trees, but maybe :root doesn't apply to shadow roots? |
| 17:43 | <annevk> | Domenic: the main question is whether things inherit into a shadow trees, maybe they actually do |
| 17:43 | <annevk> | I really don't know enough about this anymore by heart 😟 |
| 18:00 | <TabAtkins> | annevk got it. Also yes, UA stylesheets apply in shadow trees, and inheritance crosses shadows by default. |
| 18:01 | <TabAtkins> | So yeah, UA stylesheet is for when a value is a good default for some elements only, or only for SVG vs HTML, etc. |
| 18:01 | <TabAtkins> | Also :root applies to all the top-level elements in a shadow tree. |
| 18:02 | <TabAtkins> | Oh wait, that's not true. |
| 18:05 | <TabAtkins> | But anyway, yeah, the only reason to ever run a *|*:root selector in the UA stylesheet is if, for some reason, you want it not to apply when people use "all" to block inheritance. |
| 18:07 | <Domenic> | Oh, I see, UA stylesheet is for when you need a more specific selector; you can't say "initial value for X elements". That makes sense. |
| 18:30 | <TabAtkins> | Yup, exactly. |