Home

Touch input does not map correctly when a website expects mouse or trackpad input

%3CLINGO-SUB%20id%3D%22lingo-sub-718735%22%20slang%3D%22en-US%22%3ETouch%20input%20does%20not%20map%20correctly%20when%20a%20website%20expects%20mouse%20or%20trackpad%20input%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-718735%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20iOS%2013%2C%20Safari%20now%20shows%20the%20full%20desktop%20version%20of%20websites%20instead%20of%20the%20mobile%20version%2C%20but%20Apple%20mentions%20this%3A%20%3CEM%3E%22Safari%20automatically%20presents%20a%20website%E2%80%99s%20desktop%20version%20for%20iPad.%20%3CSTRONG%3ETouch%20input%20maps%20correctly%20when%20a%20website%20expects%20mouse%20or%20trackpad%20input%3C%2FSTRONG%3E.%22%3C%2FEM%3E%26nbsp%3B%20Doesn't%20this%20imply%20that%20Chromium%20doesn't%20correctly%20map%20touch%20inputs%20when%20a%20website%20expects%20mouse%2Ftrackpad%20input%3F%20It%20must%2C%20I%20very%20much%20doubt%20they're%20referring%20to%20Firefox%20for%20Windows%20or%20the%20previous%20EdgeHTML%20based%20Edge%2C%20they%20have%20to%20be%20referring%20to%20Chromium.%20Any%20idea%20what%20exactly%20Apple%20is%20saying%20the%20iPad%20now%20does%20correctly%20that%20Chromium%20is%20not%20doing%20correctly%20with%20touch%20input%20mapping%3F%20Maybe%20someone%20can%20ask%20someone%20on%20the%20Safari%20team%20what%20exactly%20they're%20referring%20to%20so%20this%20can%20be%20fixed%20for%20Windows%20touch%20devices%20like%20Surface%20tablets...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.apple.com%2Fipados%2Fipados-preview%2Ffeatures%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.apple.com%2Fipados%2Fipados-preview%2Ffeatures%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-719614%22%20slang%3D%22en-US%22%3ERe%3A%20Touch%20input%20does%20not%20map%20correctly%20when%20a%20website%20expects%20mouse%20or%20trackpad%20input%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-719614%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F318719%22%20target%3D%22_blank%22%3E%40Bdsrev%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%22Doesn't%20this%20imply%20that%20Chromium%20doesn't%20correctly%20map%20touch%20inputs%20when%20a%20website%20expects%20mouse%2Ftrackpad%20input%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Bdsrev
Occasional Contributor

In iOS 13, Safari now shows the full desktop version of websites instead of the mobile version, but Apple mentions this: "Safari automatically presents a website’s desktop version for iPad. Touch input maps correctly when a website expects mouse or trackpad input."  Doesn't this imply that Chromium doesn't correctly map touch inputs when a website expects mouse/trackpad input? It must, I very much doubt they're referring to Firefox for Windows or the previous EdgeHTML based Edge, they have to be referring to Chromium. Any idea what exactly Apple is saying the iPad now does correctly that Chromium is not doing correctly with touch input mapping? Maybe someone can ask someone on the Safari team what exactly they're referring to so this can be fixed for Windows touch devices like Surface tablets...

 

https://www.apple.com/ipados/ipados-preview/features/

1 Reply

@Bdsrev

 

"Doesn't this imply that Chromium doesn't correctly map touch inputs when a website expects mouse/trackpad input"

 

No.