Last modified: 2014-02-28 23:05:53 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 T53444, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 51444 - VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br/> at the start of a heading
VisualEditor: Sometimes it's somehow possible for VE/Parsoid to insert a <br/...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
All All
: Low minor
: ---
Assigned To: Editing team bugs – take if you're interested!
:
: 52021 (view as bug list)
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2013-07-16 14:57 UTC by C. Scott Ananian
Modified: 2014-02-28 23:05 UTC (History)
7 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description C. Scott Ananian 2013-07-16 14:57:13 UTC 
See:
http://en.wikipedia.org/w/index.php?title=User%3ACananian&diff=564446937&oldid=564446873

I was adding a heading (after a <!-- ... --> comment) and the diff stuck a <br/> inside the ==heading==.

I'm assigning this bug to VE for the moment, but it could be a parsoid bug.  I need to see the intermediate parsoid HTML generated for the change to tell one way or the other.
Comment 1 C. Scott Ananian 2013-07-16 15:04:38 UTC 
See also https://www.mediawiki.org/w/index.php?title=User%3AGWicke&diff=723931&oldid=655405

So the <!-- ... --> comment doesn't seem to have anything to do with it.
Comment 2 C. Scott Ananian 2013-07-16 15:17:16 UTC 
AzaToth made a screencast at http://youtu.be/G_xXETTVgO0 showing the issue.

Gwicke filed bug 50683 on the parsoid side -- we shouldn't allow newlines in a heading when we serialize to wikitext.

But there's still a VE issue -- where is the ↵ coming from (visible in AzaToth's screencast).  VE shouldn't be putting the newline inside the heading.
Comment 3 ssastry 2013-07-25 15:53:34 UTC 
*** Bug 52021 has been marked as a duplicate of this bug. ***
Comment 6 James Forrester 2013-09-25 00:33:23 UTC 
Does anyone have any steps to reproduce? I can't reproduce in Firefox or Chrome whilst playing around…
Comment 7 Elitre 2013-09-25 15:00:19 UTC 
The steps are clear in AzaToth's video, but I can't reproduce that either: have you fixed something about ↵ being displayed, this week?
Comment 8 Elitre 2013-09-25 15:08:30 UTC 
(BTW, I really couldn't play that vid on YouTube.)
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links