Browser Extension Tab Management Rules Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing web applications face inefficiencies in managing navigation and console tabs when accessing database systems, particularly in opening new records within the appropriate navigation tab regardless of the hyperlink source.

Innovation Solution

The implementation of a browser extension with a rules engine that manages tab management rules, allowing web resources to be opened within active navigation tabs, regardless of the source of the hyperlink, by intercepting and evaluating hyperlinks and determining if they should be rendered in the current tab or open a new tab.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If hyperlinks are opened in new navigation tabs by default, then users can access multiple web resources simultaneously, but tab management becomes complex and user interaction efficiency decreases

Engineering Contradiction:
ImproveAbility to access multiple web resourcesVSAvoidTab management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a tab management system that acts as an intermediary between hyperlinks and browser tabs. This system intercepts hyperlink clicks, evaluates them against stored tab management rules, and determines whether to open links in new tabs or reuse existing tabs. The rule set includes criteria such as URL pattern matching, tab title matching, and domain matching to intelligently decide tab creation vs. reuse, thereby reducing unnecessary tab proliferation while maintaining versatile resource access.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring tab states, user interactions, and hyperlink patterns. It evaluates each hyperlink against accumulated rules and past behavior patterns, adjusting its decision-making process based on feedback from previous tab management actions. This feedback loop enables the system to learn optimal tab management strategies and improve user interaction efficiency over time.

Inventive Principle:
Principle #23Feedback

2Quantity of substance

If multiple navigation tabs are opened for different records, then users can view multiple records simultaneously, but navigation between records becomes less efficient

Engineering Contradiction:
ImproveNumber of accessible recordsVSAvoidNavigation efficiency between records
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent merges multiple record views into a single navigation tab by detecting when a hyperlink points to a record within the same application context. Instead of opening a new tab, the system combines the new record view with the existing tab, using visual indicators to show multiple record instances within the same tab interface. This merging approach maintains access to multiple records while eliminating the need for separate tabs, thereby improving navigation efficiency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system transitions from a one-dimensional tab-based navigation model to a two-dimensional organization model. Within a single tab, records are organized in multiple dimensions such as hierarchical folders, categorized groups, or spatial arrangements. This dimensional change allows users to access multiple records simultaneously within one tab through structured organization, reducing the need for multiple tabs while maintaining comprehensive record accessibility.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Ease of operation

If the system intercepts and evaluates all hyperlinks to determine tab placement, then tab management becomes more efficient, but processing time and system complexity increase

Engineering Contradiction:
ImproveTab management efficiencyVSAvoidHyperlink evaluation processing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-evaluating and storing tab management rules before actual hyperlink interactions occur. It establishes URL patterns, domain lists, and tab matching criteria in advance, creating a ready-to-use evaluation framework. When hyperlinks are clicked, the system quickly matches them against pre-established rules rather than performing complex real-time analysis, significantly reducing processing time while maintaining efficient tab management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies partial evaluation by focusing only on the most critical hyperlink attributes rather than analyzing every aspect of each link. It uses selective matching based on predetermined criteria such as URL domain, path patterns, and keyword presence, evaluating only the necessary portions of hyperlinks to make tab placement decisions. This partial action approach reduces processing overhead while achieving sufficient tab management efficiency for most use cases.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10509843B2Systems and methods for managing tabs in web applications
Publication Date: 2019.12.17 SALESFORCE INC
  • US10509843B2 patent drawing
  • US10509843B2 patent drawing
  • US10509843B2 patent drawing

AI summary

A computer implemented method includes receiving, at the browser application, a first request for web resources based on user selection of a first hyperlink outside of the web application; determining if the first hyperlink is associated with a record accessible by the web application from the database system; determining, when the first hyperlink is associated with the record for the web application, if a web application interface for the web application is active in at least one navigation tab of the browser application; and presenting, when the first hyperlink is associated with the record for the web application and the web application interface for the web application is active in the at least one navigation tab, the record within a console tab of the web application interface in the at least one navigation tab.