Paging HTML Tag for Intuitive Browser Navigation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web browsers lack native support for intuitive pagination navigation, relying on non-intuitive navigation controls that can be cumbersome, especially on devices with smaller form factors like mobile phones.
Innovation Solution
The introduction of a "PAGING" HTML element that allows browsers to provide unified, user-friendly navigation through gestures like swiping or keyboard arrows, independent of the web application's interface, and includes attributes for next and previous page addresses, page number, total pages, and items per page.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If web pages use traditional navigation controls provided by the web application, then paging functionality is achieved, but navigation becomes non-intuitive and cumbersome
Solution Approach 1:
The patent introduces a universal paging navigation system that works across all web applications through a standardized HTML tag. The browser's rendering engine detects this tag and automatically provides unified navigation controls (swipe gestures, keyboard arrows, buttons) that function consistently across different web applications, eliminating the need for each application to implement its own custom navigation controls.
Solution Approach 2:
The patent introduces an intermediary component - the standardized HTML paging tag with attributes (current_page, total_pages, items_per_page, next_page, previous_page) that acts as a mediator between the web application content and the browser's navigation system. This intermediary enables the browser to automatically generate intuitive navigation controls without requiring changes to the underlying web application logic.
2Adaptability or versatility
If custom pagination controls are implemented for each web application, then specific navigation functionality is achieved, but developer effort and implementation complexity increase
Solution Approach 1:
The standardized HTML paging tag provides a universal solution that works across all web applications. Developers simply need to include the tag with appropriate attributes in their HTML, and the browser automatically handles navigation control generation. This eliminates the need for developers to implement custom pagination logic for each application while still providing adaptability through the tag's attributes.
Solution Approach 2:
The browser's rendering engine automatically detects the paging tag and generates appropriate navigation controls based on the tag's attributes. This self-service mechanism eliminates the need for developers to manually create navigation controls or write additional JavaScript code for pagination, as the system automatically configures and manages the navigation interface.
3Ease of operation
If traditional mouse-click navigation is used, then page navigation is achieved, but usability on smaller devices like mobile phones deteriorates
Solution Approach 1:
The patent introduces dynamic navigation methods that adapt to different device types and input capabilities. The system supports multiple navigation modes including swipe gestures for touch screens, keyboard arrow keys for desktops, and mouse clicks as a fallback. The browser automatically selects the most appropriate navigation method based on the device's capabilities, making navigation equally usable across devices of different sizes and input methods.
Solution Approach 2:
The system changes the interaction parameters based on device type - using gesture-based swiping for mobile devices with touch screens, keyboard arrow key detection for desktop devices, and traditional mouse clicks as a universal fallback. These parameter changes enable intuitive navigation on small mobile devices where precise mouse control is difficult, while maintaining compatibility with traditional desktop interaction patterns.
Data Source
AI summary
Various systems and methods for navigating paginated items results are described herein. A web browser receives, from a server, a markup language document including a subset of a plurality of item listings. The web browser detects a paging tag in the markup language document tags that identifies attributes identifying a current page number of the plurality of item listings, a total page count of the plurality of item listings, and a number of item listings on the current page. Pagination navigation information is updated in accordance with the attributes in the paging tag. The page markup language document with the subset of the plurality of item listings may be displayed.