Host Browser Rendering Incompatible Pages via Nested Instance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web applications developed for specific browser types or versions often become incompatible with newer browsers, forcing users to maintain older browser versions for compatibility, which is resource-intensive and inconvenient.

Innovation Solution

Implementing a system where a first browser determines if a page is incompatible and invokes a second browser instance within its window to render compatible pages, allowing seamless navigation between browsers without opening a new window, thus enabling the use of different browser versions within the same window.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If users maintain multiple browser versions for compatibility, then web application compatibility is improved, but device resource consumption increases

Engineering Contradiction:
Improvebrowser compatibilityVSAvoiddevice resource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent implements a nested browser architecture where a second browser instance is embedded within the first browser window. The first browser acts as a host container that can invoke and display the second browser's content within its own window frame, similar to how nested dolls contain smaller dolls within larger ones. This allows the system to access multiple browser versions without maintaining separate full browser windows for each, thereby reducing resource consumption while preserving compatibility.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Adaptability or versatility

If users open separate browser windows for different browser versions, then compatibility is improved, but user interface complexity increases

Engineering Contradiction:
Improvebrowser compatibilityVSAvoidinterface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple browser instances into a single unified window interface. Instead of requiring users to manage separate browser windows for different browser versions, the system combines them into one window where the host browser can display guest browser content within its tab structure. This consolidation simplifies the user interface while maintaining the ability to access multiple browser versions for compatibility purposes.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If users install third-party extensions to handle compatibility, then web application compatibility is improved, but system complexity increases

Engineering Contradiction:
Improveweb application compatibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal browser compatibility solution through a host browser that can invoke and run guest browser instances directly. This multi-functional architecture allows the host browser to handle both its native rendering tasks and the rendering tasks of guest browsers, eliminating the need for separate third-party extensions. The system provides a built-in mechanism for detecting compatibility issues and automatically invoking the appropriate browser version, thereby reducing system complexity while improving compatibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10733260B1Page display by hosted browser within controlling browser
Publication Date: 2020.08.04 MICROSOFT TECHNOLOGY LICENSING LLC
  • US10733260B1 patent drawing
  • US10733260B1 patent drawing
  • US10733260B1 patent drawing

AI summary

Web pages compatible with different web browsers are seamlessly rendered within the same tab of a single web browser window. A first browser is executed in a computing device, and has an open browser window. A request is received at the first browser to navigate to a first page. The first page is determined to be incompatible with the first browser and compatible with a second browser. Under control by the first browser, an instance of the second browser is invoked without a browser window opening for the instance of the second browser. An address of the first page is provided to the instance of the second browser. The instance of the second browser renders the first page within a tab in the open browser window of the first browser.