Last modified: 2013-10-07 20:33:41 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 T57410, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55410 - Misnested annotations do not round-trip correctly - autoInsertedEnd used despite editMode?
Misnested annotations do not round-trip correctly - autoInsertedEnd used desp...
Status: NEW
Product: Parsoid
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Gabriel Wicke
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-07 14:34 UTC by Roan Kattouw
Modified: 2013-10-07 20:33 UTC (History)
3 users (show)

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


Attachments

Description Roan Kattouw 2013-10-07 14:34:55 UTC
$ echo "'''<sub>Foo'''Bar</sub>" | node parse.js | node parse.js --html2wt
'''<sub>Foo'''Bar

$ echo "'''[[DTW|D'''etroit]]" | node parse.js | node parse.js --html2wt
WARNING: DSR inconsistency: cs/s mismatch for node: A s: 9; cs: 20
'''[[DTW|D]]'''[[DTW|etroit]]
Comment 1 ssastry 2013-10-07 14:37:25 UTC
https://gerrit.wikimedia.org/r/#/c/83216/ will fix the second example:

[subbu@earth lib] echo "'''[[DTW|D'''etroit]]" | node parse.js | node parse.js --html2wt
'''[[DTW|D'''etroit''']]'''
Comment 2 Gabriel Wicke 2013-10-07 20:17:09 UTC
Verified that the second case is fixed now that 83216 is merged. 

In the first case I'd expect the output to be "'''<sub>Foo</sub>'''Bar". For some reason the autoInsertedEnd marker seems to be used here despite editMode being true, which looks like a bug.
Comment 3 Gabriel Wicke 2013-10-07 20:28:44 UTC
Tidy seems to handle sub mis-nestings different from the HTML spec:
https://www.mediawiki.org/wiki/User:GWicke/Test/Sub

I'm inclined to follow the HTML5 spec in this case.

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


Navigation
Links