I just checked my website on the iPad in the Apple Store. The iPad is a joy in many ways, but I want to know that Apple maps mouse events to finger touch events. Apple may have good reasons to do the same, but their choice seems counterintuitive and too complicated for me.
Specifically, the iPad Safari browser obviously responds to fingerDown and fingerTap, And in a different way. When I click on an area of the image map, the tooltip of the mouse hover event connected to the AREA tag is displayed and remains visible until I tap other places. When I place my finger on the image map When there is an area, the area changes color. Therefore, if the iPad Safari detects the mouseOver event handler, it will execute the mouseOver code on the click “click”, which obviously prevents the “click” event from propagating, so if there are some connections to Click event thing, it doesn’t work? Is it right?
But more importantly, why is there no fingerDown’s iPad-Safari rival’s mouseOver? When mapping mouseOver events, FingerDown seems more likely to be a candidate than Tap. I expect to be mapped in this way:
MouseClick: FingerTap (ie finger down and then immediately up)
MouseOver: FingerDown (finger down and stays on the spot)
If Apple has considered fingerDown as an opponent of mouseOver, you can display the tooltip on FingerDown and It is shown on fingerUp again that this will be the counterpart of mouseOut.
Maybe someone can enlighten me on Apple’s thinking process about the mapping of these specific mouse touch events?
Thank you
If the DOM changes, the browser will not trigger” Click event. If the user clicks on the same element for the second time, the browser will click the “click” event, but will not trigger another “mouse hovering” event.
On the other hand, if the user clicks When the element is clicked for the first time and the DOM does not change after the “mouse hover” event is completed, the browser triggers the “click” event without waiting for the second click.
My The website uses image maps extensively. The images are pages of medieval manuscripts. The mouseOver event of the AREA tag has an additional tooltip, which shows a modern typographic transcription of the ancient script of the line over which the mouse is hovered.
I Just checked my website on the iPad in the Apple Store. The iPad is a joy in many ways, but I want to know that Apple maps mouse events to finger touch events. Apple may have good reasons to do like they do, But their choice seems counterintuitive and too complicated for me.
Specifically, the iPad Safari browser obviously responds to fingerDown and fingerTap in a different way. When I click on one of the image maps Area, the tooltip of the mouse hover event connected to the AREA tag is displayed and remains visible until I tap somewhere else. When I place my finger on an area of the image map, the area changes color. Therefore, if iPad Safari detects the mouseOver event handler, it will execute the mouseOver code on the click “click”, which obviously prevents the “click” event from propagating, so if there is something connected to the click event, it won’t work? Is it right?
But more importantly, why is there no fingerDown’s iPad-Safari rival’s mouseOver? When mapping mouseOver events, FingerDown seems more likely to be a candidate than Tap. I expect to be mapped in this way:
MouseClick: FingerTap (ie finger down and then immediately up)
MouseOver: FingerDown (finger down and stays on the spot)
If Apple has considered fingerDown as an opponent of mouseOver, you can display the tooltip on FingerDown and It is shown on fingerUp again that this will be the counterpart of mouseOut.
Maybe someone can enlighten me on Apple’s thinking process about the mapping of these specific mouse touch events?
Thank you
When the iPad triggers the “mouse hover” event and the “click” event, I have been doing some research. When the user clicks on the page At any position, the iPad first triggers the “mouseover” event, just like the user has just placed the mouse cursor at that location. It also triggers the “mouseout” event on the last focused element. Then, as far as I know, browse The browser will check whether any changes to the DOM occurred due to the “mouseover” event callback.
If the DOM changes, the browser will not trigger the “click” event. If the user clicks the same for the second time Element, the browser will click on the “click” event, but will not trigger another “mouse hover” event.
On the other hand, if the user clicks on the element for the first time and completes the “mouse hover” event After the DOM has not changed, the browser triggers the “click” event without waiting for the second click.