My website makes extensive use of image-maps. The images are of pages from a medieval manuscript. The mouseOver event of the AREA tags has a tooltip attached to it, which displa
I have been doing some research on specifically when the iPad fires "mouseover" events versus "click" events. When the user taps anywhere on the page the iPad first fires a "mouseover" event as though the user had just placed a mouse cursor on that spot. It also fires a "mouseout" event on the last element that had focus. The browser then, as far as I can tell, checks whether any changes to the DOM occurred as a result of "mouseover" event callback.
If there has been a change to the DOM the browser does not fire a "click" event. If the user taps on the same element a second time the browser does fire a "click" event but does not fire another "mouseover" event.
On the other hand, if after the user taps on an element for the first time and the DOM has not changed after the "mouseover" event completes, then the browser fires a "click" event without waiting for a second tap.
I did find some information that partly explains the behavior described above:
https://developer.apple.com/library/content/technotes/tn2010/tn2262/_index.html
See section 5, especially.
It appears that the touch+hold is "selecting" the image-map area. The link above says that user-select can be disabled, but it doesn't say what happens when the touch+hold gesture is used on an element where user-select has been disabled. It would be great if it could become the counterpart to mouseOver under those circumstances.