On Fri, Jul 10, 2015 at 10:54 PM, Majid Valipour maji...@chromium.org wrote:
Minor bikeshed:
I have put scrollRestoration on history.options instead of directly history
itself in order to use history.options as an interface to contain any other
restoration related attributes which have similar
On Sat, Jul 11, 2015 at 8:19 PM, Domenic Denicola d...@domenic.me wrote:
I'm not sure that actually matters though, since canceling inside
setTimeout(,0) shouldn't have much affect besides changing
`e.defaultPrevented`. So maybe it's OK.
It's fine. The code that dispatches an event and then
On Fri, Jul 10, 2015 at 9:12 PM, Rick Byers rby...@chromium.org wrote:
1) Should we extend the existing addEventListener API or change the API
names (and perhaps other things) completely.
https://github.com/RByers/EventListenerOptions/issues/18
It seems most other DOM peers are okay with
From: Anne van Kesteren [mailto:ann...@annevk.nl]
2) Should mayCancel=false listeners always get an Event with
cancelable=false, or is this just a hint such that all listeners
still get the same event with the same properties.
https://github.com/RByers/EventListenerOptions/issues/2
I was
[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