On Mon, Jun 10, 2013 at 08:25:57PM -0400, Rick Byers wrote:
> On Mon, Jun 10, 2013 at 5:19 PM, Benjamin Poulain wrote:
>
> > On Mon, Jun 10, 2013 at 7:37 AM, Rick Byers wrote:
> >
> >> There's been discussion / patches in the past for exposing system time as
> >> a separate timestamp on the Event
On Mon, Jun 10, 2013 at 5:25 PM, Rick Byers wrote:
> On Mon, Jun 10, 2013 at 5:19 PM, Benjamin Poulain wrote:
>
>> On Mon, Jun 10, 2013 at 7:37 AM, Rick Byers wrote:
>>
>>> There's been discussion / patches in the past for exposing system time
>>> as a separate timestamp on the Event object (as
On Mon, Jun 10, 2013 at 5:19 PM, Benjamin Poulain wrote:
> On Mon, Jun 10, 2013 at 7:37 AM, Rick Byers wrote:
>
>> There's been discussion / patches in the past for exposing system time as
>> a separate timestamp on the Event object (as IE does). See
>> https://lists.webkit.org/pipermail/webkit-
On Mon, Jun 10, 2013 at 7:37 AM, Rick Byers wrote:
> There's been discussion / patches in the past for exposing system time as
> a separate timestamp on the Event object (as IE does). See
> https://lists.webkit.org/pipermail/webkit-dev/2012-October/022574.html,
> https://bugs.webkit.org/show_bug
There's been discussion / patches in the past for exposing system time as a
separate timestamp on the Event object (as IE does). See
https://lists.webkit.org/pipermail/webkit-dev/2012-October/022574.html,
https://bugs.webkit.org/show_bug.cgi?id=94987 and
http://lists.w3.org/Archives/Public/public-
Hi WebKit,
Next week, I will land a patch changing the way event timestamps are
handled: https://bugs.webkit.org/show_bug.cgi?id=117179
Previously, the PlatformEvent timestamp was ignored when creating a DOM
Event, and a new timestamp was generated with currentTime() when the DOM
Event was create
6 matches
Mail list logo
