Background

We'd like to disable mobile transformations on pages which have unbalanced HTML as it can result in broken experience for readers. This is preferable as it gives editors clear feedback that something is broken (for example in the example of T416431: Section wrapping not working on page on pages with unbalanced templates it is unclear the page is broken unless you are on mobile and scroll down to the references section. In future it may also make sense to add a warning message at the top of the page.

User story

As an editor I want to know when I've introduced a template error that breaks a page on mobile.

Requirements

• Given an OutputPage and Title object it should be possible to determine if the page has unbalanced HTML to support MobileFrontend disabling behaviours based on the outcome.

$oracle = MediaWikiServices::getInstance()->getService( 'ParserMigration.Oracle' );
$parsoidPageUnbalanced = $oracle->parsoidPageUnbalanced( $ title );

BDD

• For QA engineer to fill out

Test Steps

• For QA engineer to fill out

Design

Potential use case:

Acceptance criteria

• Add acceptance criteria

Communication criteria - does this need an announcement or discussion?

• Add communication criteria

Rollback plan

• What is the rollback plan in production for this task if something goes wrong?

This task was created by Version 1.2.0 of the Web team task template using phabulous