Closed
Bug 808404
Opened 12 years ago
Closed 12 years ago
javascript fails on specific page due to defining top level function named 'top'
Categories
(Tech Evangelism Graveyard :: English US, defect)
Tech Evangelism Graveyard
English US
Tracking
(firefox16 affected, firefox17 affected, firefox18 affected, firefox19 affected, firefox-esr10 affected)
People
(Reporter: david, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: Regressed by: Bug 765527)
Attachments
(1 file)
15.54 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121024073032 Steps to reproduce: Went to page http://www.spfldcycling.org/miles/12_08_detail.htm Actual results: Javascript does not run on the page and the red "no javascript" message remains at top. Analysis says function "setup()" is not found. The page works fine with Internet Explorer and worked fine with previous Firefox versions. I am not sure exactly which version of Firefox it started to fail. I edited the page trying different things and can't make it work and feel it is a bug introduced in one of the latest Firefox versions. Expected results: The red "no javascript" message should disappear. The horizontal and vertical labels should move with the table when scrolled. Clicking on a row should cause that row to change color.
Updated•12 years ago
|
Summary: javascript fails on page → javascript fails on specific page
I'm not sure if the bug is valid but there is a regression range. It regressed in FF17 so I guess the regression has been backported into FF16. m-c good=2012-08-25 bad=2012-08-26 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=f077de66e52d&tochange=b3cce81fef1a
Keywords: regression,
regressionwindow-wanted
Comment 2•12 years ago
|
||
Regression window(m-c) Good: http://hg.mozilla.org/mozilla-central/rev/116a2c731931 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120825182458 Bad: http://hg.mozilla.org/mozilla-central/rev/b3cce81fef1a Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120826030526 Pushlog; http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=116a2c731931&tochange=b3cce81fef1a Regression window(m-i) Good: http://hg.mozilla.org/integration/mozilla-inbound/rev/7c2aaefc3891 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120825141859 Bad: http://hg.mozilla.org/integration/mozilla-inbound/rev/573c753b7bc8 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0 ID:20120825145758 Pushlog; http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7c2aaefc3891&tochange=573c753b7bc8 Regressed by: Bug 765527 And Bug 765527 maybe uplifted to 16.0
Component: Untriaged → DOM
Keywords: regressionwindow-wanted
Product: Firefox → Core
Whiteboard: Regressed by: Bug 765527
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
tracking-firefox17:
--- → ?
tracking-firefox18:
--- → ?
tracking-firefox19:
--- → ?
Ever confirmed: true
Comment 3•12 years ago
|
||
Timestamp: 11/4/12 11:52:27 AM Error: TypeError: can't redefine non-configurable property 'top' Source File: http://www.spfldcycling.org/miles/report.js Line: 67 that file defines a top-level function named 'top'.
Blocks: CVE-2012-3994
status-firefox-esr10:
--- → affected
status-firefox16:
--- → affected
status-firefox17:
--- → affected
status-firefox18:
--- → affected
status-firefox19:
--- → affected
Updated•12 years ago
|
Summary: javascript fails on specific page → javascript fails on specific page due to defining top level function named 'top'
Comment 4•12 years ago
|
||
This page also fails to work in Chrome 22, but does work in Safari 5.1.7.
Comment 5•12 years ago
|
||
Renaming the function 'top' to something else should fix the problem.
Assignee: nobody → english-us
Component: DOM → English US
Product: Core → Tech Evangelism
Version: 16 Branch → unspecified
Comment 6•12 years ago
|
||
Thanks for the report and the regression range!
Updated•12 years ago
|
OS: Windows XP → All
Hardware: x86 → All
Reporter | ||
Comment 7•12 years ago
|
||
Thank you for finding an error in my javascript. I updated report.js on the web site and there are no issues with the pages. Too bad I didn't find a bug in Firefox, maybe next time :)
Comment 8•12 years ago
|
||
Looks like it is working on Chrome and Firefox now. Thanks for the update.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•12 years ago
|
Updated•9 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•