Browser Extension Storage Using Iframes for Cross-Domain Sync

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing browser technologies face challenges in enabling cross-domain storage and event monitoring without compromising security or privacy, particularly with third-party cookies being restricted or blocked, and existing solutions like Storage Access API are intrusive and inefficient for additive software layers.

Innovation Solution

Implementing a cross-domain storage system external to the browser's client-side execution engine, using a browser extension with a communication iframe to synchronize data across domains, allowing additive software layers to operate securely and efficiently without direct user interaction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If third-party cookies are used for cross-domain storage, then data sharing across domains is enabled, but privacy security and user control are compromised

Engineering Contradiction:
Improvecross-domain data sharingVSAvoidprivacy security risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a browser extension as an intermediary component that mediates between first-party and third-party domains. The extension hosts a cross-domain storage mechanism that both domains can access through controlled interfaces, enabling data sharing without direct third-party cookie access. This intermediary architecture maintains security by keeping the storage mechanism within the browser's trusted extension environment rather than allowing external domains to directly set cookies.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If Storage Access API is used for cross-domain storage, then domain access control is improved, but user interaction requirements increase complexity

Engineering Contradiction:
Improvedomain access controlVSAvoiduser interaction complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements preliminary action by obtaining user permission once during the initial interaction with the first-party domain. The browser extension stores this permission and automatically manages cross-domain access thereafter, eliminating the need for repeated user interactions. The system proactively handles domain verification and access control in the background, reducing operational complexity for users while maintaining reliable domain control.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If external storage mechanism is implemented, then cross-domain data synchronization is enabled, but system complexity increases

Engineering Contradiction:
Improvecross-domain data synchronizationVSAvoidstorage system architecture
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal cross-domain storage mechanism hosted by the browser extension that serves multiple domains simultaneously. Rather than creating separate storage systems for each domain pair, the extension provides a single unified storage interface that any authorized domain can access. This multi-functional approach reduces overall system complexity by consolidating the storage infrastructure into one shared resource managed by the extension.

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

Data Source

PatentUS12475301B2Cross-domain storage for browsers
Publication Date: 2025.11.18 WALKME
  • US12475301B2 patent drawing
  • US12475301B2 patent drawing
  • US12475301B2 patent drawing

AI summary

A method, apparatus and product including a browser configured to render pages, wherein the browser comprises a client-side execution engine, wherein the browser is configured to execute an extension for the browser, wherein the extension is a computer program product that has a memory storage that is external to the client-side execution engine of the browser; and a set of pages that is defined over multiple domains, wherein the set of pages comprises respective instances of an additive software layer that is configured to execute a walkthrough over the multiple domains, wherein a page of the set of one or more pages comprises an instance of the respective instances and a communication element that is configured to enable the instance of the additive software layer to communicate data to and from the extension.