- From: Chris Harrelson <notifications@github.com>
- Date: Thu, 10 Jul 2025 15:40:46 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 10 July 2025 22:40:50 UTC
chrishtr left a comment (w3c/uievents#398) > I would expect Firefox's behavior. I _could_ get behind the behavior of scaling by the "layer"s transform. But scaling by all ancestor layers doesn't quite make sense to me? The coordinates get kinda meaningless in that case / you need to un-scale them to do the right thing... I don't really care either way, and am not sure it matters much to developers. I changed the behavior of layerX and layerY a few years ago and there were no bugs reported, so I don't know how much developers use these fields; if not much, then the important thing is interop. In which case, is it feasible to just match Chromium/WebKit? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/398#issuecomment-3059364270 You are receiving this because you are subscribed to this thread. Message ID: <w3c/uievents/issues/398/3059364270@github.com>
Received on Thursday, 10 July 2025 22:40:50 UTC