Last modified: 2013-04-19 18:36:09 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 T46702, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44702 - VisualEditor: Parsoid selective serialisation failure when deleting an LI (artefact of old version of Parsoid?)
VisualEditor: Parsoid selective serialisation failure when deleting an LI (ar...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: High normal
: VE-deploy-2013-04-29
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-06 04:20 UTC by Phil Kirkham
Modified: 2013-04-19 18:36 UTC (History)
2 users (show)

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


Attachments
shows the result after a save with 'friend' being duplicated (14.10 KB, image/png)
2013-02-06 04:20 UTC, Phil Kirkham
Details

Description Phil Kirkham 2013-02-06 04:20:10 UTC
Created attachment 11736 [details]
shows the result after a save with 'friend' being duplicated

Text was several lines long
Placed cursor at start of last line
Pressed delete to move the line up to the same line as the second to last
Saved
The last line has not been deleted and it also present on the second to last

Screenshot attached
This
is
the
end
my
friend

- put cursor at start of friend and pressed delete and then added a space

Screenshot shows the result, 'friend' is now in twice
Comment 1 James Forrester 2013-02-07 04:16:02 UTC
Thanks for this, report Phil; I can confirm the issue.

It is probably due to us running quite an old version of Parsoid on the live service; we need to update it to a newer version (which has been delayed for other before I can determine if we still have action to take here).
Comment 2 James Forrester 2013-04-19 18:36:09 UTC
This is now fixed given the Parsoid update. Sorry for the delay.

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


Navigation
Links