Ping. Any thoughts from folks familiar with the history API definition?
This proposal resolves a high-profile issue we've received from a number of
major websites. As Majid said, mobile-optimized websites are being forced
to choose between the fullscreen UX users expect from websites on phones
On Wed, Aug 12, 2015 at 12:37 PM, Majid Valipour maji...@chromium.org
wrote:
Does anybody know if there was any specific reasons behind the current
order?
Are the reasons you discovered yourself not sufficient?
They are pretty compelling but was wondering if there is anything I am
Sounds great to me. I agree this is an important scenario. *Ian*,
thoughts? Is anyone actively working on worker-thread canvas in blink at
the moment?
Note that Ian's CompositorWorker prototype
https://docs.google.com/document/d/18GGuTRGnafai17PDWjCHHAvFRsCfYUDYsi720sVPkws/edit#
currently
, 2015 12:47
To: Rick Byers
Cc: wha...@whatwg.org
Subject: Re: [whatwg] DOM Events Proposal: EventListenerOptions
'mayCancel' for improved scroll performance
Is it not possible for Javascript engines to statically determine if
preventDefault() is called by an event handler?
For example
On Thu, Jul 9, 2015 at 9:49 AM, Philip Jägenstedt phil...@opera.com wrote:
On Thu, Jul 9, 2015 at 3:44 PM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 9:39 AM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 9:05 AM, James Ross
w3c-20040...@james
On Thu, Jul 9, 2015 at 11:22 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers rby...@chromium.org wrote:
I think there's a big opportunity to substantially improve scroll
performance on the web in the relatively short term by doing something
On Thu, Jul 9, 2015 at 11:05 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jul 9, 2015 at 3:58 PM, Rick Byers rby...@chromium.org wrote:
I'd love to hear other ideas!
Well, we have had some discussions in the past about introducing a
better event API:
https://gist.github.com
On Wed, Jul 8, 2015 at 4:04 PM, Olli Pettay o...@pettay.fi wrote:
On 07/08/2015 10:12 PM, Rick Byers wrote:
[Cross-posted to www-...@w3.org - please let me know if there's a better
way to account for the DOM spec duality]
In Chromium we've long worked hard at maximizing scroll performance
On Thu, Jul 9, 2015 at 11:40 AM, Philip Jägenstedt phil...@opera.com
wrote:
On Thu, Jul 9, 2015 at 5:30 PM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 11:22 AM, Anne van Kesteren ann...@annevk.nl
wrote:
On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers rby...@chromium.org wrote
On Thu, Jul 9, 2015 at 12:40 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/9/15 8:42 AM, Philip Jägenstedt wrote:
Would there be any way to feature detect support for EventListenerOptions
as the third
argument?
Yes. You call addEventListener and pass an object that has getters for
the
On Thu, Jul 9, 2015 at 2:21 PM, Jonas Sicking jo...@sicking.cc wrote:
Speaking
of that, having a new function makes it an option to let mayCancel be
false by default, compat-wise at least.
That's a good question regardless of which approach we take. Filed
On Thu, Jul 9, 2015 at 2:57 PM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/9/15 1:32 PM, Rick Byers wrote:
Done. How does example 2 look now
On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/9/15 1:32 PM, Rick Byers wrote:
Done. How does example 2 look now?
http://rbyers.github.io/EventListenerOptions/EventListenerOptions.html
On Thu, Jul 9, 2015 at 12:47 PM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 12:40 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/9/15 8:42 AM, Philip Jägenstedt wrote:
Would there be any way to feature detect support for
EventListenerOptions as the third
argument?
Yes
On Thu, Jul 9, 2015 at 2:59 PM, Elliott Sprehn espr...@chromium.org wrote:
On Thu, Jul 9, 2015 at 11:52 AM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 2:21 PM, Jonas Sicking jo...@sicking.cc wrote:
...
I agree 100% with this principle. Changed mayCancel to default
[On vacation now with only a phone - so apologies for the brevity and
top-posting]
What Anne describes is perfect! I'm not hung up on the value of cancelable
itself - some internal bit on Event that makes preventDefault a no-op (or
event throw) during listener invocation is fine with me (and I
[Cross-posted to www-...@w3.org - please let me know if there's a better
way to account for the DOM spec duality]
In Chromium we've long worked hard at maximizing scroll performance, with
scroll-blocking DOM events (wheel and touchstart in particular) being by
far the biggest source of scroll
On Thu, Jul 9, 2015 at 9:05 AM, James Ross w3c-20040...@james-ross.co.uk
wrote:
Date: Thu, 9 Jul 2015 14:42:07 +0200
From: phil...@opera.com
I think this looks like a very promising approach. Would there be any
way to feature detect support for EventListenerOptions as the third
On Thu, Jul 9, 2015 at 9:39 AM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 9:05 AM, James Ross w3c-20040...@james-ross.co.uk
wrote:
Date: Thu, 9 Jul 2015 14:42:07 +0200
From: phil...@opera.com
I think this looks like a very promising approach. Would there be any
reason.
Thanks,
Rick
On Wed, Jul 8, 2015 at 3:12 PM, Rick Byers rby...@chromium.org wrote:
[Cross-posted to www-...@w3.org - please let me know if there's a better
way to account for the DOM spec duality]
In Chromium we've long worked hard at maximizing scroll performance, with
scroll
On Thu, Jul 9, 2015 at 6:03 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 9, 2015 at 12:06 PM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 2:57 PM, Rick Byers rby...@chromium.org wrote:
On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking jo...@sicking.cc wrote
21 matches
Mail list logo