[Webkit-unassigned] [Bug 92009] Stop using currentTime()

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=92009


Yong Li <yoli at rim.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|WebKit condition variable   |Stop using currentTime()
                   |should use monotonic clock  |
          Component|JavaScriptCore              |WebKit Misc.
                 CC|                            |abarth at webkit.org,
                   |                            |darin at apple.com,
                   |                            |eric at webkit.org




--- Comment #2 from Yong Li <yoli at rim.com>  2012-07-27 14:21:22 PST ---
Even though monotonicallyIncreasingTime() has been introduced for a while, WebKit is still using currentTime at so many places where monotonic time is expected.

It is too hard for one to fix all of these without breaking any port. For example, changing DOM event's timestamp to use monotonicallyIncreasingTime() could break plugins. Making ThreadCondition use monotonic clock will break WebKit2.

BTW, Web Worker's timer is using currentTime(), so it works well with ThreadCondition currently.

But the problem is still there: what if user adjusts system date to 1 month earlier?

Any idea how we can get this thing done smoothly?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.