Touchscreen Hover Button for Web Interaction Ambiguity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Touchscreen devices lack equivalent functionality for hover events, leading to ambiguity in user interactions, as pressing on the screen can be misinterpreted as either tapping or hovering, which is problematic for web browsers relying on mouseover and mouseout events.
Innovation Solution
A method for processing hover events on touchscreen devices involves obtaining web or application data, determining if it includes elements associated with hover events, and displaying a hover button if applicable, allowing users to trigger hover events through distinct touch inputs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If touchscreen devices rely solely on touch input, then the device maintains simplicity in input mechanism, but hover events cannot be distinguished from tap actions
Solution Approach 1:
The touch input mechanism is segmented into two distinct operations: a first touch input for hover selection and a second touch input for confirmation/action. This segmentation allows the system to distinguish between hovering (informational) and tapping (actional) events, resolving the ambiguity while maintaining touchscreen simplicity.
Solution Approach 2:
The first touch input serves as a preliminary action that selects or hovers over a target without executing the final action. The system registers this preliminary hover state and waits for a second confirmation touch input before executing the actual operation, enabling hover functionality without adding complex hardware.
2Device complexity
If touchscreen devices treat all presses as tap actions, then the system maintains consistent input handling, but web browser hover functionality (mouseover/mouseout events) becomes unavailable
Solution Approach 1:
The input handling system becomes dynamic by adapting its interpretation of touch inputs based on context. The same touchscreen can handle both simple tap operations and complex hover sequences, with the system determining the appropriate interpretation based on whether hover functionality is enabled and the specific interaction pattern detected.
Solution Approach 2:
The touchscreen input mechanism is designed to serve multiple functions: it can handle simple tap operations for basic interactions and complex hover sequences for browser functionality. This multi-functionality allows the same hardware to support both simplified input handling and comprehensive web browser hover support.
3Reliability
If a hover button is displayed for each element, then hover functionality is provided, but the interface complexity increases
Solution Approach 1:
The hover button serves as an intermediary element that mediates between the user's intent to hover and the system's response. Rather than requiring direct manipulation of every element, the hover button provides a centralized control point that triggers hover events for selected elements, reducing interface complexity while maintaining hover functionality.
Data Source
AI summary
A system and method for processing a hover event on a touchscreen device includes obtaining web page data on the touchscreen device. Content corresponding to the web page data is displayed on a touchscreen of the touchscreen device. A determination is made if the web page data includes a web page element associated with a hover event. If the web page data includes the web page element associated with the hover event, a hover button is displayed on the touchscreen in association with the displayed content corresponding to the web page data.