Page MenuHomePhabricator

Detect potential selser corruption
Closed, DuplicatePublic

Description

In T239875, unstripped dsr info from pasted content was being used during serialization but was detected since the node start was beyond the source length.

This task is to discuss if it's better to fail early when detecting the potential for corruption and explore other methods of detection.

Event Timeline

Arlolra created this task.Dec 6 2019, 9:47 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 6 2019, 9:47 PM
ssastry renamed this task from Detect potentail selser corruption to Detect potential selser corruption.Dec 6 2019, 9:47 PM

Change 554965 had a related patch set uploaded (by Arlolra; owner: Arlolra):
[mediawiki/services/parsoid@master] Account for getOrigSrc returning null

https://gerrit.wikimedia.org/r/554965

ssastry triaged this task as Medium priority.Dec 6 2019, 9:50 PM

Change 554965 merged by jenkins-bot:
[mediawiki/services/parsoid@master] Account for getOrigSrc returning null

https://gerrit.wikimedia.org/r/554965

LGoto moved this task from Needs Triage to Backlog on the Parsoid board.Feb 15 2020, 12:05 AM
LGoto lowered the priority of this task from Medium to Low.Feb 21 2020, 5:19 PM
LGoto moved this task from Backlog to Tech Debt / Big changes on the Parsoid board.