- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Apr 2018 12:33:02 +0000
- To: public-houdini-archive@w3.org
The Working Group just discussed `Make paint invalidation non-normative or something?`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Make paint invalidation non-normative or something?<br> <dael> github: https://github.com/w3c/css-houdini-drafts/issues/447<br> <dael> iank_: Pointed out by Alan Jeffrey that...basically we have a section of the paint spec that says how invalidation works.<br> <dael> iank_: If you have a paint validation and the style changes you have to make changes and you invalidate. It was pointed out you don't need that because you have the caching function. The caching is all the input are the same. So we could drop the whole paint invalidation section and rely on the caching and that engines can be cleverer.<br> <dael> iank_: Thoughts?<br> <dael> iank_: We could make this non-normative and say you can do validation this was or rely on caching step.<br> <dael> dbaron: I have a valgue memory when I looke d awhile ago I thought this section was more complex then it needed to be.<br> <dael> iank_: Maybe. I think I changed it since then where we moved the invalidation to individual pain functions. [reads]<br> <dael> iank_: WE could drop this and let the engines do smarter. Or make the whole section non-normative saying that engines can add incalidation.<br> <dael> shane: It would be much faster [missed]<br> <dael> Rossen: Leaning toward making it non-normative?<br> <dael> iank_: I'm fine with that. I think it should still be in the spec because I think engines will do that.<br> <dael> krit: Is there something we should add to ensure that everything is correct?<br> <dael> iank_: We did that.<br> <dael> smfr: The invalidation isn't exposed.<br> <dael> iank_: Yeah.<br> <dael> iank_: as a webkit engine impl your thoughts?<br> <dael> smfr: I don't think there's value to this section. Is there other text that spec when something becomes invalid?<br> <dael> iank_: No<br> <dael> smfr: You need that. You need to desc imputs that trigger<br> <dael> iank_: We've got that in the cache step. The paint size and similar.<br> <dael> Rossen: Objections to dropping section 2: paint invalidation ?<br> <dael> rESOLVED: drop section 2: paint invalidation<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/447#issuecomment-379735569 using your GitHub account
Received on Monday, 9 April 2018 12:33:06 UTC