How are non-text/css responses handled? about construct-stylesheets

[TakayoshiKochi]

Good catch, I don't think we have to support legacy behavior like quirks mode, as this is for a new API.

[TakayoshiKochi]

As #25 concludes disallowing @import, let me close this.

[bzbarsky]

Um... I don't see a conclusion in #25 that "disallows import". Have you talked to the CSSWG about this? You can't just go creating your own separate CSS syntax willy-nilly!

[TakayoshiKochi]

Well, sorry for the wording "conclusion" - it was not really a consensus.

[tabatkins]

Ignoring #25 for the moment tho, I agree that we shouldn't support non-text/css responses in this API.

[TakayoshiKochi]

@tabatkins shall we describe the response type restriction for each spec that involves any loading, or is there good one place to put all relevant information?

[tabatkins]

I suspect that each spec should define their type restrictions; there's a lot of places where things are loaded, so having a single point that tries to define all of them is probably bad. But I think @annevk would have a more useful opinion on that.

[annevk]

I'd actually expect a single point to be defined in CSS somewhere, suitably parameterized. Especially for security-sensitive code like loading you don't want too many independent decision makers.

[rakina]

#35 resolves this - We don't handle non-text/css.