On Thu, Jul 9, 2015 at 6:03 PM, Jonas Sicking wrote:
> On Thu, Jul 9, 2015 at 12:06 PM, Rick Byers wrote:
> > On Thu, Jul 9, 2015 at 2:57 PM, Rick Byers wrote:
> >>
> >>
> >> On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking wrote:
> >>>
> >>> On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky
> wrot
On Thu, Jul 9, 2015 at 12:06 PM, Rick Byers wrote:
> On Thu, Jul 9, 2015 at 2:57 PM, Rick Byers wrote:
>>
>>
>> On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking wrote:
>>>
>>> On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky wrote:
>>> > On 7/9/15 1:32 PM, Rick Byers wrote:
>>> >>
>>> >> Done. How
On Thu, Jul 9, 2015 at 2:59 PM, Elliott Sprehn wrote:
>
> On Thu, Jul 9, 2015 at 11:52 AM, Rick Byers wrote:
>
>> On Thu, Jul 9, 2015 at 2:21 PM, Jonas Sicking wrote:
>>
>> ...
>>
>> I agree 100% with this principle. Changed mayCancel to default to false:
>>
>> https://github.com/RByers/EventL
On Thu, Jul 9, 2015 at 2:57 PM, Rick Byers wrote:
>
> On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking wrote:
>
>> On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky wrote:
>> > On 7/9/15 1:32 PM, Rick Byers wrote:
>> >>
>> >> Done. How does example 2 look now?
>> >>
>> >>
>> http://rbyers.github.io/
On Thu, Jul 9, 2015 at 11:52 AM, Rick Byers wrote:
> On Thu, Jul 9, 2015 at 2:21 PM, Jonas Sicking wrote:
>
> ...
>
> I agree 100% with this principle. Changed mayCancel to default to false:
>
> https://github.com/RByers/EventListenerOptions/commit/b6ca043c9f13cea773a9338d580a0ebc24ea8140
> .
>
On Thu, Jul 9, 2015 at 2:24 PM, Jonas Sicking wrote:
> On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky 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#example_2
> >
> >
On Thu, Jul 9, 2015 at 2:21 PM, Jonas Sicking 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
> > https://github.com/RByers/Event
On Thu, Jul 9, 2015 at 11:05 AM, Boris Zbarsky 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#example_2
>
> Looks like it would work. Also looks kind of ugly because of the
> obje
>> 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
> https://github.com/RByers/EventListenerOptions/issues/17
I definitely think that if we're going t
On 7/9/15 1:32 PM, Rick Byers wrote:
Done. How does example 2 look now?
http://rbyers.github.io/EventListenerOptions/EventListenerOptions.html#example_2
Looks like it would work. Also looks kind of ugly because of the
object-truthiness bit, but I'm not sure there's any way to avoid that
whi
On Thu, Jul 9, 2015 at 12:47 PM, Rick Byers wrote:
> On Thu, Jul 9, 2015 at 12:40 PM, Boris Zbarsky 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 add
From: whatwg [mailto:whatwg-boun...@lists.whatwg.org] On Behalf Of Rick Byers
> That seems like a nice incremental compromise. Using a new name for
> addEventListener will help address some of the feature detection /
> compatiblity concerns too. Filed
> https://github.com/RByers/EventListener
On Thu, Jul 9, 2015 at 12:40 PM, Boris Zbarsky 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 prop
On Thu, Jul 9, 2015 at 6:40 PM, Boris Zbarsky 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
> proper
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 properties you care about detecting. If those getters get invoked,
the bro
On Thu, Jul 9, 2015 at 11:40 AM, Philip Jägenstedt
wrote:
> On Thu, Jul 9, 2015 at 5:30 PM, Rick Byers wrote:
> > On Thu, Jul 9, 2015 at 11:22 AM, Anne van Kesteren
> wrote:
> >>
> >> On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers wrote:
> >> > I think there's a big opportunity to substantially im
On Thu, Jul 9, 2015 at 5:30 PM, Rick Byers wrote:
> On Thu, Jul 9, 2015 at 11:22 AM, Anne van Kesteren wrote:
>>
>> On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers wrote:
>> > I think there's a big opportunity to substantially improve scroll
>> > performance on the web in the relatively short term by
On Thu, Jul 9, 2015 at 11:22 AM, Anne van Kesteren wrote:
> On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers wrote:
> > I think there's a big opportunity to substantially improve scroll
> > performance on the web in the relatively short term by doing something
> > incremental. I.e. I'm pretty sure I
On Mon, Jul 6, 2015 at 2:47 AM, Mike West wrote:
> I've dropped the opener/openee-disowning behavior from my proposal,
> and renamed the sandboxing keyword to `allow-popups-to-escape-sandbox` in
>
> https://wiki.whatwg.org/index.php?title=Iframe_sandbox_improvments&diff=9958&oldid=9955
It appe
On 07/09/2015 06:22 PM, Anne van Kesteren wrote:
On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers wrote:
I think there's a big opportunity to substantially improve scroll
performance on the web in the relatively short term by doing something
incremental. I.e. I'm pretty sure I can get major scroll-b
On Thu, Jul 9, 2015 at 5:15 PM, Rick Byers wrote:
> I think there's a big opportunity to substantially improve scroll
> performance on the web in the relatively short term by doing something
> incremental. I.e. I'm pretty sure I can get major scroll-blocking libraries
> like Google Analytics to o
On Thu, Jul 9, 2015 at 11:05 AM, Anne van Kesteren wrote:
> On Thu, Jul 9, 2015 at 3:58 PM, Rick Byers 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/annevk/5238964
>
> Maybe the ti
On Thu, Jul 9, 2015 at 3:58 PM, Rick Byers 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/annevk/5238964
Maybe the time has come...
(I agree with Philip that if we add this it would need to b
On Thu, Jul 9, 2015 at 9:49 AM, Philip Jägenstedt wrote:
> On Thu, Jul 9, 2015 at 3:44 PM, Rick Byers wrote:
> > On Thu, Jul 9, 2015 at 9:39 AM, Rick Byers wrote:
> >>
> >>
> >> On Thu, Jul 9, 2015 at 9:05 AM, James Ross <
> w3c-20040...@james-ross.co.uk>
> >> wrote:
> >>>
> >>> > Date: Thu, 9
On Thu, Jul 9, 2015 at 3:44 PM, Rick Byers wrote:
> On Thu, Jul 9, 2015 at 9:39 AM, Rick Byers wrote:
>>
>>
>> On Thu, Jul 9, 2015 at 9:05 AM, James Ross
>> wrote:
>>>
>>> > Date: Thu, 9 Jul 2015 14:42:07 +0200
>>> > From: phil...@opera.com
>>> >
>>> > I think this looks like a very promising ap
On Thu, Jul 9, 2015 at 9:39 AM, Rick Byers wrote:
>
> On Thu, Jul 9, 2015 at 9:05 AM, James Ross
> 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 fo
On Thu, Jul 9, 2015 at 9:05 AM, James Ross
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
> > argument? It seems like
> 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
> argument? It seems like a problem that addEventListener(type,
> callback, { mayCancel
On Wed, Jul 8, 2015 at 9: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, with
> scroll-blocking DOM events (wheel and touchstart
29 matches
Mail list logo
