Microsoft Sends Broken Stylesheets to Opera 957
An anonymous reader writes "The Register has a story that the MSN homepage serves a different style sheet to the Opera web browser that makes Opera appear to be broken. Is this deliberate or a mistake? Who can possibly say? Opera's own take on the situation can be found here." This is not the first time.
No fear of prosecurion, no problem! (Score:5, Insightful)
Send us your Linux Sysadmin [librenix.com] articles.
Re:No fear of prosecurion, no problem! (Score:5, Funny)
Drat, I must have missed the good days.
Re:No fear of prosecurion, no problem! (Score:3, Funny)
Re:No fear of prosecurion, no problem! (Score:5, Informative)
MSDN [microsoft.com] has a similar behavior. I don't give a shit about MSN, but I needed to download the DirectX 8.1 SDK (to use OGRE [sf.net]) the other, and it was hell. I fact, I needed to identify as Mozilla 5 to see more than a few unrelated links on this page [microsoft.com] (try it if you have Opera. Change your identifier and reload the page)
Re:No fear of prosecurion, no problem! (Score:4, Funny)
Maybe they don't want to. But Internet Explorer certainly does.
Re:No fear of prosecurion, no problem! (Score:4, Insightful)
But is someone forcing you to use Hotmail?
i dunno (Score:5, Insightful)
never attribute to malice that which can be explained by stupidity.
Re:i dunno (Score:3, Insightful)
Modifying SMB to break Samba could well be worth the potential bad press. Why would Microsoft care about Opera? Or think that misrendering the MSN home page is a good way to undermine it? And decide that the rewards outweigh the downside of such obvious meddling?
It just doesn't make sense to me. If they did the same thing to Mozilla or Konqueror/Safari, that I could see...
Re:i dunno (Score:3, Insightful)
Opera is becoming a serious contender in the mobile arena. This is an area that Microsoft cares a good deal about. Doing that to Mozilla would generate too much press, and as for Konqueror, that isn't even a real competitor on the windows platform or in the mobile arena.
They would do this. This is just the type of crap that monopolies pull, largely because they can.
Re:i dunno (Score:5, Interesting)
Just wanted to say that I'm glad you took a moment to take a step back and and say "Why?" as opposed to jumping the gun and saying "Damn MS trying to enforce it's monopoly as usual". Frankly, I'm tired of the wild assumptions that MS works that way.
As an Opera user and a Windows user, you can understand that I've run across exactly this problem. I'd like to share with you a few observations I've made on this topic:
- As an Opera user, I find myself having to deal with a number of sites that just don't care about me. Having IE available as a backup is just part of my everyday Opera life. I don't see MS as being very different here. Some sites block me totally, like the site I use to send payments to my credit card.
- Because of my having to keep IE on hot standby, it doesn't even occur to me anymore to email MS (or any other site) and complain about lack of Opera testing. If they don't get feedback, they ain't gonna fix it.
- Website maintenance is a perpetual, priority based job. Often problems are ranked by how many people are affected by them. Truth be told, Opera's just not significant today in light of other things going on. I wouldn't be a bit surprised if nobody there had Opera installed. Anybody who's ever done web development at a Dilbert-esque corp would probably understand this.
- Wouldn't it be weird that MS would break Opera, but not Mozilla, Netscape, or other browsers?
- What possible benefit could that bring them? Despite my comment earlier, Opera handles the vast majority of sites(*) just fine. When I run across a site that doesn't work with Opera, it feels like the operators of the site were moronic, not that Opera is incompatible. In other words, MS's site not working right with Opera makes MS look incompetant, not Opera. * Sites that I personally have visited, other people's experiences may vary.
- MS's site is a marketing tool. Head on over there and you hear all about TabletPC's, PocketPc's, MS's latest server stuff, Windows XP, etc etc etc. Breaking their site means potentially shoo'ing off customers. I seriously doubt any PHB would want to do that.
If other Opera users share my observations, then it actually makes sense that MS just doesn't care. But the idea that they're doing it to enforce a monopoly is not so evident.
Please don't flame me for not jumping on the "MS is like OCP!!!" bandwagon. I'm just the type of person that'd rather look at all the details than try to find details to support a bias.
READ THIS FOR EVIDENCE AS TO WHY IT HAPPENS (Score:5, Informative)
1st piece of evidence:
Amaya and Netscape Nav 4.7 both get fed the same stylesheet that Opera gets. Indicating that the site checks for Netscape 6 and above, and IE 6 and above only, providing a default style sheet to all other browsers.
2nd piece of evidence:
Mozilla gets the Netscape 6 stylesheet, which has the SAME bug that the default (passed to Opera) stylesheet has. The same -30px margin is passed to it, but Mozilla renders it correctly (latest build).
3rd piece of evidence:
Netscape Navigator 4.7 MANGLES the front page of MSN if you set the margin-left property to 0px instead of -30px. Here's NS4.7 showing the page with a modified site.css stylesheet:
http://home.earthlink.net/~simoncook
Whereas here is Netscape Navigator 4.7 using the unmodified stylesheet (the same one passed to Opera):
http://home.earthlink.net/~simoncooke/ns47orig.
Now, if you take a look at most sites, you will see that the most popular browsers are IE, followed by Netscape Navigator 4.7, followed by Netscape 6.x (including Mozilla), and finally trailed VERY FAR BEHIND by Opera.
http://www.sla.org/stats/conf2003/conf2003_sep0
Now if you were to realistically act as a site designer, you would go out of your way support IE, Netscape 6.x and company, and Netscape 4.7 -- which is the 2nd most used browser in the world.
And guess which browser needs a bugfix so that it doesn't crash when you pass it a stylesheet it doesn't understand, and so that it doesn't screw up the layout?
Yep, that's right, Netscape 4.7. Our 2nd place winner, and the one that this "horrible, Opera breaking stylesheet" was *actually* written for.
You know, a little research and a little critical thinking might not have set you down this path in the first place.
Simon
Re:i dunno (Score:5, Insightful)
It took microsoft SIX MONTHS to fix a one-liner that prevented Mozilla from working with Passport (buggy browser "detection" code). See bugzilla bug #141279 if you are curious. Interoperability and open standards are not placed anywhere near the top of the queue at Microsoft. In fact, the dragging of feet would point to more sinister motives... but of course there's no proof of such (without Halloween memos, at least).
Re:i dunno (Score:5, Insightful)
The point is that the page rendered exactly same as IE provided the stylesheets are same. Unless MS thinks there is something wrong with the way IE(or Opera7) displays the page, why type out a different stylesheet and commit a typo in the process ? If it ain't broke, fix it to break it ?
I doubt it (Score:5, Insightful)
By the way, the full quotation is:
"Never ascribe to malice, that which is adequately explained by incompetence"
- Napolean Bonaparte.
I think one of Microsoft's new unwritten policies is "When accused of malice, always hide behind incompetence".
"No no... we'd love to, but we simply CAN'T remove IE from Windows." Sound familiar?
Re:i dunno (Score:3, Informative)
Re:i dunno (Score:5, Insightful)
but it really looks like an honest typo in the style sheet.
Really? Let's look and see...
MSIE stylesheet:
Opera stylesheet:
I don't know how you go about typing, but I'd have to throw silly putty at the keyboard from the other side of the room to hit the "-" key instead of the "2".
Re:No fear of prosecurion, no problem! (Score:3, Informative)
I wouldn't be suprised if there are many more Opera users than there were DR-DOS users. The number of PCs has exploded in the past several years, and Opera is a pretty well-known name among browsers.
Re:No fear of prosecurion, no problem! (Score:3, Funny)
Standards schmandards. (Score:4, Insightful)
Anyone, including Microsoft, who writes a site that serves seperate pages to different browsers is doing a disservice to the public.
Re:Standards schmandards. (Score:5, Interesting)
My browser is set to send nonsense as its id strings; it doesn't seem to do my surfing experience much harm.
Re:Standards schmandards. (Score:3, Funny)
Coincidentally, so are most web servers.
Re:Standards schmandards. (Score:4, Informative)
How the HELL did this get modded to 5?!? RTFA, the problem is MSN sending a perfectly-compliant, but deliberately flawed in values, CSS style sheet *only* to the Opera 7 browser. Note that the sheet values were chosen to instruct O7 to misrender the pages. Nothing the W3C can do about this, standards compliance wasn't the problem.
Re:Standards schmandards. (Score:5, Interesting)
Of course, it would be lovely if all browser makers were to forced to follow the recommendations down to the nitty gritty, but even the recommendations don't always provide strict requirements on how a property or class should be rendered.
The fact that Microsoft is pushing out (delibrately) a broken style sheet is just wrong.
Re:Standards schmandards. (Score:5, Insightful)
Anyone, including Microsoft, who writes a site that serves seperate pages to different browsers is doing a disservice to the public.
While I agree with the philosophy, unfortunately it's unrealistic. Reason: so many browsers, worst among them Netscape 4, try to support CSS and fail so miserably that a standards-complaint CSS page is likely to be unreadable. And, unfortunately, some people still use NS4 and old versions of IE.
What I've done some places is write some SSI that detects the browser. If it detects Netscape 4 or lower, or IE ... probably 4 or lower, I forget at the moment ... it sends a "dumbed down" style sheet that will present only a faint echo of the layout of the page, but which will leave the text readable. Any other browser, you get the normal "standards compliant" style sheet. Note that here I am sending specific style sheets for specific browsers-- but I assume that any version of Opera, and any version of Netscape or Mozilla 5 or greater and any recent IE and any other browser that may come is standards complaint.
-Rob
Re:Standards schmandards. (Score:4, Interesting)
Re:Standards schmandards. (Score:5, Informative)
Here's a tip for including CSS without having to worry about NS4 and (I think) IE4 screwing it up:
Use the CSS2 @import rule to import your style sheet.
The version 4 browsers will ignore this tag, therefore you don't have to worry about crashing NS4 with your perfectly valid CSS.
Example:
Re:Standards schmandards. (Score:5, Informative)
Re:Standards schmandards. (Score:3, Interesting)
Re:Standards schmandards. (Score:3, Interesting)
Hmmm... although the thing is, the item in the stylesheet which they claim is broken (ul tag style) is the same in the Nav6 stylesheet.
Mozilla renders the page perfectly, and it gets the nav6 stylesheet with that very same ul {} declaration... here's all three listed together:
Opera: ul {list-style-position: outside; margin: -2px 0px 0px -30px; list-style-image: url(http://msimg.com/m/8/bullet-black.gif);}
Nav 6: ul {list-style-position: outside; margin: -2px 0px 0px -30px; list-style-image: url(http://msimg.com/m/8/bullet-black.gif);}
IE6: ul {list-style-position: outside; margin: -2px 0px 0px 8px; list-style-image: url(http://msimg.com/m/8/bullet-black.gif);}
Looks like human error to me.
Simon
Re:Standards schmandards. (Score:3, Interesting)
This may or may not be true; I've seen some quite impressive standards compliant sites that seem to work in many of the major browsers. But does that excuse feeding a deliberately broken style-sheet to a competitor's browser, and only to that browser? I would say not.
Re:Quite the contrary (Score:3, Insightful)
I can write a page that looks good in EVERY browser, including NS4 and lynx. So can you... so can anybody...
all it takes is a little time, and a bit of a brain.
Unfortunately, far to many people in web dev don't have brains, and far too many to "save time" use wysiwyg crap to gerate code for them.
having muyltiple pages for multiple browsers is a sign of not doing it right the first time, not a 'service'.
Re:Quite the contrary (Score:3, Insightful)
all it takes is a little time
"
No! It's _easier_ to write bread-and-butter HTML that looks _fine_, if a little unexciting, than it is to write anything that could break any half-decent browser (i.e. one that understands what it's told, like w3m or opera).
YAW (who writes his boring but perfectly usable (100-hits a day on some pages, which ain't too bad) web-pages using 'cat > filename')
Re:Quite the contrary (Score:3, Informative)
I suspect you can write a page that works in every browser that looks decent. I also suspect that, in doing so, you are violating W3C WAI guidelines, or at least being shortsighted in your compliance with them.
(I could be wrong about that, I have no idea who you are or what work you do. This is simply my general experience and please pardon me for jumping on you!)
The biggest problem with supporting every browser is that you're mixing up content with layout. You are most likely using tables for layout; if you know how to make a page look good in NS4 without doing that, let me know. The problem with this is that assistive devices try to comprehend your page by seperating content from layout, and tables are supposed to be used for content, and CSS for layout. But NS4 doesn't even begin to support that properly. This is an issue right now for WAI people and those of us who have to make our sites 508 compliant, but it's going to be more of an issue in the future as all browsers will need to clearly differentiate between layout and content.
We made the decision to simply stop supporting NS4 and comply with HTML 4.0 and CSS2. These are no longer cutting edge standards, and it does give our designers a lot more freedom in how a site looks. Yes, they -could- design something to work in every browser (and we did, until recently) but it is a whole lot of extra work to design something with tables and deal with all of the stuff that entails. So it's not a 'we're too dumb' thing, it's a 'we'd rather devote our creative energies to something that complies with standards that are now a couple years old than support a browser > 3% of people still use.'
And if we get someone who complains that they can't access our stuff with NS4, we mail them a CD with Mozilla or Phoenix. Your tax dollars at work.
Cheers,
Aquitaine
Program on Employment and Disability
Cornell University
Re:Quite the contrary (Score:5, Insightful)
If you are creating multiple copies of resources for different user agent strings, then it is a prime indication you haven't understood the very simple concept of the World Wide Web.
Making a website accessible does not mean text-only. This is a myth, and a badly misinformed piece of strawman fluff. Text-versions of websites should only be a last resort, when you've reached the point where you admit your design and markup skills are inadequate to do even a competant job, let alone a good one. Accessible websites can also be well designed, there's no mutual exclusivity.
If you so strongly want to believe this nonsense, please post a reference to either a standard or recommendation that states that User-Agent is a mandatory HTTP parameter. You know as well as I do that User-Agent strings are optional, and relying on them to determine presentation is so typically short-sighted that its now laughable.
You cannot succeed over the medium to long term adopting a browser-sniff route. It is folly.
Opera should respond (Score:5, Funny)
Re:Opera should respond (Score:5, Funny)
Re:Opera should respond (Score:5, Funny)
We need browser masking. (Score:3, Interesting)
I've heard plenty of stories of forms suddenly working when a feature in a browser was changed to show Internet Explorer for Windows/Mac, and otherwise breaking when they work just fine. Or in my case, I came across a site that said IE and Netscape only, but used Opera and it worked perfectly - this sort of ignorance on the part of web developers really is intolerable.
Re:We need browser masking. (Score:3, Informative)
Re:We need browser masking. (Score:5, Insightful)
As an unfortunate side-effect, this would reinforce webmasters' belief that everybody in the world uses MSIE.
Yep. What we really need is too late to accomplish. What we really need is a protocol that forbids you from identifying which browser you are, but only allows you to specify to which standards you conform.
Then maybe webmasters would write their HTML and such the way they're supposed to, and what's more the browsers would have to really support the standards they claim to support.
But, unfortunately, that's an ideal world, not the one we live in.
-Rob
Aww, come on... (Score:3, Funny)
Re:Aww, come on... (Score:4, Funny)
Standards and lies (Score:5, Insightful)
Re:Standards and lies (Score:5, Insightful)
Extend and enhance (also known as extend and extinguish) is not the way to go about making a standards-based system. There are standards. They are not mutable, they are not extensible (except where stated).
In this particular case, they purposely serve a messed-up CSS stylesheet to Opera. If you browse with CSS turned off, the site looks fine. So, regardless of their adherence to standards (which is not very good), they purposely try to monkeywrench Opera. That's the point of this story, really. Every page should render identically on every browser. All information should be visible on every browser. Purposely hiding your text under a graphic is unacceptable behavior.
Re:Standards and lies (Score:5, Insightful)
every browser, even Opera: Real-world example [webreference.com]
There are no chance that they would have gone through the process to server different code to different browsers without testing it out afterwards.
IE on macintosh is reported to work very good, and there are XML engine updates for Windows to download. This all points to the fact that microsoft is very capable of actually supporting the standards, but we also know that standards would give people no reason to prefer IE over some other browser.
Re:Standards and lies (Score:5, Informative)
Yes, you can see the page, but it's not doing WHAT it SHOULD.
Sites del. diff. content to different browsers... (Score:5, Informative)
..is fucking irritating. Don't mess with it!
NO! It it not necessary. It just makes things worse in the long run, so if you're doing this _you're_ part of the problem, so don't complain about how you have to treat browsers differently.
Sheeesh. Write to the standards, not browsers.
(And no, this isn't "insightful", it's totally _obvious_ to anyone with a clue)Re:Sites del. diff. content to different browsers. (Score:5, Insightful)
This is fine for a personal or hobby site but for e-commerce, you need to write to users, not standards. It makes no difference to the user that your page is coded to standards if he/she can't view it. Telling them they need a different browser isn't the answer either. Showing them what they want, in a manner that works correctly with their browser, is unfortunately the best solution if you want to be profitable.
I've had to code drop down menus differently for different browsers to get things to look the same, however when I'm done, you get the exact same page, with everything the same size and in the same place in IE, Netscape, Mozilla, and Konqueror. I've never used Opera so I don't test that one, but I guess I probably should.
Re:Sites del. diff. content to different browsers. (Score:3, Insightful)
Clearly you use IE as your default browser. As an avid user of non-Microsoft browsers (Phoenix, in my case) it is almost a daily occurence that some site blocks me based on my user-agent ID and tells me to go download IE. I'm sure you have also seen "Best viewed with Internet Explorer" bottons before, too. Your argument is specious.
Oddity to me (Score:5, Interesting)
Re:Oddity to me (Score:5, Insightful)
Of course, I am happy with Moz and never think of using MSN. But that's just me.
Re:Oddity to me (Score:3, Interesting)
Hotmail worked fine with Safari just after Safari was released, then Microsoft changed something later in the day and all Safari users now get odd Javascript error messages when attempting to log on to Hotmail.
Clicking on the "help" link brings you into your account, and once in, everything works just fine (and faster than IE on the Mac as well).
logically speaking.... (Score:5, Insightful)
one would think that since they want people coming to this page and accessing it regularly they would make it easier for them to get here.
conspiracy theory aside this doesn't make sense from a business point of view. i have a feeling this is a mistake of some sort.
Re:logically speaking.... (Score:3, Informative)
Not Just opera broken (Score:5, Interesting)
Older version of IE were also purposely broken in the same way; forced obelesence? As a regular Opera user I notice the same problem on some portions of the Microsoft web site as well (not just MSN).
To me this just proves that the remedy isn't working, that MS as a company prefers dirty tricks to competition and that the states that have not agreed to settlement had better press MS hard. (Wow holy run on sentence batman). It's sad that a company as successful and as full of talented people as MS has to resort to this type of behavior when a competitor comes out with a good product.
I'm reminded of a famous quote "Can't we just all get a long". I guess if your MS and you can't or won't compete the answer is no.
so what? (Score:3, Insightful)
Who says it has to work with other companies browsers?
If you don't like it, either use IE (not me thanks) or not visit the website (that would be me).
Microsoft will notice the lack of ad revenue. Then they might fix it. If it is enough for them to care. Being that this is Opera, I kind of doubt it.
Re:so what? (Score:3, Insightful)
How can you call it a website if it doesn't work on the Web. I haven't seen an official definition of the World Wide Web that indicates what browsers are allowed and what browsers aren't allowed. Care to shed a light on a reference of this nature?
Now if someone can't author a website properly, calling it a website could be misrepresentative. Why not call it an IEsite, not a website - since it fails to meet the requirements of a website.
Re:so what? (Score:3, Insightful)
Uh, we do. As in, society does, in much the same way that we demand our kitchen appliances use the type of electricty that is most common in the country. In fact, the govt enforce such standards, partly to stop an electricty company trying to force its way into the market for cookers by giving you free "special" electricity that only works with its products.
Why can't I refuse to hire somebody because they are black, or because they drive a Fiat? Because that'd be unfair discrimination, and it'd be illegal. I don't see why it should be different for products. Clearly it's very easy to make it work OK in Opera, just remove the browser sniffing code.
When big companies pull tricks like this, everybody loses. The web becomes more fragmented, and some idiots might look at such behaviour and think that it's actually ok to do something similar.
MSDN didn't work with Mozilla UA for a while (Score:4, Informative)
Rather coincidentally, it was fixed shortly after I filled out a MSFT survey that appeared as I tried to leave the site - I claimed I was leaving because I was fed up with changing my UA string. Of course, I'm not conceited enough to think they fixed their problems because of me
Comment removed (Score:3, Funny)
Actually (Score:5, Interesting)
Re:Actually (Score:3, Interesting)
Try a 2 celled Excel spreadsheet, the left cell with a picture, and the right with a short bit of text. That's horrendous.
Although, believe it or not, not as bad as MSPublisher.
It is pretty easy to do (Score:5, Interesting)
www.wannabrowser.com (Score:5, Informative)
I'm not going to bother posting the results here but it's easy enough to see for yourself what the differences are.
Ben
What is the alternative? (Score:4, Interesting)
Re:What is the alternative? (Score:5, Insightful)
Are you sure?
Without consequence as to what?
Okay. I'll use your logic, and the same logic as some other posts here from Microsoft agents.
I want to start serving stuff from my site that takes advantage of all known exploits in IE browsers. After all, it's my site. I can serve whatever I want. It's my business.
If users don't like it, then they should use Mozilla or Opera.
If you're a Microsoft user, why would you want to come to my site anyway?
It's just an accident. Give me the benefit of the doubt.
I'll probably get modded redundant since my above four arguments have already been made.
Re:What is the alternative? (Score:3, Interesting)
But in doing so, MSN is making a very specific, very pointed, very inaccurate statement about the Opera web browser. That statement is, "Opera doesn't render web pages correctly."
Since Opera's success relies on public perception of the quality of their product, this amounts to slander. Since this is a Microsoft portal making the statement about a company that competes with Microsoft, it also raises antitrust issues.
I would also like to know how you got it in your head that, if we don't have legal recourse, the only alternative is to shut up and take it. People have a right to complain. People should complain. Opera users, specifically, should complain.
On a related note, I just spent twenty minutes on MSN.com, trying to find some sort of contact address. No dice.
Its not about free choice (Score:3, Interesting)
As far
M$ claims W3C compat...mistakenly? (Score:4, Interesting)
"We supported the latest W3C standards when developing the content and services delivered from MSN,"
But Visse recommended that for the best experience with MSN, customers should use a browser that tightly adheres to the W3C standard.
"If customers choose to use a browser that does not tightly support W3C standards, then they may encounter a less then optimal experience on MSN," he said.
except, that if you ask the W3C validator, it doesn't work!
www.microsoft.com [w3.org]
www.msn.com [w3.org]
Microsoft has a long history of intentionally breaking compatibility with other products to promote their own, as early as (and maybe earlier) the Windows 3.1 -> 3.11 "upgrade" which conveniently broke the diagnostic and repair software PC Tools.
In fairness (Score:3, Informative)
Slashdot and w3.org... (Score:5, Interesting)
Pretty childish, if you ask me.
J.
Re:Slashdot and w3.org... (Score:5, Funny)
Re:Slashdot and w3.org... (Score:5, Funny)
Slashdot: Microsoft Sends Broken Stylesheets to Opera.
The people: So what, you send broken HTML to everybody!
the reason they are targeting opera (Score:5, Insightful)
The reality is that most windows users will never change their browser from IE to something else, so they are not afraid of Mozilla, konq, Safari, etc.
The cellphone market on the other hand is HUGE, and given recent advances in wireless bandwith, has the potential to be highly lucrative.
More than likely its probably safe to say that a significant percentage of all web browsing in the future will be on cellphones.
They are attempting to ensure that non MS cellphones can't surf the web properly, in an attempt to make consumers prefer buying MS enabled webphones, which in turn will generate more revenue in the embedded market for them, which they desperately need.
Just my opinion tho - can never tell what does guys are up to...
Make Opera appear broken?? (Score:5, Insightful)
No problems with Mozilla as Opera (Score:5, Informative)
user_pref("general.useragent.override", "Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.1) Opera 7.0 [en]");
I restarted Mozilla (1.3a), checked the about page (it shows the user agent) and then visited the MSN page. The page showed up fine. I thought that maybe that maybe MS had changed the CSS. I downloaded the style sheet in Mozilla and saw the -30 there. From what I can tell Mozilla must have a check to ensure that text does not appear outside of the cell, not matter what the css indicates. If Mozilla can do it, then the guys over at Opera can do it too.
Note - I am not saying that this clears MS, as any well implemented web site should only need one version of any page, unless they have localization. What I am saying is that this is a fixable issue on the part of Opera.
opera vs. msdn (Score:3, Interesting)
Truly unrecognized browsers are treated similarly (Score:5, Interesting)
I messed around with a few other UserAgent strings, and it gets a little clearer:
"Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.1) Opera 7.0 [en]" -> site.css
"Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.1) Oprah 7.0 [en]" -> site-win-ie6.css
So far, exactly as reported in the article
"Mozilla/4.0 (compatible) Oprah 7.0 [en]" -> site.css
"Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.1) Oprah 7.0 [en]" -> site-win-ie5.css
"Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.1; Opera 7.0) Oprah 7.0 [en]" -> site.css
It's pretty clear what they're doing:
In other words, it doesn't matter what Opera claims to be compatible with - they always get the default sheet, just like a completely unrecognized browser does.
I'm trying to apply Hanlon's Razor here, but it's hard...
this is typical, the .NET framework does this, too (Score:5, Insightful)
the
I constantly have to hard-code formatting for controls because MS treats Netscape 6 as a 'down-level' browser and doesn't bother sending out certain formatting tags. So some pages look bad in Netscape 6, the reason behind it would be that the formatting tags weren't sent out because Netscape doesn't support them, but this is false because when I add them by hand, netscape handles them fine and my pages look the same in both browsers.
I have to believe that MS does this so people say "this page looks like azz in Netscape" and assume that it's Netscape's problem.
the framework has been out for too long and this is still not fixed, so I can not believe that it is an honest or innocent mistake.
Fortunately Opera lies, too... (Score:3, Insightful)
Breaking my own sites. (Score:5, Interesting)
In my industry, just about every site does video of some sort. There's always some group that feels they were intentionally blocked because of whatever reason. I've seen sites that stream exclusively Windows Media, and some that use propriatory plugins like "Emblaze".. Some were using the Netscape "Push" method (send a multipart header, and then send a new mime delimiter between frames). Netscape "Push" doesn't (or didn't) work with MSIE.. Windows Media doesn't work with Linux. (with a few exceptions).. Something doesn't work with something else.
If I choose to make my site not work with MSIE or Netscape, and only let Opera viewers see it, well, it's my site.. If Slashdot decides tommorrow that they like a feature of Mozilla 9.999, and it doesn't work with any other browser, including MSIE, how many of you are going to be bitching for MSIE compatability?
I'll get a bunch of comments back "Microsoft Sucks", but I'd *LOVE* it if they'd put the REMOTE_USER_AGENT string beside your name in the comments.
For those curious, mine is:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
I'm not defending Microsoft. It's shitty that they did it, but honestly it's their site. Try doing a Windows Update from Netscape, that doesn't work either.
Want more fun? Try installing a nice fresh copy of an older Microsoft OS (say WinNT 4.0), and get yourself up to day.. Years ago, they broke the Microsoft pages, so you couldn't get the updates. But I can't say that I've ever seen a
Where I work, we try our best to make our pages render correctly on our machines.. That means, keep everyone in the office happy, and hopefully it will make the majority of our customers happy. We have enough varity by choice to keep things interesting. here's the short list of the browsers we use:
Win98/Win2k/WinXP:
MSIE 5.0 -> MSIE 6.1
Netscape 4.7 -> Netscape 7.01
Mozilla 1.1 -> Mozilla 1.3a
Opera (unsure of version)
Mac: OS/9, OS/X
MSIE (unsure of version)
Netscape (unsure. various versions)
Mozilla (unsure. various versions)
Linux: (Slackware)
Mozilla 1.1 -> 1.3a
Netscape (various)
Konqueror 3.0.1
But sure as hell, we'll have some sort of rendering problem on some browser, and someone will scream that there's a conspiracy against them specifically..
Our sites don't require any special browser. They all work. We don't know of any compatability issues right now, but I'm sure someone will find that Konqueror v1.0 won't work with a particular page, if they try hard enough. Our site has average users browsing. Some advanced users, lots of regular users..
In the last 24 hours we had 17,017 different REMOTE_USER_AGENT strings sent to one of the servers, in 1,949,023 requests from 116,273 unique IP's.. If I take the list and:
cat list.txt | cut -f 1-3 -d ";" | sort | uniq -c > work.txt
less work.txt
Here's the top 10 results:
474500 "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1
317359 "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98
140794 "Mozilla/4.0 (compatible; MSIE 5.5; Windows 98
91425 "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0
66331 "Mozilla/4.0 (compatible; MSIE 5.0; Windows 98
31072 "Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0
29963 "Mozilla/4.0 (compatible; MSIE 6.0; AOL 8.0
26778 "Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0
25426 "Mozilla/3.0 (compatible
20841 "Mozilla/4.0 (compatible; MSIE 5.01; Windows 98
And in comparison, we'll look at some other top 10's.. Here's the top 11 Linux clients (11, because the first Opera was #11)
grep -i linux work.txt
1563 "Mozilla/5.0 (X11; U; Linux i686
387 "Mozilla (X11; I; Linux 2.0.32 i586
161 "Mozilla/5.0 (compatible; Konqueror/3; Linux
145 "Mozilla/4.7 [en] (X11; I; Linux 2.2.13 i686
96 "Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U
72 "Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U
67 "Mozilla/5.0 (X11; U; Linux i586
64 "Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686
56 "Mozilla/4.78 [en] (X11; U; Linux 2.4.9-34 i686
46 "Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U
39 "Opera/6.11 (Linux 2.4.2 i386; U
And the top 10 Opera clients.
127 "Opera/6.01 (Windows 98; U
118 "Opera/6.05 (Windows XP; U
104 "Opera/6.05 (Windows 2000; U
74 "Opera/7.01 (Windows NT 5.0; U
72 "Opera/6.05 (Windows 98; U
60 "Opera/6.0 (Windows 98; U
56 "Opera/7.0 (Windows NT 5.1; U
49 "Opera/6.0 (Windows 2000; U
41 "Opera/7.0 (Windows 98; U
39 "Opera/6.11 (Linux 2.4.2 i386; U
Ok, lets give better Opera numbers. It seems Opera has a few different formats for its browser string. Thanks guys. That helps me a lot..
The top 10 browser string with "Opera" anywhere in it are:
cat list.txt | grep -i opera | sort | uniq -c | sort -r -n -k 1
---
752 "Mozilla/4.0 (compatible; MSIE 5.0; Windows XP) Opera 6.05 [en]"
627 "Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows XP) Opera 7.0 [en]"
617 "Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.1) Opera 7.0 [en]"
378 "Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows 98) Opera 7.0 [en]"
277 "Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.1) Opera 7.01 [en]"
271 "Mozilla/4.0 (compatible; MSIE 5.0; Windows 2000) Opera 6.05 [en]"
246 "Mozilla/4.0 (compatible; MSIE 5.0; Windows 98) Opera 6.05 [en]"
222 "Mozilla/4.0 (compatible; MSIE 5.0; Windows XP) Opera 6.05 [de]"
194 "Mozilla/4.0 (compatible; MSIE 6.0; MSIE 5.5; Windows NT 5.0) Opera 7.0 [en]"
156 "Mozilla/4.0 (compatible; MSIE 5.0; Windows ME) Opera 6.05 [en]"
Or more specifically, lets find every Opera browser regardless of OS type.. That's just about as big as we can inflate your numbers.
cat list.txt | grep -i opera > work.txt
cat work.txt | grep ^\"Opera > a.list
cat work.txt | grep -v ^\"Opera > b.list
cat a.list | cut -f 2 -d \" | cut -f 1 -d " " > opera.id
cat b.list | cut -f 2 -d ")" | cut -f 1 -d \[ >> opera.id
And then a little cleanup in 'vi' to fix the leading space, and the space versus slash in the two types...
cat opera.id | sort | uniq -c | sort -r -n -k 1
---
2565 Opera/6.05
2488 Opera/7.0
678 Opera/7.01
549 Opera/6.01
537 Opera/6.0
438 Opera/6.04
336 Opera/6.03
105 Opera/6.11
63 Opera/5.12
47 Opera/6.02
47 Opera/5.0
43 Opera/6.0/\xa4/
32 Opera/5.02
30 Opera/4.0/Beta/4
28 Opera/5.11
27 Opera/5.01
21 Opera/6.01/~/
14 Opera/5.12/\xa1\xe8/
13 Opera/3.60
12 Opera/5.12/OCV2/
9 "
7 Opera/6.1
2 Opera
1 Opera/6.01/OCV2/
Now honestly, who should I be designing pages for? the 2,500 hits from Opera 7.0, or the 474,500 from "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1 ?
**WE** do respect peoples ability to choose what browser they want, and *WE* won't limit it, but I'd bet with these numbers in front of them, most bosses would have the pages designed for the majority..
If the decision were presented to me, wether to include a really great feature that works in Netscape and MSIE but not Opera, or not, and I did exactly what I just did, and saw that 8,092 of 1,949,023 hits came from Opera, that's
If Microsoft had half a clue (which I'm sure someone there does), and they checked to see what browsers were viewing, and *THEY* saw that
Won't help!! (Score:5, Interesting)
It looks like MSN uses more advanced techniques to find out what the client is than just the agent identification, in order to sabotage Opera in this case.
Opera uses a bad disguise (Score:5, Informative)
RMN
~~~
Re:Who uses Opera (Score:3, Insightful)
Isn't MSN meant to be commerically independent of Microsoft?
Re:Who uses Opera (Score:3)
I also use Konq once in a while when a site tells me I don't have the right browser. I have it set to report that it's IE and that works just fine. It really pisses me off that by telling the server it's IE, it can display the page perfectly. Why do people require a specific browser? That's just plain ignorance.
Re:Who uses Opera (Score:3, Informative)
it.
2) Mouse gestures. Another control method is
great
3) Speed and it's not an M$ product
4) Ability to disable/enable cookies/plugins/javascript/java/referrer logging/ gif animation/annonying embedded audio/popups from a single panel by pressing F12. Very handy.
5) Ability to turn graphics off completely.
6) Good CSS support (Opera7)
7) Zoom feature -- handy for guys like me with coke bottle glasses.
When I have to use other computers that don't have Opera or Mozilla installed it's a painful experience.
Re:Clearly This Sucks but.... (Score:5, Informative)
The problem here is that if you've set Opera to the report the true user-agent, MSN sends a page with a broken CSS file that tells the browser to render the content so that the page becomes unreadable--Here, they set a negative margin on content in some divs so that the first couple words in any column are overlapped by the div to the left, frustrating the viewer. Even IE chokes on the page they give to Opera:
http://deb.opera.com/howcome/2003/2/msn/opera7.
This is sabotage.
Read the original report here:
http://deb.opera.com/howcome/2003/2/msn/
Comment removed (Score:5, Interesting)
Re:Clearly This Sucks but.... (Score:3, Insightful)
Neat, huh?
Re:Clearly This Sucks but.... (Score:5, Informative)
Re:Clearly This Sucks but.... (Score:5, Insightful)
And, not to defend MS or anything... but how come EVEN THE OPERA.COM SITE NEGLECTS TO MENTION THAT OPERA6.0 HAD A +30 BUG WHEN RENDERING CSS SHEETS?? Who is sabotaging who here?!?
Re:Clearly This Sucks but.... (Score:5, Informative)
Opera6 shows the page that MSIE6 receives just fine. I even included a screenshot of it on my page [opera.com] -- scroll down to the second image.
If you still believe this is Opera6's fault, please provide a test case showing how it fails.
Re:Clearly This Sucks but.... (Score:3, Informative)
Yes, it can.
But why should it? It just encouranges the stupidity of most 'web designers' who look at logs and say 'Oh, 98% of visitors use MSIE5/6, no need to write correct code, just kludge some MS-only code together'. Lather, rinse, repeat.
User-Agent string fascism and spoofing is a classic chicken and egg situation. Except the chicken in this case is an MCSE armed with MS Frontpage.
Re:Realplayer (Score:3, Insightful)
I see why.... (Score:3, Insightful)
Kjella
Re:Maybe, but... (Score:3, Informative)
Re:Microsoft destroys Netscape, Opera must be next (Score:3, Informative)
People have to stop thinking that the PC is all there is on the net...
Re:Not necessarily saying this story isn't true, b (Score:3, Informative)
Re:Bad autodetection (Score:4, Informative)
The fact that it only sends the broken sheets to Opera 7 would indicate that someone at MSN wants to hurt the reputation of Opera's latest offering.
2) No. Nobody should have to browse with a false user-agent string. Period. The fact is, as much as we like standards, every browser has its own quirks and problems that must be worked around if you want to give all browsers the same experience.
A good webmaster can use the agent string to greatly improve the browsing experience for everyone. But bad ones use the information to mess with users of specific browsers[*], or to deny them access altogether, even though the vast majority of websites I've entered under false pretenses worked just fine.
The whole issue is about respect. Microsoft is not respecting my decision to use a non-IE browser. Coding to standards and ensuring cross-browser correctness shows respect to everyone who views your site. Locking out users of browsers you don't like shows disrespect for those who don't share your browser preferences.
[*] Not always to IE users' benefit. I remember one slashdotter who rigged his site so that anyone using IE ended up listening to the musical stylings of William Shatner.
Re:Bad autodetection (Score:5, Informative)
If you read the discussion and set your filter below "+5 for loudly bashing MS", you would notice that Opera6.0 had a problem that was FIXED BY -30 OFFSET. So what you're looking at is the inability to distinguish between opera6.0 and opera7.0. Or, essentially bashing for the (somewhat screwd up) fix of opera6.0.
What truly amazes me is that opera.com description of the problem fails to mention that. I have to say that MSN guys come out looking *far better* than the Opera.