Closed Bug 1494470 Opened 7 years ago Closed 7 years ago

document.elementFromPoint got erroneously merged into DocumentOrShadowRoot.elementFromPoint

Categories

(Developer Documentation Graveyard :: API: Miscellaneous, enhancement, P1)

All
Other
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: JoeBlevins_github, Assigned: sheppy)

References

()

Details

:: Developer Documentation Request Request Type: Correction Gecko Version: unspecified Technical Contact: :: Details There's two different APIs, there's the DocumentOrShadowRoot's elementFromPoint and there's the document's elementFromPoint. You've merged the two into one article, and then slapped the word "Experimental" and "Obsolete" all over the place, which is all well and good for DocumentOrShadowRoot but has nothing to do with a feature which has existed well before that was even a draft. Your own search and external sites are still linking to the now-not-existing old article e.g.: https://caniuse.com/#feat=element-from-point (See resources MDN Web Docs - elementFromPoint) I cannot revert the edit since the old article simply doesn't exist. It has been entirely replaced by the the DocumentOrShadowRoot's version of the same.
Assignee: nobody → eshepherd
Component: API: CSSOM → API: Miscellaneous
Priority: -- → P1
The Document.elementFromPoint property has actually moved to the DocumentOrShadoRoot mixin, which defines methods and properties that are available both on Document and ShadowRoot objects. So this move is actually correct. However, the page content was definitely confusing. I've made a number of changes that I hope will help. We also recognize that this system of documenting mixins the way we do can be confusing. We are planning to make changes to clarify this, but we need to finish some other tasks first.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.