Closed Bug 686250 Opened 14 years ago Closed 14 years ago

jquery/cycler does not work in some circumstances.

Categories

(Core :: DOM: HTML Parser, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: royv, Unassigned)

References

()

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20100101 Firefox/7.0 Build ID: 20110908135051 Steps to reproduce: Browse to: http://ntbs.screenpeace.net/home.php?page=aboutus Actual results: The images on the right of the page, lower half, should cycle through (using jquery and the cycler function) but they don't. Expected results: The images should cycle through one after the other (in two separate blocks). IE and Opera work. Note that this DOES work in firefox for this page: http://ntbs.screenpeace.net/home.php?page=calendar
Works in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.22) Gecko/20110902 Firefox/3.6.22 ID:20110902133716 Fails in Mozilla/5.0 (Windows NT 5.1; rv:9.0a1) Gecko/20110911 Firefox/9.0a1 ID:20110911030845 Also fails in SeaMonkey 2.3 so kicking to Core. No relevant errors in the error console. Can you provide a reduced test case (the least amount of code to show the issue)? It would also be helpful if you could find a regression window Instructions at http://harthur.github.com/mozregression/
Product: Firefox → Core
QA Contact: general → general
I'll have a go at finding a regression window sometime tonight. I'll play with getting the bug to appear in less code over the next few days.
Result of regression window testing: Last good nightly: 2010-05-03 First bad nightly: 2010-05-04 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=83c887dff0da&tochan ge=d6bb0f9e9519
Since the HTML 5 Parser had been pref'ed on that Time, I can confirm that with html5.parser.enable;false set, the Issue isn't happening.
Component: General → HTML: Parser
QA Contact: general → parser
Version: 7 Branch → Trunk
My apologies people. In endeavoring to provide a reduced test case, I discovered some invalid html further up the page. Correcting that fixed the problem. Seems that pre the HTML 5 parser, Firefox was more forgiving of crud code. Sorry to have taken up your time on this.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.