Re: [csswg-drafts] [css-cascade-4] Revert at computed-value time (#4155)

> They're crazy scenarios.

Hehe, great assessment.

@FremyCompany I'm not worried about the implementation difficulty of this as it stands currently. My worry is that we're setting a potentially dangerous precedent on the spec level.

The act of computing the value of force-color-adjust means the computed value of all the properties it depends on must also be known. I would then consider it _too late_ to revert any of those dependencies to a different computed value, as it would mean there are two answers for what the computed value is.

I'm well aware that force-color-adjust can't _currently_ depend on anything that will be reverted. So for now that works. But this also sets a precedent that reverting at computed-value-time is OK, and reinforces the unfortunate precedent set by css-logical that computed-value-time results can affect cascade behavior, and that is the part that worries me.

But since I seem to be the only one sufficiently worried about it (and I don't really have a better solution), I think it makes sense to close this issue and live with it. If we ever manage to create a world where the bad situation is possible, hopefully we can invent some mitigation to maintain consistency in the cascade.




-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4155#issuecomment-631800909 using your GitHub account

Received on Thursday, 21 May 2020 00:05:06 UTC