(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #19) > But it means that we also don't need bug 2041034, right? That's right. (Bug 2041034 was spun out from this bug for the purpose of land one of the patches in the original series, possibly behind a pref.) > A change like that most likely would require spec work on our side as well. At the time of filing, I was thinking we could make this implementation change without any spec changes. I think we still potentially could if we needed to, but now that it's looking like we won't need this for Interop 2026, I think it will make more sense to start with a spec discussion and maybe give users of the WebDriver scroll action API the option to pan-gesture vs. mouse-wheel behaviour.
Bug 2015367 Comment 20 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Henrik Skupin [:whimboo][⌚️UTC+2] from comment #19) > But it means that we also don't need bug 2041034, right? That's right. (Bug 2041034 was spun out from this bug for the purpose of land one of the patches in the original series, possibly behind a pref.) > A change like that most likely would require spec work on our side as well. At the time of filing, I was thinking we could make this implementation change without any spec changes. I think we still potentially could if we needed to, but now that it's looking like we won't need this for Interop 2026, I think it will make more sense to start with a spec discussion and maybe give users of the WebDriver scroll action API the option to choose between pan-gesture vs. mouse-wheel behaviour.