Last modified: 2014-02-28 23:41:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T51761, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 49761 - VisualEditor: Provide an easy way to sanity-check VE input / output behavior
VisualEditor: Provide an easy way to sanity-check VE input / output behavior
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: High enhancement
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-18 18:22 UTC by Gabriel Wicke
Modified: 2014-02-28 23:41 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Gabriel Wicke 2013-06-18 18:22:25 UTC
In the investigation of most round-tripping bugs we need to figure out if VE modified the DOM in unexpected ways or Parsoid had issues in handling an unmodified DOM. 

We need an easy way to display both the original HTML string retrieved by VE and a serialization of the modified HTML the VE sends out, possibly popped up in two textareas on some keybinding for easy copying.

This would at least allow basic manual debugging.

Optionally, as a time saver, it would be nice if you could also output a DOM diff that makes it easy to spot DOM differences. You could probably base this on the Parsoid DOMDiff module. This DOM diff can also be used in sanity checks to automatically detect VE round-trip issues.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links