Closed Bug 427329 Opened 16 years ago Closed 14 years ago

flash opens site well, but when I click on the options, for example, games, crossword, it will not open the link. Firefox 2.0.0.1 opens it fine.

Categories

(Core :: DOM: HTML Parser, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jfairbanks76432, Unassigned)

References

()

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

what else can i say

Reproducible: Always

Steps to Reproduce:
1.click on games
2.cllck on crossword
3.
Actual Results:  
does not open

Expected Results:  
should open the crossword
Also occurs on Linux.  Regression range: 2008-03-14-04 -- 2008-03-15-04
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-03-14+03%3A00&maxdate=2008-03-15+05%3A00&cvsroot=%2Fcvsroot
Bug 420148?
Status: UNCONFIRMED → NEW
Component: Extension Compatibility → Plug-ins
Ever confirmed: true
Keywords: regression
OS: Windows XP → All
Product: Firefox → Core
QA Contact: extension.compatibility → plugins
Version: unspecified → Trunk
Hmm, backing out bug 420148 locally did not help, might be more needed,
or it might be something else...
... the odd thing is that it appears we start to load the correct page,
I can see the background changing to green when selecting an item in
the Games menu, changing to red when choosing News etc.
Then the new page load is redirected back to the start page.
Backing out bug 311366 locally fixes it for me.
Blocks: 311366
Component: Plug-ins → HTML: Parser
QA Contact: plugins → parser
Might the <IE:homePage ID="oHomePage" /> tag be the problem?
Flags: blocking1.9?
Blake is super short on time, so it would be great with a minimized testcase here. There is even a risk that the change here is intentional.
I think the problem is that <foo:bar /> needs to become empty as in, AFAIK, IE. In IE /> is reportedly special when the tag name has a colon.
Hmm. <IE:homePage ID="oHomePage" /> becomes a container in Safari 3.1 as well.
A minimised testcase would be useful here. I am having great trouble working out what's going on.
When we get a minimized test case, re-nom.  
Flags: blocking1.9? → blocking1.9-
The site has fixed itself.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.