Yahoo Pledges Full Firefox Support
homerj79 writes "News.com.com is reporting that Yahoo! has pledged full support of Firefox across its entire site. Despite its search bar for Firefox, which was launched in February, users still had to revert back to IE for certain features of Yahoo, like customizing your Yahoo Messenger avatar via the web. A specific date has not been set, but the company did say it would not launch any new services until all existing one supported Firefox." Update: 03/18 18:24 GMT by Z : GraffitiKnight (among many others) wrote in to mention that the claim has been retracted by the Yahoo! central office.
(Heard Wednesday at SDWest) Even ASP.NET 2.0/VS 2005 will have (better) support for Firefox. It sure perked up my ears. What's their plan?
A feeling of having made the same mistake before: Deja Foobar
"...but the company did say it would not launch any new services until all existing one supported Firefox"
No, they didn't say that. They said they wouldn't launch any new services until making sure they worked with Firefox. They don't have a timeline for when they get all existing services supported on Firefox and, not surprisingly, don't want to hold off on launching new services for an arbitrary period of time.
sigs are a waste of space
A quick fix is hitting Ctrl + and then Ctrl -
then use a Hosts file, that combined with adblock and eDexter means i havent seen an advert/banner on yahoo in months !
Yeah, it used to do that for me. But nightly builds solve the problem just fine. The Moox 1.0 build also works fine. If you don't like those solutions though, there's also the slashfix extension.
This just comes up again and again, doesn't it? Let's recap:
That would suggest an issue with your filter set, not with Yahoo.
I don't use yahoo, but in about 15 seconds, I came up with this:
http://us.a1.yimg.com/*/promotions/*
Turned it on and didn't see any more ads come up. It may need tweaking after ad rotations.
Hope that helps.
use the ctrl + and ctrl - shortcuts to increase the text size, then reduce it back to normal. This will re-render the page properly. Why this works, I have no idea.
There are some people that if they don't know, you can't tell 'em.
whenever I browse Slashdot with Firefox the page just doesn't seem to be drawn correctly.
See that little icon in the upper right corner? The one that if you mouseover says "Firefox Upgrades to Download" or somesuch?
Try clicking on that and downloading the upgrades.
I did that and since then have never had any problems.
Now, the stories I could tell about WebPine glitches are another matter...
-- Tigger warning: This post may contain tiggers! --
Posted today:
9 020384,39191834,00.htm/
http://news.zdnet.co.uk/software/applications/0,3
----- Open Source = More Secure (mmmmkay)
Opera is a popular browser???
m l/
http://www.onestat.com/html/aboutus_pressbox36.ht
Browser Usage...
1. Microsoft IE 87.28 %
2. Mozilla Firefox 8.45 %
3. Apple Safari 1.21 %
4. Netscape 1.11 %
5. Opera 1.09 %
Just because YOU use it, doesn't make it "popular".
----- Open Source = More Secure (mmmmkay)
Yahoo! have retracted their promise: not everything will be Firefox-compatable after all.
view source
...HREF="//slashdot.org/index.rss" TYPE="application/rss+xml">
...
save as
upload check on validator
File: C:\slashdot[1].html
Encoding: utf-8
Doctype: HTML 3.2
Errors: 119
No Character Encoding Found! Falling back to UTF-8.I was not able to extract a character encoding labeling from any of the valid sources for such information. Without encoding information it is impossible to reliably validate the document. I'm falling back to the "UTF-8" encoding and will attempt to perform the validation, but this is likely to fail for all non-trivial documents.
So what should I do? Tell me more...
This page is not Valid HTML 3.2!
Below are the results of attempting to parse this document with an SGML parser.
Line 4, column 80: there is no attribute "TYPE"
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).
This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.
How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.
Line 11, column 11: there is no attribute "TOPMARGIN"
TOPMARGIN="0" LEFTMARGIN="0"
Line 11, column 26: there is no attribute "LEFTMARGIN"
TOPMARGIN="0" LEFTMARGIN="0"
Line 12, column 13: there is no attribute "MARGINWIDTH"
MARGINWIDTH="0" MARGINHEIGHT="0">
Line 12, column 30: there is no attribute "MARGINHEIGHT"
MARGINWIDTH="0" MARGINHEIGHT="0">
Line 16, column 8: there is no attribute "BGCOLOR"
bgcolor="#cccccc" style="border-top: 1px #999999 solid; border-bottom: 5px #0000
Line 16, column 24: there is no attribute "STYLE"
bgcolor="#cccccc" style="border-top: 1px #999999 solid; border-bottom: 5px #0000
Line 18, column 46: there is no attribute "STYLE"
Line 76, column 15: element "NOBR" undefined
You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "" element), or by using vendor proprietary extensions such as "" or "" (this is usually fixed by using CSS to achieve the desired effect instead).
Line 90, column 16: an attribute value must be a literal unless it contains only name characters
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 123, column 15: element "NOBR" undefined
Line 132, column 15: element "NOBR" undefined
Line 144, column 16: element "NOBR" undefined
Line 154, column 16: element "NOBR" undefined
Line 175, column 41: character "%" is not allowed in th
Huh. I hadn't noticed that since I don't usually try to navigate the front page with the keyboard.
Typing anything while on the page puts what you type into their search box, even if you click out of the search box first. However, ctrl+f and typing into the find box works (Mozilla 1.7.3, Windows XP). Luckily this is only true on the front page. You can still keyboard navigate other pages, if you can get to them.
File names get truncated when file attachments are downloaded in Yahoo! Mail (in Firefox, but not in IE).
For example,
"Water_Sample_from_Your_Kitchen.doc"
becomes
"Water" (no file extension, usually)
"Water Sample from Your Kitchen.doc"
also becomes
"Water"
I've tried contacting Yahoo! Mail Help about it multiple times, but they kept responding saying that they didn't see the problem. But I've seen in Mozillazine and independent blogs that other people have reported the same problem.