Touch Event Queuing for Partial Page Interaction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users experience significant delays when requesting web pages due to factors like connection speed, server load, page size, embedded objects, and processing power, making browsing frustrating with extended DOM interactive times.
Innovation Solution
Implementing a touch event queuing system on user devices that stores and visually indicates touch events before a web page is fully interactive, allowing these events to be applied once the page is partially interactive, thereby improving user interaction without waiting for complete rendering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the browser waits for the page to be fully interactive before processing user touch events, then the page can respond correctly to user actions, but the user experiences significant delay and frustration
Solution Approach 1:
The patent implements a touch event queue that captures and stores user touch events before the page is fully interactive. Instead of discarding or delaying these events, the system preliminarily records them in a data structure (queue) with their original coordinates, allowing them to be processed once the page becomes interactive without losing the user's intended actions
Solution Approach 2:
The patent introduces a touch event queue as an intermediary mechanism between the user's touch input and the page's interactive elements. This queue acts as a buffer that temporarily holds touch events, allowing the system to decouple the timing of user input from page readiness, thereby resolving the contradiction between immediate response and correct processing
2Speed
If the browser processes touch events immediately upon receipt, then user interaction feels responsive, but the page may not be ready to handle these events correctly
Solution Approach 1:
The system performs preliminary capture and storage of touch events in a queue immediately when received, preserving the timing and intent of user actions. The events are stored with their original coordinates and queued for later processing when the page is ready, thus maintaining both speed of capture and accuracy of execution
Solution Approach 2:
The patent implements a dynamic system that adapts its behavior based on page readiness state. The touch event queue dynamically adjusts when events are processed - holding them when the page is not ready and releasing them when interactive elements are available, thereby balancing immediate response with correct processing
3Reliability
If the browser waits for complete page rendering before allowing user interaction, then all page elements are properly loaded and interactive, but the user experiences extended waiting time
Solution Approach 1:
The patent applies partial action by processing touch events against the portion of the page that is currently interactive rather than waiting for the entire page to load. The touch event queue allows users to interact with available elements immediately, while events targeting elements that are still loading are captured and processed later when those elements become available
Solution Approach 2:
The system preliminarily captures touch events and their coordinates before the page is fully rendered. These events are stored in the queue and automatically applied when the corresponding page elements become interactive, allowing users to perceive immediate responsiveness while ensuring all page elements are properly loaded before interaction
Data Source
AI summary
A browser or browser component queues touch events on a user device while an associated network page is being rendered. The browser may store a detected touch event, a location of the touch event, and/or a vector associated with the touch event in a touch events queue implemented by a data repository. The browser may also visually indicate that the touch event has been registered. Once the network page is at least partially interactive, the browser may retrieve the touch event information from the touch events queue and apply the touch event. Prior to or after applying the touch event, the visual indicator that alerts the user that the touch event was registered may be removed. The browser may then re-render and display the network page after the touch event has been applied.