Re: [w3c/uievents] Standardize layerX/layerY on MouseEvent (#135)

> Rather than depending on arbitrary layerization by the browser (which is, AIUI, what's going on in Blink and WebKit), we should come up with a more reasonable / interoperable definition...
> 
> In Gecko, we use the closest abspos containing block or scrolling box (and per [webcompat/web-bugs#94500](https://github.com/webcompat/web-bugs/issues/94500) we should add outer `<svg>` as well I guess).

So two questions:

1. What's the use case? It would seem that the definition/behavior changing might actually affect how this API gets used, and how useful it actually is. No?

2. If we end up changing from something related to layerization to something related to containing blocks, should the name change? Maybe `containerX`/`containerY`?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/135#issuecomment-991139730