| 09:54 | <annevk> | So I haven't really looked into TPAC yet as much as I should. Does one need to register in order to attend breakout sessions? |
| 10:10 | <jgraham> | I mean it says you're supposed to register, but who knows if it's enforced |
| 10:10 | <jgraham> | It's at least not hard to do |
| 19:24 | <TabAtkins> | ...how do I actually refer to a resource that is CORS-cleared? |
| 19:25 | <TabAtkins> | Like, what term do I use to distinguish between "this cross-origin resource is okay" vs "it's not"? |
| 19:25 | <TabAtkins> | The Fetch spec doesn't seem to give me anything. |
| 21:05 | <Domenic> | TabAtkins: "opaque response" vs. not? |
| 21:06 | <TabAtkins> | Term does not exist; closest is "opaque filtered response" <https://fetch.spec.whatwg.org/#concept-filtered-response-opaque>;, is that what I should be deciding on? |
| 21:19 | <Mek> | closest is "a response whose type is opaque" |
| 21:19 | <Mek> | but what are you actually trying to do... |
| 21:29 | <TabAtkins> | cross-origin images that haven't been cleared thru CORS need to censor their orientation/resolution data in certain ways |
| 22:25 | <zcorpan> | TabAtkins: I think (opaque filtered response OR opaque-redirect filtered response) - but HTML doesn't use those terms: https://html.spec.whatwg.org/multipage/urls-and-fetching.html#cors-same-origin |
| 22:27 | <zcorpan> | annevk: ^ |
| 22:37 | <TabAtkins> | Ah, I like HTML's terms. |