Closed Bug 468212 Opened 16 years ago Closed 16 years ago

new version of Yahoo mail blocks Shiretoko on user agent string

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 334071

People

(Reporter: notforyourmail, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081205 Shiretoko/3.1b3pre
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081205 Shiretoko/3.1b3pre

Yahoo mail will not let you use their newer (AJAX) interface if you are using the Firefox 3.1 beta.  They block it as an unsupported browser.  Setting the user agent string to the string for older versions of Firefox makes mail work perfectly.

Reproducible: Always

Steps to Reproduce:
1.  Run the latest 3.1 beta
2.  Go to mail.yahoo.com  (it may help to delete your cookies for mail.yahoo.com if you have any.)
3.  Log in, and attempt to use new mail interface
4.  Get a message from yahoo saying the browser is blocked because it is unsupported.  The message suggests that you use another browser, and gives you the option of using mail with the old interface.
5.  Switch the user agent string to that of an older version of Firefox (say, 3.0.4).
6.  New yahoo mail interface works perfectly.
Actual Results:  
Get a message from yahoo saying the browser is blocked because it is unsupported.  The message suggests that you use another browser, and gives you the option of using mail with the old interface.

Expected Results:  
Should be able to use Yahoo Mail with the new interface.
Assignee: nobody → english-us
Component: General → English US
OS: Mac OS X → All
Product: Firefox → Tech Evangelism
QA Contact: general → english-us
Hardware: Macintosh → All
Dupe of bug 448184, bug 334071.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.