Last modified: 2013-05-10 02:54:28 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 T50303, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48303 - IE7/IE6 RL error on login pages for jquery.NavigationTiming
IE7/IE6 RL error on login pages for jquery.NavigationTiming
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
NavigationTiming (Other open bugs)
unspecified
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 48309
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-09 18:10 UTC by Chris McMahon
Modified: 2013-05-10 02:54 UTC (History)
4 users (show)

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


Attachments

Description Chris McMahon 2013-05-09 18:10:43 UTC
Seen at 
http://commons.wikimedia.beta.wmflabs.org/wiki/Special:UserLogin/signup  at least after navigating to Special:CreateAccount

The browser test for creating an account has a function that checks for Resource Loader errors:  https://github.com/wikimedia/qa-browsertests/blob/master/features/step_definitions/create_account_steps.rb

That function is returning an error "Error modules: jquery.NavigationTiming." for IE7 and IE6.
Comment 1 Steven Walling 2013-05-09 19:09:11 UTC
(In reply to comment #0)
> 
> That function is returning an error "Error modules: jquery.NavigationTiming."
> for IE7 and IE6.

Related to https://meta.wikimedia.org/wiki/Schema:NavigationTiming ?
Comment 2 Matthew Flaschen 2013-05-09 20:44:19 UTC
Note, GettingStarted does not control the login or signup pages themselves.  It affects Special:GettingStarted and the post-signup screen, and sometimes UI on later pages (e.g. an article it encourages you to work on).

This looks like a possible bug in NavigationTiming.
Comment 3 Matthew Flaschen 2013-05-09 22:17:55 UTC
It's running an ancient version (the first added to extensions.git) due to bug 48309.  I'll look at this again when that is resolved.
Comment 4 Andre Klapper 2013-05-10 01:40:02 UTC
(In reply to comment #3)
> due to bug 48309.  I'll look at this again when that is resolved.

==> adding dependency on bug 48309
Comment 5 Ori Livneh 2013-05-10 02:54:28 UTC
This extension was totally rewritten in March. There is no 'jquery.NavigationTiming' module, and the current JavaScript code base does not share so much as a single line with the version running on the beta cluster. The version that did have 'jquery.NavigationTiming' was broken in several ways, any one of which could have caused this. Marking as 'invalid', as this bug is epiphenomenal to bug 48309 but not a duplicate of it.

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


Navigation
Links