- From: Masayuki Nakano <notifications@github.com>
- Date: Wed, 02 Oct 2019 23:46:09 -0700
- To: w3c/uievents <uievents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 3 October 2019 06:46:31 UTC
(Sorry, I didn't realize the mention here.) Yes, sounds like that's great idea. I agree with it. However, I have a concern about implementing it. For making it, each implementation should have computed value of `lineDeltaX/Y` and `pageDeltaX/Y` or line height or page height/width for computing them later since events may be stored with variables and may be referred later (i.e., after ending the propagation). I don't mind the cost as a developer of Mozilla DOM Events, but I'm not sure how other browser developers. And in my understanding, the line height, page width and page height values are used the value **at** dispatching `wheel` event rather than the attributes are accessed. So, I hope that UI Events should define: 1. **When** these reference values are fixed. 2. **Which** element's size should be referred (Event.target? Nearest ancestor scrollable Element? Root element?). -- 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/181#issuecomment-537811017
Received on Thursday, 3 October 2019 06:46:31 UTC