Last modified: 2014-01-18 05:45:23 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 T58381, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56381 - Change DOM rendering of <nowiki /> to be <span typeof="mw:Nowiki"></span> or similar?
Change DOM rendering of <nowiki /> to be <span typeof="mw:Nowiki"></span> or ...
Status: NEW
Product: Parsoid
Classification: Unclassified
DOM (Other open bugs)
unspecified
All All
: Normal minor
: ---
Assigned To: Gabriel Wicke
https://en.wikipedia.org/w/index.php?...
:
: 59650 59829 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-30 19:31 UTC by James Forrester
Modified: 2014-01-18 05:45 UTC (History)
8 users (show)

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


Attachments

Description James Forrester 2013-10-30 19:31:14 UTC
VisualEditor deliberately drops <span typeof="mw:Nowiki"> annotations on changed content to prevent originally-necessary <nowiki> blocks interfering with editing. This means that HTML editors don't need to know or care about <nowiki>s, and they are just magically sorted out in the back-end so the resultant wikitext is the most like what a human would create.

However, <nowiki />s come out as a <meta typeof="mw:Placeholder">, which VisualEditor doesn't show to users but also won't ever remove, leading to potential issues where a no-longer-needed <nowiki /> sits in the wikitext, disruptively confusing to wikitext editors.

If Parsoid instead represented it as <span typeof="mw:Nowiki"></span> or similar, VisualEditor could do the same (well, a bit more work) and so drop it when the context has been edited, letting Parsoid re-generate it if needed.
Comment 1 Gabriel Wicke 2013-11-15 00:15:48 UTC
If we want to perform clean-up like this, then we should perhaps implement that in Parsoid rather than VE so that other users benefit from it as well.
Comment 2 James Forrester 2013-11-15 02:05:35 UTC
(In reply to comment #1)
> If we want to perform clean-up like this, then we should perhaps implement
> that in Parsoid rather than VE so that other users benefit from it as well.

Happy for it to be done in Parsoid instead, and for us to remove the dropping from VE.
Comment 3 James Forrester 2014-01-18 05:41:40 UTC
*** Bug 59829 has been marked as a duplicate of this bug. ***
Comment 4 James Forrester 2014-01-18 05:41:48 UTC
*** Bug 53659 has been marked as a duplicate of this bug. ***
Comment 5 James Forrester 2014-01-18 05:42:10 UTC
*** Bug 59650 has been marked as a duplicate of this bug. ***

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


Navigation
Links