Unfortunately implementing this was complicated enough that no browsers implemented it correctly. The usemap attribute was formerly defined as caseless.
Intent to Remove | Chromestatus Tracker | Chromium Bug # Remove case-insensitive matching for usemap attribute Fire a consistent sequence of MouseEvents with appropriate buttons and other properties.Starting with Chrome 58, a mouse on Android M or later will: The design had many side-effects including mouse interactions firing TouchEvents, all mouse buttons appearing as left mouse buttons, and MouseEvents being suppressed by TouchEvents. For example, a mouse drag motion occurring while a mouse button is pressed generates MotionEvents, delivered through View.onTouchEvent.īut since touch events cannot support hover, hovering mousemoves followed a separate path. Until Chrome 57, Android low-level mouse events in Chrome primarily followed an event path designed for touch interactions. # Mouse on Android stops firing TouchEvents
This list is subject to change at any time. This article describes the deprecations and removals in Chrome 58, which is in beta as of March 16. In nearly every version of Chrome, we see a significant number of updates and improvements to the product, its performance, and also capabilities of the Web Platform.