Last modified: 2014-06-20 22:04:05 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 T68693, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66693 - VisualEditor: Typing diacritics results in stray accent marks at the top of the page in Chrome
VisualEditor: Typing diacritics results in stray accent marks at the top of ...
Status: RESOLVED WORKSFORME
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-16 22:37 UTC by WhatamIdoing
Modified: 2014-06-20 22:04 UTC (History)
2 users (show)

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


Attachments

Description WhatamIdoing 2014-06-16 22:37:25 UTC
María typed her name in VisualEditor on a Mac:  [SHIFT] m + a + r + [OPTION] e + i + a. 

She runs Chrome on a MacBook Pro with a U.S. keyboard.  The result was this:


[top of page]
´

Lots of text here

María

The rest of the page

[end of page]


Using a normal keyboard shortcut to add accents to characters should not result in  stray "´" characters at the top of the page.

See https://office.wikimedia.org/w/index.php?diff=113478&oldid=113425 for an example.
Comment 1 WhatamIdoing 2014-06-16 22:38:01 UTC
I can't reproduce this in Safari 6.1.4 on my Mac and haven't tried to reproduce it in Chrome.
Comment 2 James Forrester 2014-06-18 21:41:38 UTC
I can't reproduce in Chrome or Safari either, in master, testing or production – possibly something odd with a system IME or similar? Provisionally marking as WORKSFORME – can María test again and confirm?
Comment 3 WhatamIdoing 2014-06-20 22:04:05 UTC
Testing after the latest update was unable to reproduce the problem.

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


Navigation
Links