Closed Bug 283390 Opened 20 years ago Closed 17 years ago

sovsport.ru - piece of JavaScript code displayed in page (incorrect HTML sent to Firefox)

Categories

(Tech Evangelism Graveyard :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: vic, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In the page (see the URL) FF throws a JS error and stops the execution of
script, the page is displayed incorrectly then. It doesn't happen in 1.0, but
happens in Trunk builds both with new and old profiles.
Screenshot: http://hkitchen.quakesrc.org/js.png

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.sovsport.ru/

Actual Results:  
You see the JS errors and malformed page

Expected Results:  
Display the page properly
None of the error messages in your screenshot have anything to do with the
behavior you mention.

The page has <iframe...>...</iframe>");.  Of course "); is going to be
displayed. The site sends different HTML to IE.
Assignee: firefox → other
Component: General → Other
Product: Firefox → Tech Evangelism
QA Contact: general → other
Summary: Firefox throws a JS error causing the page to be displayed incorrectly → sovsport.ru - piece of JavaScript code displayed in page (incorrect HTML sent to Firefox)
But why does it happen in Trunk builds only? Do Aviary builds have a slightly
different JS parsing code?
The only problem I see in the Error Console now is

Error: uncaught exception: Permission denied to call method Location.toString

and the page displays identically in Camino trunk and Firefox 2, as well as Safari 3. I think they've done a redesign since this was filed.

FIXED.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
OS: Windows XP → All
Hardware: PC → All
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.