Closed Bug 991899 Opened 10 years ago Closed 8 years ago

Unprefix pointer lock

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla50
Tracking Status
firefox50 --- fixed

People

(Reporter: Ms2ger, Assigned: xidorn)

References

(Blocks 2 open bugs)

Details

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

Attachments

(3 files)

      No description provided.
What are the conditions for unprefixing?
Are there pending spec issues?
Are there known bugs/cross-browser inconsistencies?
[Edge] and [Chrome] support pointer lock unprefixed. The [webkit prefix] in Chrome was removed. The [spec] is at Candidate Recomendation with no issues. The [next spec step] in moving the spec forward is to develop testharness tests. 

[Edge] https://dev.windows.com/en-us/microsoft-edge/platform/status/pointerlockmouselock?filter=f3f0000bf&search=pointer%20lock
[Chrome] https://www.chromestatus.com/features/6753200417800192
[webkit prefix] https://bugs.chromium.org/p/chromium/issues/detail?id=398457
[spec] https://www.w3.org/TR/pointerlock/
[next spec step] https://lists.w3.org/Archives/Public/public-webapps/2015OctDec/0116.html
Blocks: pointer-lock
(In reply to Vincent Scheib (scheib@chromium.org) from comment #2)
> [Edge] and [Chrome] support pointer lock unprefixed. The [webkit prefix] in
> Chrome was removed. The [spec] is at Candidate Recomendation with no issues.
> The [next spec step] in moving the spec forward is to develop testharness
> tests. 

Do you meet any compatibility issue when removing the prefixed API?

If the interface of the API was never changed after browsers implemented it, I suppose everything should be fine.
Flags: needinfo?(scheib)
Chromium's unprefixing changed the API name only. There was no behavior change. The API has remained stable for several years now.
Flags: needinfo?(scheib)
Depends on: 1284785
Depends on: 1284788
Assignee: nobody → xidorn+moz
Given that Blink has removed prefixed PointerLock API for quite a while
without receiving compatibility issue, I'd suggest we try dropping the
prefixed version directly.

We will either pref the prefixed API on if we see enough compatibility
issue, or remove the whole bunch of prefixed PointerLock API after the
unprefixed API reaches release channel without issues.

Review commit: https://reviewboard.mozilla.org/r/67318/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/67318/
Blocks: 1289642
Comment on attachment 8774978 [details]
Bug 991899 part 3 - Disable prefixed PointerLock API by default.

https://reviewboard.mozilla.org/r/67318/#review64472

I guess we can try this.

::: dom/events/EventListenerManager.cpp:1166
(Diff revision 1)
> +      switch (aEventMessage) {
> +        case ePointerLockChange:
> +          return eMozPointerLockChange;
> +        case ePointerLockError:
> +          return eMozPointerLockError;
> +      }

don't you get some warning here about not handling all the cases? (missing default)
Attachment #8774978 - Flags: review?(bugs) → review+
https://reviewboard.mozilla.org/r/67318/#review64472

> don't you get some warning here about not handling all the cases? (missing default)

Yeah, you're right... Now I know why the webkit thing uses lots of if... I tend to just add a "default:" at the end rather than changing to use list of ifs.
Pushed by xquan@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/996b4f2f9963
part 1 - Add unprefixed API for PointerLock. r=smaug
https://hg.mozilla.org/integration/mozilla-inbound/rev/c03efdd8732f
part 2 - Unprefix PointerLock tests. r=smaug
https://hg.mozilla.org/integration/mozilla-inbound/rev/76ead0b044bb
part 3 - Disable prefixed PointerLock API by default. r=smaug
Pushed by xquan@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/1a7af0fca900
followup - Mark some pointerlock wpt as expected-pass on CLOSED TREE
I've updated the compat tables for this API to indicate that it's no longer prefixed from Firefox 50:
https://developer.mozilla.org/en-US/docs/Web/API/Pointer_Lock_API

Also updated Firefox 50 for developers:
https://developer.mozilla.org/en-US/Firefox/Releases/50
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: