Conversation
| }, | ||
| "chrome_android": { | ||
| "version_added": null | ||
| "version_added": true |
There was a problem hiding this comment.
The MDN table has it listed as false for Chrome for Android, I'm not sure what mouse support is like for android browsers? Ditto for Webview Android.
There was a problem hiding this comment.
I marked it as true because I was thinking something like: "How can basic support be false when sub-feature support is true?"
Waiting on additional input for how to proceed.
| "version_added": "47" | ||
| }, | ||
| "chrome": { | ||
| "version_added": "47" |
There was a problem hiding this comment.
the MDN page says the constructor got support in Chrome in v45
There was a problem hiding this comment.
Yes, the root page indicated v45. However, the constructor page said otherwise. When in doubt, I use the later version.
| "deprecated": false | ||
| } | ||
| }, | ||
| "long_to_double": { |
There was a problem hiding this comment.
The MDN table only mentions MouseEvent.screenX, MouseEvent.screenY, MouseEvent.clientX, and MouseEvent.Y [sic] as being converted from a long to a double. Nothing about offset as far as I can tell.
| } | ||
| } | ||
| }, | ||
| "x": { |
There was a problem hiding this comment.
According to the MDN page, x and y are just aliases of clientX and clientY. Should these be merged into clientX/clientY as alternative names? I'm not sure how this should work.
There was a problem hiding this comment.
I think they should stay separate for now because x and y are still experimental and there is no way to show that fact on the alternative name of a non-experimental sub-feature, as far as I know.
api/MouseEvent.json
Outdated
| "deprecated": false | ||
| } | ||
| }, | ||
| "accel_support": { |
There was a problem hiding this comment.
Interestingly, Accel is said to have been "effectively deprecated" for the KeyboardEvent API, I wonder if the same is true of MouseEvent? And if we should handle this in some way? https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/getModifierState#Accel_virtual_modifier
There was a problem hiding this comment.
It appears that way. I found no mention of "Accel" in the newer ui events spec for neither KeyboardEvent nor MouseEvent. Good catch!
The way you've done this here is better in my opinion. I'd like to have giant texts and notes to remain in the wiki. 👍 |
MouseEvent
The tables are missing quite a bit of data so I used my best judgement to make what was available somewhat consistent.
One question: how can I add the notes from
buttonsfor Firefox? Do I add the huge paragraph in a note?