Open Bug 1534199 Opened 7 years ago Updated 6 months ago

Delete `MouseEvent.mozPressure` after deprecation period is over

Categories

(Core :: DOM: Events, task, P2)

task

Tracking

()

People

(Reporter: mbrodesser, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed, site-compat)

Attachments

(1 file)

Priority: -- → P2
Assignee: nobody → mbrodesser
Depends on: 1260726
Keywords: site-compat
Depends on: 1165211
No longer depends on: 1260726

According to the telemetry (using https://gist.github.com/badboy/2f254551a627ce19f877de216c435953, as described in https://bug1165211.bmoattachments.org/attachment.cgi?id=9051264) data, roughly 1.5% of opened pages still use MouseEvent.mozPressure. However, YouTube is known to be one user. The usage of it observed there won't break the page when this attribute is removed. However, I can't exclude there are usages, which break that or other sites. Given that YouTube is one the most popular websites, I guess that the main usage of the above mentioned 1.5% stems from it.

Therefore, I suggest submitting this to Nightly now, since the merge date (https://wiki.mozilla.org/Release_Management/Calendar) was yesterday. In case removing MouseEvent.mozPressure breaks a significant number of websites, we can revert this change easily, only affecting Nightly.

Type: defect → task
Assignee: mbrodesser → nobody
Severity: normal → S3

Sean, what would the threshold to finally remove this? (It came up in Bug 1871789) Document Use Counter seems to be at .5% while Page is at 3.9% but I'm not clear about the differences there....

Flags: needinfo?(sefeng)
See Also: → 1871789

I am not sure about the threshold and also not sure who's making the call.

Redirecting this to Simon :)

Flags: needinfo?(sefeng) → needinfo?(zcorpan)

We might want to do the pointer event upgrade of click event before removing this, in case anyone is doing some polyfill with this.

See Also: → 1675847

Document use counters count usage per document, and they accumulate to Page use counters which count usage per window.

I don't know if there's any threshold, but 3.9% of pages using, as the only data point, does NOT say that it's safe to remove.

I could check usage in httparchive to see how it's used. Keeping NI.

Blocks: unprefix
No longer depends on: proprietary-dom

From httparchive session: it seems one of mozPressure use is from tinymce that wants to ignore the deprecated properties to prevent deprecation warnings.

https://github.com/tinymce/tinymce/blob/4b7583d4afea3c35dd5118b675cd85590ba5814e/modules/tinymce/src/core/main/ts/events/EventUtils.ts#L61-L66

I think we should look into removing mozInputSource and the MOZ_* constants at the same time.

(In reply to Simon Pieters [:zcorpan] from comment #10)

I think we should look into removing mozInputSource and the MOZ_* constants at the same time.

I still think the blocker is bug 1675847; e.g. OpenStreetMap uses mozInputSource to polyfill the lack of PointerEvent on contextmenu event and removing them without PointerEvent upgrade may break webcompat.

(This is not about unprefix)

Blocks: proprietary-dom
No longer blocks: unprefix, 1675847
Depends on: 1675847
See Also: 1675847

This removal should probably be mentioned at https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent for completeness. (mozInputSource and other proprietary and deprecated properties are mentioned there as well.)
A reference to https://developer.mozilla.org/en-US/docs/Web/API/PointerEvent/pressure might make sense.

Sebastian

Keywords: dev-doc-needed

Clearing NI (but keeping on my todo).

Flags: needinfo?(zcorpan)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: