Automated Layout Error Detection for Cross-Browser UI Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cross-browser compatibility issues arise due to differences in how browsers render source code, leading to layout errors such as incorrect text display, misalignment, and inconsistent design elements, which can affect user experience and interface functionality.

Innovation Solution

A method and system for detecting layout errors by applying layout error detection rules against object model data, comparing attributes of layout elements, and generating a layout error report to identify and address inconsistencies across different browsers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual UI testing is performed across multiple browsers, then layout errors can be identified, but time consumption and testing complexity increase significantly

Engineering Contradiction:
Improvelayout error detection accuracyVSAvoidtesting time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent replaces manual mechanical testing with automated computer-based testing. The system uses automated browsers to render application states and automatically compares visual representations against expected layouts, eliminating the need for manual testing while maintaining high detection accuracy

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent creates visual copies (snapshots) of application states rendered in different browsers and compares these copies to identify layout discrepancies. This copying approach allows efficient parallel testing across multiple browsers without increasing time consumption

Inventive Principle:
Principle #26Copying

2Reliability

If comprehensive UI testing is performed to ensure cross-browser compatibility, then display consistency improves, but device complexity and testing resource requirements increase

Engineering Contradiction:
Improvecross-browser compatibilityVSAvoidtesting system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal testing framework that can test application states across multiple browsers using the same core comparison logic. The system handles different browser types (Chrome, Firefox, Safari, Edge) through a unified approach, reducing overall system complexity while improving cross-browser reliability

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

Solution Approach 2:

The patent introduces an intermediary comparison system that mediates between different browser renderings. Instead of directly comparing complex browser outputs, the system uses intermediate visual snapshots and standardized comparison algorithms to identify layout errors, simplifying the testing architecture

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If detailed layout error detection is implemented, then manufacturing precision of UI display improves, but difficulty of detecting and measuring errors increases

Engineering Contradiction:
ImproveUI display precisionVSAvoidlayout error detection difficulty
Core Design Contradiction:
Manufacturing precisionVSDifficulty of detecting and measuring

Solution Approach 1:

The patent segments the UI layout into distinct elements (headers, footers, content areas, navigation elements) and compares each segment independently. This segmentation approach enables detailed precision detection while simplifying the measurement process by breaking down complex layout comparisons into manageable individual element comparisons

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10474887B2Identifying a layout error
Publication Date: 2019.11.12 MICRO FOCUS LLC
  • US10474887B2 patent drawing
  • US10474887B2 patent drawing
  • US10474887B2 patent drawing

AI summary

First object model data from a first application state generated in a first browser mode may be collected. The first object model data may comprise a code-based representation of a first layout element and a second layout element of the first application state. According to a layout detection rule, a first attribute of the first layout element may be compared with a second attribute of the first layout element or of a second layout element. A layout error corresponding to the first layout element may be identified based on the comparison of the first attribute with the second attribute.