- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 May 2018 23:57:00 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Define which subresources block the DOM load event`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Define which subresources block the DOM load event<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1088<br> <dael> TabAtkins: fantasai requested to figure out what spec it goes in<br> <dael> Rossen_: whatwg?<br> <dael> gsnedders: we resolved in values and units<br> <dael> TabAtkins: add proposed dom events to v&u. Okay.<br> <dael> fantasai: Yes. Ana added the agenda+ I don't know why.<br> <fantasai> s/Ana/Anne/<br> <dael> Rossen_: I'm okay to move on. We can come back if there's a need to reoslve.<br> <dael> dbaron: I think there's stuff to discuss here.<br> <dael> Rossen_: What would you like to discuss or does it stay in GH?<br> <dael> dbaron: GH may be fine. There's a bunch of non-interop but we have space to converge if we agree to try and progress in that direction. Example @import blocks if it's one level deep, but not further and other browsers never block. I think we should be consistant and not having different behavior at different depths.<br> <dael> dbaron: But we can discuss more on issue.<br> <dael> Rossen_: I think that's better.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1088#issuecomment-386156433 using your GitHub account
Received on Wednesday, 2 May 2018 23:57:08 UTC