Last modified: 2013-08-13 08:21:18 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 T53976, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51976 - Impossible to edit a specific section when switching from VisualEditor to "legacy mode" (due to reference to QuickEdit gadget in vector.js?)
Impossible to edit a specific section when switching from VisualEditor to "le...
Status: RESOLVED INVALID
Product: VisualEditor
Classification: Unclassified
General (Other open bugs)
unspecified
Macintosh Mac OS X 10.8
: Unprioritized major
: ---
Assigned To: James Forrester
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-24 17:23 UTC by L736E
Modified: 2013-08-13 08:21 UTC (History)
4 users (show)

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


Attachments

Description L736E 2013-07-24 17:23:57 UTC
I'm an user on it.wiki, where VisualEditor is now enabled by default on the whole ns0.

I was trying to modify a long article, on a specific section, and needed to introduce wikicode (namely {{...}} for a paragraph replaced by an empty section).


VisualEditor forced me to switch to legacy mode, but whenever I try to edit the specific section, through the local "Edit" command at section level, the legacy editor always opens in the basic editor the whole article and not just the selected section.

This is heavily annoying when dealing with very long articles, with plenty of sections.
Comment 1 John Mark Vandenberg 2013-07-24 22:22:43 UTC
I can't reproduce this on it.wiki, using vector skin and Firefox/Linux.

Does this happen on every article for you?  Which skin are you using?
Comment 2 L736E 2013-08-09 16:29:20 UTC
I'm using vector. The issue appeared both on Safari/OS X (Mountain Lion, 10.8) and on Firefox/Windows XP Pro.


However, I was apparently able to overcome the issue. I read in the FAQ that it's recommended to disable the QuickEdit extension to avoid undesired effects with VE, so I checked in my preference pane that this extension was actually disabled (and it was).


However, in my vector.js fiel, inside the "toLoad" variable, there was a reference to QuickEdit gadget (qed). Looks like the presence of that string inside vector.js actually caused the extension to be loaded anyway. Removing that string from the vector.js and refreshing the browser's cache overcame the issue. Now I'm able to open VE directly over single individual sections.

So the results are:
* it's not enough to verify in the preference pane that the QuickEdit extension is disabled
* any reference to QuickEdit shall be removed also from the local vector.js (or monobook.js, I assume then)

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


Navigation
Links