Last modified: 2014-05-22 00:53:19 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 T64229, 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 62229 - VisualEditor: Link inspector dirties links, causes dirty diffs for links with underscores
VisualEditor: Link inspector dirties links, causes dirty diffs for links with...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
Data Model (Other open bugs)
unspecified
All All
: High normal
: VE-deploy-2014-05-22
Assigned To: Ed Sanders
https://www.mediawiki.org/wiki/User:C...
:
Depends on: 64750
Blocks: ve-linkediting
  Show dependency tree / graph
 
Reported: 2014-03-04 20:52 UTC by Roan Kattouw
Modified: 2014-05-22 00:53 UTC (History)
5 users (show)

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

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

Description Roan Kattouw 2014-03-04 20:52:41 UTC 
Edit a page with wikitext [[User:Trevor_Parscal|Trevor Parscal]] ([[User talk:Trevor_Parscal|talk]]). Inspect the second link ("talk"), wait for the suggestions to load, then click out of the inspector. The save button activates. Click the save button and review the diff, and you'll see that the underscore in the link target went away.

Looking at the DM transaction history, the link was replaced with a newly generated annotation that doesn't have htmlAttributes and doesn't have origTitle or any of the orig* attributes.

For whatever reason, this bug doesn't happen for the first link. Maybe it's because only the second link has a namespace prefix that contains a space?
Comment 1 James Forrester 2014-05-19 23:14:19 UTC 
Is there anything for VE to do here or will it Just Work™ once Parsoid updates the production service?
Comment 2 James Forrester 2014-05-22 00:53:19 UTC 
AFAICT this is now fixed, thanks be to Parsoid.
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