| 11:48 | <yoav> | Hey! HTML question - I want to move the image-specific Client Hints definitions away from the Client Hints IETF draft and into one of the web specs. IMO, the natural place for that would be the HTML spec. I want to see if: a) folks here agree? b) If so, where? somewhere in https://html.spec.whatwg.org/#images? Or elsewhere? |
| 12:13 | <annevk> | yoav: I guess because they are to be set during image fetching? |
| 12:14 | <annevk> | yoav: HTML does own that at the moment so that'd probably make sense, though maybe it should move to Fetch long term as there's a bunch of specifications that need to use image fetching, HTML being one of them |
| 12:14 | <yoav> | The actual setting would be in Fetch, but I want to define what those features are, and HTML's image section seems to me like the best fit. There's also some interaction between Content-DPR and image density which definitely needs to be defined there |
| 12:15 | <yoav> | If the image loading section moves to Fetch, it makes sense for that to move with it |
| 12:15 | <annevk> | yoav: is image density HTML-specific? |
| 12:19 | <yoav> | The concept of https://html.spec.whatwg.org/#density-corrected-intrinsic-width-and-height is something I know exists in HTML and CSS, but not aware of it elsewhere |
| 12:19 | <yoav> | (although it seems like it could be applicable elsewhere as well) |
| 12:21 | <yoav> | Content-DPR will probably need to set the https://html.spec.whatwg.org/#current-pixel-density |
| 12:23 | <annevk> | yoav: CSS is what I'm thinking of primarily with regards to the algorithm needing abstraction, though also icon fetches and such |
| 12:23 | <yoav> | oh, OK |
| 12:23 | <yoav> | that same concept is applicable there |
| 12:25 | <yoav> | through image-set or through Client Hints |
| 12:25 | <annevk> | yoav: I guess at least through tests we can ensure both are covered, but it'd be nice if you could find someone to finally give image fetching some love overall so it's less of a neglected mess |
| 12:26 | <annevk> | yoav: anyway, also sounds like HTML is the place |
| 12:26 | <yoav> | cool, thanks! |
| 12:27 | <yoav> | sounds like that kind of image loading love would be something that would help the larger goal of CSS/Fetch integration, right? |
| 12:28 | <ondras> | 9/w 42 |
| 12:28 | <ondras> | damn sorry |
| 12:30 | <yoav> | that's something I discussed a bit with JakeA. Agree that it would be good to move that forward. Not sure who can take that on and when tho |
| 14:51 | <Ms2ger> | annevk, I'm starting to feel like we should explicitly define separate IDL and ES objects for "platform objects", what do you think? |
| 14:53 | <annevk> | Ms2ger: I'm not sure I fully understand, but being able to use the term for both would be good |
| 14:53 | <annevk> | Ms2ger: although maybe it's not needed, "is a platform object" is always correctly used |
| 14:54 | <annevk> | Ms2ger: it's mostly that things building on "platform object" also need to be available easily from IDL objects (or perhaps primarily) |
| 15:55 | <annevk> | Domenic: could you review https://github.com/web-platform-tests/wpt/pull/15649 while you're going through things? |
| 15:55 | <annevk> | (the failure doesn't matter apparently) |
| 15:56 | <Domenic> | Sure, will be a couple hours |
| 15:59 | <annevk> | ta |
| 16:00 | <Domenic> | Or, now; I misremembered my meeting time by an hour -_- |
| 16:14 | <Domenic> | Blocked https://github.com/zafar4u org-wide due to repeated (machine-generated?) spam |
| 16:23 | <annevk> | Domenic: I think you read over my comment in https://github.com/whatwg/html/pull/4415 that we cannot grab this stuff from platform objects (which are ECMAScript objects) |
| 16:24 | <annevk> | Domenic: it's now no longer tracked anywhere at least |
| 16:24 | <Domenic> | Oh, sorry about that |
| 16:24 | <Domenic> | My opinion is we should be OK blurring the lines, but yeah, we should track it |
| 16:24 | <Domenic> | I'll open a Web IDL issue in penance |
| 16:33 | <annevk> | Domenic: I filed https://github.com/whatwg/html/issues/4418 |
| 16:33 | <annevk> | I forgot to look if you replied |
| 16:33 | <Domenic> | Hmm I filed https://github.com/heycam/webidl/issues/680 |
| 17:06 | <annevk> | Domenic: mostly worried due it being a security boundary of sorts, so feels like we should be explicit about bridging |
| 17:58 | <zcorpan> | hsivonen: MikeSmith: what's the url to the parse tree tool on validator.nu ? |
| 17:59 | <zcorpan> | also can it be made discoverable in About? |
| 18:01 | <zcorpan> | found it https://parsetree.validator.nu/ |