W3C home > Mailing lists > Public > public-css-bugzilla@w3.org > February 2012

[Bug 16016] Place some constraints on when computed values must be deemed to change

From: <bugzilla@jessica.w3.org>
Date: Fri, 17 Feb 2012 19:17:28 +0000
To: public-css-bugzilla@w3.org
Message-Id: <E1RyTJA-0006AT-5z@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16016

L. David Baron <dbaron@dbaron.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dbaron@dbaron.org

--- Comment #1 from L. David Baron <dbaron@dbaron.org> 2012-02-17 19:17:27 UTC ---
(In reply to comment #0)
> Can we at least require that if you make a change, then a setTimeout() function
> makes another change, they can't be simultaneous?  There should be at least one
> way for authors to change styles and know it's not simultaneous.

I think that's too strong -- it prevents implementations from coalescing
changes that happen within the same screen refresh, for example.

I think if we wanted to say something we'd want to say something about the
previous style having been visible to the user.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 17 February 2012 19:17:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 17 February 2012 19:17:34 GMT