- From: Vaughan Hilts via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Apr 2021 05:12:13 +0000
- To: public-css-archive@w3.org
Thanks @atoic. I agree that v2 makes it easier to work with but still doesn't address things like "I made my height bigger in response to being squeezed width wise" or "I use negative margins", but they are in use by many web apps today (and unfortunately why I am now faced with the dilemma of finding resolutions now...) My understanding is correct, yes? The border-box solution simply solves the "I made my padding and/or border-box more compact to accomadate my size and and my real size didn't actually change" problem, right?
As for #5023, I don't mind taking a look but it will likely take some time for me to figure out what's best here. Is it so bad to just simply print a verbose warning to the console like Chrome does today and call it a day? ;) I know these things are nuanced.
I think you have the gist of it though, we need a way to selectively configure the notifications being dropped. Part of this comment ("Let's define a mechanism to instruct the engine that it's OK to bail after a single dispatch") is what I was trying to express in many words, that you did in a few. This problem is a lot invasive if on the corner cases a developer had a way of just saying "yeah, I can guarantee the layout will have settled and the dropped notification is no big deal"
I appreciate you taking the time to reply.
--
GitHub Notification of comment by hilts-vaughan
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6173#issuecomment-812321719 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 April 2021 05:12:15 UTC