Re: [WICG/webcomponents] Template/part proposals - Naming for DOM Parts API (#902)

> Of those mentioned so far, "mutation point" seems strongest to me. I'd throw _position_ out there as a candidate too, e.g. as DOMPosition. The advantage of "position" over "point" from my POV is that "point" might be too suggestive of absolute pixel coordinates as opposed to junctures in a DOM tree.

mutation position seems okay and it's probably less confusing than point, which has much greater association with graphics like a point on a line, a plane, or in a 3D space. But `Range` uses the term point to refer to its end points via compareBoundaryPoints, comparePoint, isPointInRange, etc... so there is that too.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/902#issuecomment-943071830