removeEventListener does not allow reusing addEventListenerOptions

[HolgerJeromin]

TypeScript Version: 2.5

Right now EventTarget.removeEventListener is defined with the precise definition from the Spec (without passive). But I and MDN would suggest to use the exact parameter you used at addEventListener.

unless you have specific reasons otherwise, it's probably wise to use the same values used for the call to addEventListener() when calling removeEventListener().

ref #14196 #18136

[mhegazy]

The spec seems to be clear that remove does not accept passive: https://dom.spec.whatwg.org/#ref-for-dom-eventtarget-removeeventlistener%E2%91%A0

I would say we should follow the spec, unless there is a strong reason why not to.

[HolgerJeromin]

The Browser does/must not use passive. Yes.
But are more rich dictionaries are/should be disallowed?

[kitsonk]

Excess properties are allowed when the object is not fresh. When it is fresh, objects are restricted. It is intentional to help identify errors. So yes, in certain situations, subtype dictionaries can be assigned to supertypes.

const options: AddEventListenerOptions = {
    passive: true
}

declare const target: EventTarget;

const listener = () => { };

target.addEventListener('click', listener, options);
target.removeEventListener('click', listener, options); // Works fine
target.removeEventListener('click', listener, {
    passive: true // object is fresh, therefore checked for excess properties
                  // Object literal may only specify known properties, and 'passive' 
                  // does not exist in type 'boolean | EventListenerOptions'.
});

[HolgerJeromin]

@kitsonk
Wow. I never recognized this difference!
This is exactly what i want! Thanks a lot.