Last modified: 2014-10-08 21:25:37 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 T70493, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 68493 - VisualEditor: Chrome 36 and higher throws "Discontiguous selection is not supported" on opening the editor
VisualEditor: Chrome 36 and higher throws "Discontiguous selection is not sup...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
All All
: Low normal
: VE-deploy-2014-09-18
Assigned To: Ed Sanders
:
: 68771 69616 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-24 02:09 UTC by Krinkle
Modified: 2014-10-08 21:25 UTC (History)
8 users (show)

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


Attachments

Description Krinkle 2014-07-24 02:09:22 UTC
Might be related to bug 68492.

> Discontiguous selection is not supported. rangy-core-1.3.js:2842
>> (anonymous function) rangy-core-1.3.js:2842
>> (anonymous function) rangy-core-1.3.js:2852
>> (anonymous function) rangy-core-1.3.js:327
>> init rangy-core-1.3.js:249
>> loadHandler rangy-core-1.3.js:365
Comment 1 James Forrester 2014-07-28 21:50:29 UTC
*** Bug 68771 has been marked as a duplicate of this bug. ***
Comment 2 Tim Down 2014-08-01 23:08:41 UTC
It's coming from a perfectly reasonable feature test in Rangy that is upsetting non-standard behaviour in Chrome. I've reluctantly put in a hideous browser sniff to work around it in the latest Rangy release.
Comment 3 Roan Kattouw 2014-10-06 10:31:28 UTC
Fixed now because we don't use Rangy any more.
Comment 4 James Forrester 2014-10-08 21:25:37 UTC
*** Bug 69616 has been marked as a duplicate of this bug. ***

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


Navigation
Links