Remove never-supported nodeFromPoint

[saschanaz]

A checklist to help your pull request get merged faster:

• Summarize your changes
• Data: link to resources that verify support information (such as browser's docs, changelogs, source control, bug trackers, and tests)
• Data: if you tested something, describe how you tested with details like browser and version
• Review the results of the linter and fix problems reported (If you need help, please ask in a comment!)
• Link to related issues or pull requests, if any: Remove items that has never been supported #6854, Remove totally unimplemented things #6768

[foolip]

https://github.com/mozilla/gecko-dev/blob/f98dad153b59a985efd4505912588d4651033395/dom/webidl/DocumentOrShadowRoot.webidl#L18-L23 confirms this. There's a reference to w3c/csswg-drafts#556 which is still open, there isn't anything to implement yet.

[foolip]

https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/nodeFromPoint and https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/nodesFromPoint would have to be archived. @sideshowbarker do you have the power to do this? (Not merging this yet.)

[sideshowbarker]

https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/nodeFromPoint and https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/nodesFromPoint would have to be archived. @sideshowbarker do you have the power to do this?

No, I don’t — and not sure who else among BCD contributors might, except for @chrisdavidmills

[chrisdavidmills]

Yup, I can do this. Do you think archiving is the best idea? I could just delete them, or perhaps redirect them to the main interface page, to avoid the chance of broken links.

[foolip]

I don't know what's usually done with these pages, but I think @Elchi3 or @ddbeck helped me archive one in a previous instance.

We will need to archive or remove a lot of pages to land the many PRs @saschanaz has sent so it'd be great to pick an approach and coordinate a bit. Maybe like this:

• Someone reviews to confirm historical non-implementation of the removed entries
• That someone approves and ping a second reviewer who can archive/delete MDN pages
• That second reviewer does the MDN thing and then merges the PR

[ddbeck]

it'd be great to pick an approach and coordinate a bit. Maybe like this:

• Someone reviews to confirm historical non-implementation of the removed entries
• That someone approves and ping a second reviewer who can archive/delete MDN pages
• That second reviewer does the MDN thing and then merges the PR

I agree with this and I like this as proposed. To fill in one detail: I like the idea of redirecting to the parent interface (if it exists). If there's no parent, then we'll need to take it on a case-by-case basis, perhaps with a bias toward deletion unless someone can come up with an affirmative case for preserving the page.

For pages that need redirects, I'm happy to be the default second reviewer for the MDN redirect + merge. For deletes/archives, I think that needs extra permissions. I guess we pull in @chrisdavidmills for those?

Any suggestions or objections before we just go for it?

[foolip]

Sounds great to me, if @chrisdavidmills is up for some page deletion duty :)

[chrisdavidmills]

Sounds great to me, if @chrisdavidmills is up for some page deletion duty :)

Yup, definitely!

I'd like to go with @ddbeck 's suggestion of redirecting to parent page if there is a sensible parent to redirect to, or deleting if not.

Aside from that, send me the list of pages and I can get to work.

[foolip]

I've summarized our process in #6854 (comment) and will start with this very PR.

[foolip]

These are Gecko APIs never exposed to web content. These pages need redirecting to the parent page:
https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/nodeFromPoint
https://developer.mozilla.org/en-US/docs/Web/API/DocumentOrShadowRoot/nodesFromPoint

Over to @ddbeck

[ddbeck]

Redirects done and merging. Thanks everyone for coming together for a good way to handle these. 👍