273628 - yahoo.com - Errors in javascript console

Status: RESOLVED WONTFIX

(Tech Evangelism Graveyard :: English US, defect, P1)

Description

[Moiz Dohadwala]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041205 MultiZilla/1.6.4.0b
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041205 MultiZilla/1.6.4.0b

Error: Error in parsing value for property 'font'.  Declaration dropped.
Source File: http://my.yahoo.com/
Line: 14
Error: Error in parsing value for property 'cursor'.  Declaration dropped.
Source File: http://us.js1.yimg.com/us.yimg.com/lib/my/ym_gt_a_20.css
Line: 3
Deprecated property window.title used.  Please use document.title instead.
Error: Error in parsing value for property 'font'.  Declaration dropped.
Source File: http://us.js1.yimg.com/us.yimg.com/lib/my/ym_gt_a_20.css
Line: 5

Followed by tons of other errors in the same .css file


Reproducible: Always
Steps to Reproduce:
1. Tool Menu --> Web Development --> Javascript Console.
2. In the javascript console, click the clear button to remove all errors/warnings
3. In the browser navigate to http://my.yahoo.com.
4. In the javascript console, the errors appear.




I noticed the errors when i tried to add content to the front page and tried to
add news modules to the front page and nothing happened when i clicked on the
add buttons. Then when I brought up the javascipt console i saw a large amount
of errors and warnings.

It appears that Yahoo is not Gecko compliant. This is a huge knock for Mozilla
to have such a prominent web-portal not be compliant with it.

Comment 1

[Felix Miata]

Conforming summary to TFM item 10 at 
http://www.mozilla.org/projects/tech-evangelism/site/procedures.html#file-new

Reporter, when you file a TE bug, please follow the reporting guidelines.

Comment 2

[gabe]

duplacate of bug 152298

Comment 3

[Chris Lawson (gone)]

(In reply to comment #2)
> duplacate of bug 152298

Definitely not.

However..."Gecko-compliant" does not necessarily mean "zero CSS errors."

There are a metric shitload of legitimate TE bugs with Yahoo, where by "bug" I mean "things that are actively broken". As far as I can tell, none -- zip, zero, zilch -- of the errors in Yahoo's CSS are actually a problem.

WONTFIX. We're not wasting TE resources trying to get Yahoo to be 100% W3C compliant.