Last modified: 2014-04-02 22:46:25 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 T65447, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63447 - VisualEditor: ContentEditable div often takes more than 5 seconds to appear in Beta Labs
VisualEditor: ContentEditable div often takes more than 5 seconds to appear i...
Status: RESOLVED FIXED
Product: VisualEditor
Classification: Unclassified
ContentEditable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Chris McMahon
: browser-test-bug
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-02 21:35 UTC by Chris McMahon
Modified: 2014-04-02 22:46 UTC (History)
4 users (show)

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


Attachments

Description Chris McMahon 2014-04-02 21:35:57 UTC
seen on beta labs http://en.wikipedia.beta.wmflabs.org/

After clicking Edit for VisualEditor, sometimes the user waits longer than expected for the editable div to appear.  

There is a default timeout of 5 seconds in the automated browser tests, and these tests are failing more and more often because the edit surface in VE takes longer than 5 seconds to appear, for a page of reasonable size.
Comment 1 James Forrester 2014-04-02 22:39:29 UTC
Fixed in Gerrit change #123450.
Comment 2 Chris McMahon 2014-04-02 22:42:42 UTC
Well, the *tests* are fixed, but it is a bit sketchy that the editable div is taking so long to manifest.
Comment 3 James Forrester 2014-04-02 22:46:25 UTC
(In reply to Chris McMahon from comment #2)
> Well, the *tests* are fixed, but it is a bit sketchy that the editable div
> is taking so long to manifest.

Beta Labs being slow isn't really a bug so much as a statement of fact…

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


Navigation
Links