| 03:44 | <Domenic> | The important thing is that they come in before document creation. A meta tag doesn't work for that. |
| 03:44 | <Domenic> | Because the process the document is created in depends on whether the headers are present or not |
| 08:07 | <bakkot> | ah, hm. does the content-type attribute not also need to come in before document creation? |
| 08:07 | <bakkot> | I guess that one is kind of special though |
| 08:09 | <bakkot> | still, seems like one could reasonably say "if you encounter a <meta http-equiv="COOP"> in the first 1024 bytes, and you are not currently in the corresponding COOP state, throw away the document and start again in that state |
| 17:49 | <Domenic> | Content-Type does need to come before document creation. |
| 17:50 | <Domenic> | Throwing away documents seems like something useful for demo sites but not something we'd want to encourage as a general tool for the wider web, just for perf/resource consumption reasons. |
| 18:31 | <bakkot> | Yeah, that's reasonable. I'm mostly coming at this from, I am often in a position to control the content of a document but not the headers it's served with, and so I end up resorting to stuff like the service worker hack mentioned above, which is definitely more expensive and also harder to integrate with other things (because service workers don't compose) |
| 18:31 | <bakkot> | This seems like something which comes up a fair bit, in my experience with teams at other companies, but I don't know if it's actually worth worrying about |
| 18:34 | <bakkot> | (and the current context is just that I wanted to make SAB work on github pages, which, while it's something I care about, is almost certainly not worth worrying about for the web platform) |
| 20:34 | <Domenic> | So many web platform features have gotten worse because GitHub pages won't let you set headers :( |