| 07:15 | <noamr> | morning annevk! still not a lot of responses on the orientation-cors thing... for now I updated the resolution PR https://github.com/whatwg/html/pull/5574 to be on the safe side and only support origin-clean images when reading metadata. WDYT? |
| 07:37 | <annevk> | noamr: I think we need some kind of conclusion among implementers on the way forward |
| 07:38 | <annevk> | GitHub down again? What is going on over there? |
| 07:47 | <noamr> | yea seems like it is |
| 08:13 | <noamr> | it's back now it seems |
| 08:20 | <noamr> | yoav: can I ask for your help again in concluding https://github.com/w3c/csswg-drafts/issues/5165 from chromium's perspective? It seems like it's blocked on people not being convinced that reading a cross-origin image's orientation/resolution is a same-origin policy violation, but also not concluding the other way - so we currently have a feature in the wild that allegedly violates same-origin policy (image-orientation: |
| 08:20 | <noamr> | none CSS), and we can't proceed with other EXIF-based features. TabAtkins, maybe you have an opinion on this? |
| 08:24 | <noamr> | I was personally convinced by annevk that reading an image's orientation/resolution is an origin-policy violation, and though it's hard to imagine exactly how this information can be (ab)used, we should err on the careful side and ignore EXIF metadata for images that are not origin-clean, at least for the new uses (EXIF resolution). |
| 09:26 | <annevk> | Ms2ger: you around? Do you happen to know the equivalent to Class.prototype.method.call for getters? |
| 09:28 | <annevk> | Object.getOwnPropertyDescriptor(MessageChannel.prototype, "port1").get.call(c) seems to work, but I'm not sure if I missed something now |
| 09:34 | <Ms2ger> | Heya |
| 09:35 | <Ms2ger> | I think that's the shortest approach, yeah |
| 09:45 | <Ms2ger> | gsnedders, congrats! |
| 09:47 | <annevk> | oh cool, congrats gsnedders |
| 09:48 | <jgraham> | I see they left their sense of logic at the door! |
| 09:49 | <jgraham> | (congrats ;) |
| 10:09 | <gsnedders> | yeah, guess y'all have to put up with me still |
| 10:43 | <MikeSmith> | gsnedders: very happy news |
| 10:43 | <MikeSmith> | Laissez les bons temps rouler |
| 10:44 | <MikeSmith> | the train keeps a’rollin |
| 16:42 | <astearns> | congrats, gsnedders! |
| 19:01 | <EveryOS> | Just joined, and irc topic says >Please leave your sense of logic at the door, thanks! |
| 19:01 | <EveryOS> | Given that this is a meta channel for WhatWG's specifications, I was expecting people would be more serious. |
| 19:09 | <Domenic> | It sounds like you're not properly following the IRC topic's instructions, then. |
| 20:22 | <EveryOS> | Writing an HTML parser is such a nightmare, I can only feel bad for the poor soles who write Ecma 262 implementations (which are even harder to write, I assume) |
| 20:23 | <EveryOS> | I made a type, but this is IRC so I can't fix it |
| 20:23 | <EveryOS> | *typo |
| 21:34 | <yoav> | noamr: I commented on the issue a week ago. I think CORS would be too restrictive in this case, but waiting for security folks to weigh in |
| 22:59 | <shu> | could someone point me to where the code that adds the MDN sidebar icons is? i'm having trouble understanding what it uses to key the MDN page to link |