- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Apr 2018 00:43:51 +0000
- To: public-css-archive@w3.org
I think having behavior differences between `@import` and `<link>` (which have been described as equivalent for years) should be avoided if at all possible. (And it sounds like it's possible; it seems like the plan is that recursive `@import` should also block load, which I strongly support since it matches `<link>` and simple `@import`.) Another bit that should be defined is when restrictions on use of style sheets such as `media` or any alternate style sheet mechanisms (`title` / `alternate` / etc., though I'm not sure what the current state of the spec is) block onload. This came up recently in a Mozilla bug pointing out lack of interop in terms of whether loading of print (or other not-currently-used-medium) style sheets blocks onload, and I think that bug pointed to a whatwg/html issue, but I can't currently find either... (I think our conclusion is that Gecko should block the load event less in those cases to match Chrome, but also that the spec should define what exactly those cases are.) -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1088#issuecomment-384124439 using your GitHub account
Received on Wednesday, 25 April 2018 00:43:59 UTC