Closed
Bug 475767
Opened 17 years ago
Closed 17 years ago
Hotmail: impossible to write a new message using Minefield
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
RESOLVED
DUPLICATE
of bug 464074
People
(Reporter: mkohler, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090127 Minefield/3.2a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090127 Minefield/3.2a1pre
ATM it's impossible to write a new email in Hotmail using the nightlies (Minefield). The only way is to alter the UserAgentString.
I thought I should open a new bug for not using Bug 462428 as thread for this.
This is just a discussion since we can't do anything about this. Let's bring Mozilla to deliver the same code to all browsers!
(please feel free to mark this entry as invalid if you don't want to have a discussion thread in here.)
Reproducible: Always
Steps to Reproduce:
1. Go to hotmail.com and try to write a new eMail
Actual Results:
You can't type a message, because the input field is grayed-out.
| Reporter | ||
Updated•17 years ago
|
Version: unspecified → Trunk
Comment 1•17 years ago
|
||
There i
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Comment 2•17 years ago
|
||
sorry, submitted early by mistake.
The bug in Firefox is fixed and the other issue is a hotmail one.
There is nothing to discuss
| Reporter | ||
Comment 3•17 years ago
|
||
okay.
Updated•17 years ago
|
Resolution: DUPLICATE → INVALID
Comment 4•17 years ago
|
||
(In reply to comment #2)
> the other issue is a hotmail one.
Which, as far as I can tell, is why this bug was filed in the first place.
In your opinion, Matthias, is the issue TE-worthy and not already covered by other bugs?
Comment 5•17 years ago
|
||
TE has a ticket open for this, might as well dupe
Resolution: INVALID → DUPLICATE
Comment 6•17 years ago
|
||
sorry mid-aired with you, feel free to undupe :)
Comment 7•17 years ago
|
||
which should be itself a dupe of bug 396259 and both are not TE worthy because MS doesn't care for beta browsers if they are not from them.
Comment 8•17 years ago
|
||
(In reply to comment #7)
> which should be itself a dupe of bug 396259 and both are not TE worthy because
> MS doesn't care for beta browsers if they are not from them.
The point isn't that M$ doesn't care about beta browsers; the point is that they don't care about any Gecko browser not named, specifically, "Firefox".
If they want to block betas because they're "prerelease software", that's fine. I don't think anyone really cares about that. But that's not what they're doing now, and it's not what most TE bugs that are dependencies of bug 334967 are about.
Comment 9•17 years ago
|
||
(In reply to comment #8)
> (In reply to comment #7)
> > which should be itself a dupe of bug 396259 and both are not TE worthy because
> > MS doesn't care for beta browsers if they are not from them.
>
> The point isn't that M$ doesn't care about beta browsers; the point is that
> they don't care about any Gecko browser not named, specifically, "Firefox".
>
> If they want to block betas because they're "prerelease software", that's fine.
> I don't think anyone really cares about that. But that's not what they're doing
> now, and it's not what most TE bugs that are dependencies of bug 334967 are
> about.
I believe that Firefox 3 and above also faces this problem.
It is only Firefox 2 that escape from this problem, since other non-firefox browsers will work if their user agent is set to firefox 2.0 .
This bug is not a dupe of bug 396259 because it talking about different issues from this bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•