Last modified: 2013-06-21 00:26: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 T51732, the corresponding Phabricator task for complete and up-to-date bug report information.

Bug 49732 - VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B


Summary:	VisualEditor: Reference editor adds pawn on Ctrl+I, Ctrl+B

Status:	RESOLVED FIXED

Product:	VisualEditor
Classification:	Unclassified
Component:	Editing Tools (Other open bugs)
Version:	unspecified
Hardware:	All All

Importance:	High normal
Target Milestone:	VE-deploy-2013-06-20
Assigned To:	Inez Korczyński

URL:
Whiteboard:
Keywords:

Duplicates:	49877 49888 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Attachments
Screenshot (15.50 KB, image/png) 2013-06-18 05:26 UTC, Oliver Keyes	Details
Add an attachment (proposed patch, testcase, etc.)

Description Oliver Keyes 2013-06-18 05:26:33 UTC

Created attachment 12571 [details]
Screenshot

See associated character; italics in the reference editing interface causes a pawn to appear.

Comment 1 Oliver Keyes 2013-06-18 05:53:55 UTC

Also adding a pawn on bolding.

Comment 2 Roan Kattouw 2013-06-19 00:46:53 UTC

Please check your browser's JS console, there should be an error message that appears there at the same time that the pawns appear in the editor.

Comment 3 Oliver Keyes 2013-06-19 09:33:25 UTC

Actually, neither the console nor firebug show any errors.

It is an italicised or bolded pawn, however, so we can confirm that works.

Comment 4 James Forrester 2013-06-19 22:23:38 UTC

Fixed in Gerrit change #69503 which we will deploy this afternoon.

Comment 5 James Forrester 2013-06-21 00:13:10 UTC

*** Bug 49888 has been marked as a duplicate of this bug. ***

Comment 6 James Forrester 2013-06-21 00:26:09 UTC

*** Bug 49877 has been marked as a duplicate of this bug. ***