Open Bug 1583519 Opened 5 years ago Updated 2 years ago

PointerEvents implementation has too many errors with stylus input

Categories

(Core :: DOM: Events, defect, P3)

defect

Tracking

()

UNCONFIRMED

People

(Reporter: aleksandar.xyz, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.132 Safari/537.36

Steps to reproduce:

I implemented advanced 3D viewport controls using PointerEvents API and noticed way too many bugs in Firefox when used with stylus input device.

Actual results:

Further investigation led me to bugs #1583480 and #1449660. After I implemented Firefox-specific workarounds I noticed another few issues like 'pointermove' event firing twice within the same animationFrame loop (which shouldn't happen) and few more.

Expected results:

At this point I am wondering if there is any point submitting those bugs individually considering that #1449660 hasn't been fixed in 2 years! It appears that the state of PointerEvents is beyond repair when used with stylus input device. Perhaps a fresh new implementation of PointerEvents would make more sense for Firefox?

Consider that iOS Safari and MacOS Safari finally shipped working and to-the-spec implementation of PointerEvents and it appears that Firefox is the only browser behind, at least in terms of accessibility and wide input device support.

I agree that stylus input in Firefox is very broken.

Hi, for now I will set a component for this issue, if isn't the right one please fell free to change it; maybe someone from dev's team could give us a hand.
Regards,
Liviu

Component: Untriaged → DOM: Events
Product: Firefox → Core
Priority: -- → P3
Blocks: 1631377
No longer blocks: 822898
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.