chrome, doesn't accept preventDefault and still cancelable is true

[Nadya678]

Chrome cannot preventDefault on the #document, <body/> and <html/> objects. The cancelable is still true. The warnings and access violation should be reported IMO if cancelable is false.

TouchEvent 
{
altKey:false
bubbles:true
cancelBubble:false
cancelable:true
changedTouches:TouchList {0: Touch, length: 1}
composed:true
ctrlKey:false
(...)
}

[Intervention] Unable to preventDefault inside passive event listener due to target being treated as passive. See https://www.chromestatus.com/features/5093566007214080

IMO if any browser "improve scrolling" and other make extensions, the event should have set cancelable to false due to specification.

After setting touch-action:none the warning is not emitted but still the event is not cancelled by use od preventDefault and stopPropagation.

[annevk]

I recommend filing a bug against Chrome or maybe https://github.com/WICG/interventions/. This isn't really defined behavior.

[Nadya678]

@annevk This is not true.

cancelable of type boolean, readonly Used to indicate whether or not an event can have its default action prevented. If the default action can be prevented the value is true, else the value is false.

https://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-Event-canCancel

[annevk]

That definition is no longer entirely accurate, but it doesn't matter, since you're complaining about behavior specific to Chrome, not something that's in the DOM Standard: https://dom.spec.whatwg.org/.