Slashdot Mirror


10 Percent of UK Sites Incompatible with Firefox

Bimo_Dude writes "The BBC News is reporting that ten percent of UK websites alienate Firefox users. From the article: 'While most people still use Microsoft's browser, Firefox is slowly making inroads. Its share of the browser market grew to 8% in May, up from 5.59% at the beginning of the year, according to US-based analysts NetApplications. Microsoft IE's share of the market dropped to 87.23% in May, compared to 90.31% in January.'"

340 comments

  1. standards compliance by PurPaBOO · · Score: 2, Insightful

    MS is nolonger the standard. Woohoo

    --
    If it weren't for the rocks in its bed, the stream would have no songs.
    1. Re:standards compliance by PurPaBOO · · Score: 1

      I only mention this as I previously had a boss who insisted that because Microsoft had 85%+ browser share, he insisted that it was the standard that we design to. I insisted that we design to w3.org standards. There were tears.

      --
      If it weren't for the rocks in its bed, the stream would have no songs.
    2. Re:standards compliance by CaymanIslandCarpedie · · Score: 1

      OK, but that stats quoted in the summary say they still have 87.23%. 87 > 85. IE is still the standard for your previous boss.

      --
      "reality has a well-known liberal bias" - Steven Colbert
    3. Re:standards compliance by Anonymous Coward · · Score: 0

      and then you both hugged, and made love in your Firefox t-shirts

    4. Re:standards compliance by bedroll · · Score: 1

      Ha! I've had similar conversations with my current boss.

      Seems that all Microsofties share that sort of thinking. Thing is, I've yet to find anywhere where Microsoft incourages this bit of thinking. This leads me to speculate how they achieve such ubiquity in their advocates... Subliminal messages in the MCP training, perhaps?

    5. Re:standards compliance by PurPaBOO · · Score: 1

      Normally the pointy head is a giveaway! :-)

      --
      If it weren't for the rocks in its bed, the stream would have no songs.
    6. Re:standards compliance by dusik · · Score: 2, Interesting

      Yeah... I've been trying to figure out the Microsofties at my work, and I keep hearing the argument over and over: "I use logic. If everybody uses it, it must be good." And then there's the big word: "compatibility". They feel like if they stray from the Microsoft way of life in any way, they'll have trouble communicating with others in the field.

      It's sad, but I totally stumped a professional programmer at work when I said something about running a binary. How can you run a binary file? Maybe they're right... I've got communication problems now ;)

    7. Re:standards compliance by Eric+Giguere · · Score: 2, Insightful

      Time to dust off this page:

      How to Detect Internet Explorer

      But only encourage switching to a different browser, don't harangue them into doing it. Remember that some companies/organizations still require the use of IE, especially to access internal systems. If your surfers are coming from such a place, getting mad at them won't help either of you.

      Eric
      Recently interviewed in The Waterloo Chronicle! (OK, so it isn't The Globe and Mail)
    8. Re:standards compliance by Metatron · · Score: 1

      I've never been able to work out this logic either. Imagine a conversation with a department store manager saying that as long as 85% of people could get though his front door, then he was happy. What business is happy to ignore 15% of its potential customer base.

      Yes Mr Shareholder, we could have earn't 15% more money this last financial year, but we were happy with what we got, so thats okay ... isn't it ?

    9. Re:standards compliance by bedroll · · Score: 1

      [devilsadvocate]But if it costs 20% more to get 15% more business then why do it?[/devilsadvocate]

      The cheapness of VB development has many people convinced that developing for Microsoft products is always the quickest and cheapest.

    10. Re:standards compliance by Metatron · · Score: 1

      VB development maybe, but does it cost that more to generate standards compliant HTML ?

    11. Re:standards compliance by chrish · · Score: 1

      That requires JSP... have you got a version that'll do it just with JavaScript?

      --
      - chrish
    12. Re:standards compliance by Eric+Giguere · · Score: 1

      A very similar approach can be found here: JavaScript Browser Detection. If you're running JavaScript, though, you can detect the browser more accurately using other techniques that don't rely on the user-agent header. The code gets pretty complicated, though.

      If all you're interested in is a way to detect IE then you'll probably be interested in IE's Conditional Comments, which is really a horrible hack but it works...

      The problem with doing things in JavaScript, of course, is that it's a client-side technique and it doesn't work if the browser's disabled JavaScript support.

      Eric
      Read Make Easy Money with Google, a book for non-techies (not you guys!)
    13. Re:standards compliance by masklinn · · Score: 3, Insightful
      That thing is fricking stupid, UA sniffing is sheer bullshit 99% of the time (part of which is cause modern browsers can camouflage themselves with 2 clicks, or you can create custom UAs, or block UA alltogether).

      How about using sensible detections for a change?
      For example, MS provided us the wonderful thing called Conditional Comments.
      <!--[if lt IE 7]>
      your code
      <![endif]>
      Your code will only be read by MSIE browsers under version 7 (aka up to and including IE6), presenting them with unique content without tracking tricky or dumb things.

      Same thing in Javascript, don't use User Agent sniffing, use Object sniffing for exemple. Aka if your script uses document.createElement, precede the script with
      if(!document.createElement)
      return;
      Which will only try to feed the script to browsers which can actually handle it (those who have implemented document.createElement)

      Then, if you're a really good and tricky web designer, you can do it Malarkey Style, presenting both different presentation and suggestion to switch to a better browser to crappy browsers users... using CSS advanced functions (one design uses CSS1, the other one uses CSS2, CSS2 non compliant browsers will only get v1 black&white, and as soon as a CSS2 compliant MSIE is born it should be allowed to see v2 design). Try it out with MSIE, then with any CSS2 (somewhat) compliant browser (Firefox, Opera, Safari, Konqueror, ...)
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    14. Re:standards compliance by bedroll · · Score: 1

      VB development is what convinced them that designing for Microsoft is cheaper, just because there's so much cheap VB development labor. My point was that once they're on that line of thinking they don't seem to come off of it when it comes to things like DHTML and CSS. Try convincing a Microsoftie management type that by making simple adjustments in how a group of web developers do coding you could comply with standards while not driving up costs, driving up production time, or reducing percieved quality of the finished product. A true Microsoftie will brush aside your suggestion with a "Why bother, who uses that other crap anyway?" They seem to get offended if you even suggest complying instead of catering to Microsoft. The thinking is along the lines that any change will cost money.

    15. Re:standards compliance by chris_mahan · · Score: 1

      Yes, because good xhtml+css is harder (meaning pay more for the experienced devs) than dreamweavering a photoshopped layout.

      Of course, that's short term. really well designed web sites cost a lot less long term. So you spend more up front, and you spend less overall long-term.

      On the "85% so it must be good" argument: The #1 selling car in the world is the Ford Escort.

      --

      "Piter, too, is dead."

    16. Re:standards compliance by Eric+Giguere · · Score: 1

      For example, MS provided us the wonderful thing called Conditional Comments

      I'm not sure I'd describe it as "wonderful", but it is certainly an option. Really, I wrote "How to Detect Internet Explorer" as a companion piece for my HTTP header viewer to show some of the things you can (very easily) do with the header information. As with most things in computing, there are various ways to accomplish the same basic goal.

      Eric
      The three types of click fraud
    17. Re:standards compliance by emandres · · Score: 1

      That's pointy hair... not pointy head. Unless of course your boss is a conehead.

      --
      The only way to tell the difference between a hamster and a gerbil is that the hamster has more white meat.
    18. Re:standards compliance by emandres · · Score: 1

      Cheap, as compared to what? Developing in Malbolge? In my experience VBScripting, at least in ASP pages, is a waste of time because the error messages are so insanely vague (Something to the tune of "ERROR, WILL ROBINSON! ERROR!")

      --
      The only way to tell the difference between a hamster and a gerbil is that the hamster has more white meat.
    19. Re:standards compliance by bedroll · · Score: 1

      Cheap as in labor. VB programmers are cheaper labor, and many are poorly trained. Microsofties are notorious for spending far more on software than on labor. They think they'll save by paying Microsoft more than they do their employees. So, if you have to pay a VBScripter $30k a year to write ASP and you have to pay a PHPer $50k a year to write PHP then hypothetically you're saving if the VBScripter is only two thirds as productive.

      Keep in mind that I, personally, don't believe any of this stuff. I've had it extolled at me before, though.

    20. Re:standards compliance by chrisnewbie · · Score: 1

      well 8% of the browser market is not a wind of change....when they get to 50% then i guess you can say MS is no longer a standard.

      But right now, it's not supported on some web based software. I have experienced lots of time out,even dns errors on pages compare to IE. I still use Mozilla 99% of the time but cant say i'll get rid of IE for some time.
      At least not unitl it's fully intergrated and supported everywhere.

    21. Re:standards compliance by poningru · · Score: 1

      ha A friend has created this:
      http://xanoo.com/ct/securityspoof
      please take the script as much as you want.

      --
      Calm down people, its a religion not an operating system.
    22. Re:standards compliance by r_jensen11 · · Score: 0

      Yes Mr Shareholder, we could have earn't 15% more money this last financial year, but we were happy with what we got, so thats okay ... isn't it ?
      Sorry mate, but if you're saying that you only have 85% of your customer base, then saying "gshould've ernt 15% more" is still alienating the 2.25%. .85*1.15=0.9775, meaning you have 2.25% missing somewhere.... So really, you shoulve said:
      Yes Mr Shareholder, we could have earn't approximately 17.6470588% more money this last financial year, but we were happy with what we got, so thats okay ... isn't it ?

    23. Re:standards compliance by dusik · · Score: 1

      You might have a point about VB development, but I find it truly hard to understand a similar justification of Visual C++ with MFC development of complex visual application.

      At work, we have a small team of dedicated MS programmers (mostly VB, but some C++). I was showing one of them how to operate the new installment of Visual Studio a couple weeks ago. He was very, very confused with all the GUI changes. My point is that aside from the horribly painstaking process of developing a visual application with MFC (compare to, e.g., Delphi), the changes Microsoft makes with every installment of their development environment only add to the inefficiency of the task.

      That reminds me of the old Soviet joke: "Q: Why don't we have any meat in the Soviet Union? A: Because we're taking 7-mile leaps toward communism and the cattle can't keep up!"

  2. My site isn't! by Shinaku · · Score: 2, Funny

    I'm from the UK and my site, www.xearix.com (the XearixNET IRC network) isn't. I remeber my old schools website only worked in IE, was a real hassle working around all the glitches to get my work downloaded - quite often I just thought screw it, if they can't be arsed to design a website which is actully complys with standerds, I can't be arsed to do my homework.

    --
    -- :>
    1. Re:My site isn't! by Anonymous Coward · · Score: 0

      You lost 10% audience of techno-savvy users, then. If you're a commercial site, it can make a difference...

    2. Re:My site isn't! by yotto · · Score: 1

      Your site isn't compliant with standards, or your site isn't one of the ones that is incompatible with Firefox? /using lynx, can't check in firefox if I wanted to.

    3. Re:My site isn't! by callqcmd · · Score: 0

      Your site isn't compliant with standards, or your site isn't one of the ones that is incompatible with Firefox? /using lynx, can't check in firefox if I wanted to.

      Thats irrelevant now.. because his site is just ISN'T.
      Poor baby, wanted some traffic to his site, instead ended up smelling burnt cables due to the slashdot effect.

    4. Re:My site isn't! by ThaReetLad · · Score: 1

      Actually, amongst techno-savvy users the proportion of firefox users in MUCH higher. Some tech sites have over 50% firefox users. If you're a tech site you'd better be standards complient, conversely, if you run a IT management site and you want to keep the PHB's in and the geeks out, run LOTS of IE specific code.

      --
      You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
  3. In other news... by mrighi · · Score: 5, Funny

    ...10 percent of UK web sites are hosted at the domain http://www.msn.co.uk./

    1. Re:In other news... by drspliff · · Score: 2, Insightful

      Eh?
      Microsoft have recently re-done their entire MSN site in most countries to take advantage of pure xhtml and css.. with one of the main incentives being that sure people may run other browsers, but they want to use MSN.

      What would happen if Microsoft stopped Hotmail from displaying properly in any other browser, there would be some very big critics giving them an ego bashing...

      What the article was actually refering to was the suprising number of business sites owned by reputable companies that hire complete arsehats for web designers/developers.

      I've seen it on many occasions, and even though Opera can identify as Internet Explorer, this damn website seemed to be specificly checking for 'Opera' in the useragent string..

      So, 20 minutes later I'd 'fixed' opera and made the useragent string almost identical to a real IE client, and sure enough the website worked perfectly...

      I did phone up their technical support number just to log a problem (it would have been stopping me from getting an insurance quote...) and the woman on the phone just didn't seem to understand and refused to pass it onto the 'technical people'.

      I know it's kinda lame, but if you come across this sort of thing happening with a large company.. take time to phone or atleast e-mail, if enough people are made aware of this we'll all be generally better off.

    2. Re:In other news... by Anonymous Coward · · Score: 1, Insightful

      A while back I was looking at bank/building society websites. My own bank wouldn't let me use anything other than IE on Windows for online banking, as they used ActiveX for security features (yes, they really did say that!) They've cleaned up their act since then, but as an example of the nonsense you find on MSIE only sites, it takes some beating.

      Meanwhile another bank had a website obviously tested on every browser they could find, and none of that "let's be cool and have all the links as javascript" that makes sites inaccessible to visually impaired customers with text browsers. I sent them an email commenting on this, and actually got a reply from the developers, pleased that someone had noticed their efforts to make the site compatible and accessible.

      So don't just complain: when you see that the developers have made the effort let them know that someone appreciates it.

    3. Re:In other news... by masklinn · · Score: 1
      What would happen if Microsoft stopped Hotmail from displaying properly in any other browser, there would be some very big critics giving them an ego bashing...
      Fucking up most Hotmail links by pointing 95% of them to Javascript scripts instead of regular links looks like a first step to me.

      In fact, it was such a retarded move that some people went through the trouble of creating an extension to reverse this change back
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    4. Re:In other news... by drspliff · · Score: 1

      I guess you're right about the Hotmail links, but I was implying 'the big 3' instead of 'any other browser'.. That is 'Mozilla, Opera and Safari/Konqueror'.. Lets face it - if you're browsing the web using Links/Lynx, you're probably not going to be using Hotmail - so it's a non-issue.

    5. Re:In other news... by 6031769 · · Score: 1
      Microsoft have recently re-done their entire MSN site in most countries to take advantage of pure xhtml and css..

      Not very well though: Validate MSN.

      --
      Burns: We're building a casino!
      McAllister: Arrr. Give me 5 minutes.
    6. Re:In other news... by masklinn · · Score: 1

      You know some people out there surf with javascript disabled?

      And the recent NoScript extension helps, too...

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
  4. Standard by myukew · · Score: 3, Funny

    Why don't webdesigners simply use standard compliant ways to make their websites?

    1. Re:Standard by Anonymous Coward · · Score: 0

      Have you been living under a rock for the past few years?

    2. Re:Standard by CaymanIslandCarpedie · · Score: 1

      The biggest problem with that is, the goal of webdesigners is to basically make an attractive site (to the highest percentage of viewers as practical). There is no browser which is 100% standards compliant, so going with the official standards isn't that practical since there are no browsers which fully support the standards. The practical solution (like it or not) is build for the defacto standard (the browser with 90% market share).

      --
      "reality has a well-known liberal bias" - Steven Colbert
    3. Re:Standard by zkn · · Score: 1

      To most "webdesigners" It simply isn't a question of compatibility. If you make you page in frontpage continualy checking it in IE it doesn't matter to you whether tags are closed or if stuff lines up corectly in firefox.

      That seems to be changing as more and more of the slightly "tech savy" start using firefox.

    4. Re:Standard by DMNT · · Score: 2, Insightful
      Why don't webdesigners simply use standard compliant ways to make their websites?

      Because, it's far more easier to write web pages for one OS, one browser and one version. Especially, if you have bells and whistles to put to the site. Dominance of IE has lead to a situation where WWW means Windows Wide Web: Even when web designers want to write standard html they are forced to check it against IE bugs. Usually this leads to poor structure, like using tables for layout. See why using tables for layout is stupid.

      For example about problems html writers encounter, I dare you to find out how to write W3 standards compliant pages that work with IE and Mozilla and have a flash plugin without googling. It's not as easy as one could think.

      Finally, testing is also easier when you have only one browser -- platform specific bugs are doubled with two browsers.

      --
      ?SYNTAX ERROR
    5. Re:Standard by GigsVT · · Score: 1, Informative

      That's bullshit. I design all pages using firefox, then validate them. They always look fine in IE and all the other browsers.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    6. Re:Standard by ErroneousBee · · Score: 4, Insightful

      No, you are selling the website to the client, not thier customers. If the client is thinking in terms of pretty pictures instead of useability and robust technology, then you give them pretty pictures.

      There are still plenty of retailers that havent got a clue about the market or the technology. boo.com was the classic example, but theres plenty of retailers that are happy to give every 10th customer a sharp poke in the eye. These retailers will always be at a disadvantage and will dissappear over time.

      The last one I saw was Abel and Cole selling Organic Food. Last year they were on the Google first page for 'Organic Food UK' but now thier competitors are stealing thier market. Searching for 'Able and Cole' leads to the competition, thier website lists products by code rather than product name, they used to be unusable with Mozilla. I expect they will dissappear in a few years.

      Other sites I find hard to use are:
      Ebay/Paypal. It took me a week to get set up to sell something. Google or Amazon will overtake them because they understand 'easy to use'.
      Dabs.com Havent used them for a year, but it was so hard to find technical info that I had to go to other retailers to find out about the product.
      WarehouseExpress. Horrible site, only made useable by the price, range and because they arnt as bad as Jessops.
      Jessops. Already seen a dive in shareprice. Expect them to be dead by next year.

      --
      **TODO** Steal someone elses sig.
    7. Re:Standard by CaymanIslandCarpedie · · Score: 1

      That's bullshit. I design all pages using firefox, then validate them. They always look fine in IE and all the other browsers.

      Sorry, but how is my statement bullshit? If you took from my previous statement that I was saying everyone designs for IE, then sorry I wasn't trying to say that. I was just trying to reply to the GP who was asking why developers don't always use the standards. What part of my inital post do you find to be bullshit? Perhaps I'm overlooking something and part of it is bullshit (don't know what part it could be though). However, basically saying "Bullshit, I design for FireFox" isn't helping me see the flaw in my post.

      --
      "reality has a well-known liberal bias" - Steven Colbert
    8. Re:Standard by Anonymous Coward · · Score: 0

      Again. Why is it web designers fault? Why do they have to spend hours and hours making sure a web site works in four or more web browsers just because no one really can follow the W3 standards?

      If a web designer creates his/her site to follow the standards, then it should work in all browsers. PERIOD!

    9. Re:Standard by steveyT · · Score: 1

      I work for a leading web design company in the UK and that's not the attitude we have. I'm probably preaching to the converted but: On top of limiting your audience, including Mac users which most designers I know use, you are also helping to alienate people that using screen readers etc. as they find it a lot easier to understand clean markup.

      On top of that by writing standards compliant code you make it easier for search engines to understand your site. There are plenty of reasons to create a standards compliant site.

    10. Re:Standard by Just+Some+Guy · · Score: 1
      No, you are selling the website to the client, not thier customers. If the client is thinking in terms of pretty pictures instead of useability and robust technology, then you give them pretty pictures.

      Not if you want to keep them, you don't. If someone goes to a doctor, they expect to be given a treatment plan to follow. They go to a lawyer or accountant because they don't know those fields forward and backward. They go to you because they don't understand the web. If you give them what they want instead of what they need, then they'll drive you crazy asking why they're not getting as many visitors as they thought they should. Do you want to be the one to tell them that it's because the work you did for them is inferior, even if only because you did what they asked?

      If you're just starting out, it can be tempting or necessary to take on bad clients. However, you can and should prioritize your clients based on their willingness to let you do the job that you specialize in once you can afford to do so.

      I've told would-be customers to take their business elsewhere - that my reputation was more important than their money. Lord knows I'm not Bill Gates, so if I can do it, you probably can, too.

      --
      Dewey, what part of this looks like authorities should be involved?
    11. Re:Standard by RoLi · · Score: 1
      Usually this leads to poor structure, like using tables for layout. See why using tables for layout is stupid.

      I've already heard it so often, I can't stand it anymore how table layout is sooo bad and CSS-layout is so much better.

      There was a time (stupid me) when I actually believed it and I tried hard, really hard, to implement it, but CSS-layout just doesn't work very well

      At least in my opinion, the biggest advantage of html is that you don't have to care about micromanaging every stupid detail.

      That means, when I make a table with 2 columns, it works in all resolutions, in all font sizes, in all languages (text takes a different amount of space in a different language) and most importantly, it does never overlap.

      With CSS, you usually have to deal with pixels and as soon as you want to translate your website into another language your whole website falls apart and/or it's fixed to a specific resolution.

      To see what I mean, just visit CSS zen garden. Except for the homepage layout and maybe half a dozen others, all layouts are fixed to 800 pixel width.

      Also you can make almost every layout break down by increasing the font size.

      I like CSS very much, but not for layouting.

      Table-layouting is simple and it works. And most importantly it defaults to a sane state in which the browser tries to display it well.

    12. Re:Standard by AaronLawrence · · Score: 1

      Also, tables have been around a lot longer (since HTML 1?) and older browsers will make a much better attempt at rendering them than they will fancy CSS. I don't really mind if older browsers don't make the page look pretty, but it should be readable and usable and approximate the same ideas.

      --
      For every expert, there is an equal and opposite expert. - Arthur C. Clarke
    13. Re:Standard by masklinn · · Score: 1
      That seems to be changing as more and more of the slightly "tech savy" start using firefox.
      The "tech savvy" are already using Firefox, or Safari, or have been using Mozilla for years.

      What's changing now is that Joe Sixpack is starting to use Firefox too, as well as you mother and Henry's grandparents.
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    14. Re:Standard by masklinn · · Score: 1
      With CSS, you usually have to deal with pixels and as soon as you want to translate your website into another language your whole website falls apart and/or it's fixed to a specific resolution.
      You should switch dealer, your crack is awfully bad quality.

      Working with CSS doesn't mean you have to "deal with pixels", dealing with pixels is a designer's choice (and quite a stupid one if I may add), fixed design is one type, liquid, elastic, flexible are others.

      Pick the one that fits your needs, but don't spout bullshit about CSS being about pixels, it's not.
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    15. Re:Standard by GigsVT · · Score: 1

      The practical solution (like it or not) is build for the defacto standard (the browser with 90% market share).

      This part is the bullshit.

      You said "The practical solution" implying that it is the only valid solution. Then you reinforce this idea by saying "like it or not", which implies any other methods are invalid, and people have no choice.

      Besides that, it's factually incorrect in my experience.

      Back when I used to test in IE first, I always had trouble with rendering in other browsers. Since I started targetting standards compliance and firefox, I very rarely have problems with pages looking vastly different or wrong in other browsers.

      If anything, the more practical solution is to not target IE.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    16. Re:Standard by ssundberg · · Score: 1

      With CSS, you usually have to deal with pixels and as soon as you want to translate your website into another language your whole website falls apart and/or it's fixed to a specific resolution.

      You aren't all that familiar with CSS if you use only pixels for dimensions. Percentages work with CSS just as they do with tables. The big advantage I've found using CSS is that, by using external stylesheets, I'm able to reduce considerably the size of some of my page files, load images (e.g. a logo that appears on every page) in such a way that it speeds up page-load times, and not have to deal with all of the extra, and sometimes messy, code tables requires.

      I'm quite happy using CSS, and there is a very simple CSS workaround to the IE vs. Firefox incompatibility problems.

    17. Re:Standard by RoLi · · Score: 1
      Percentages work with CSS just as they do with tables.

      True, but that wasn't the point.

      The point is that a table is always rendered as a table (which is what I want) while CSS divs are overlapping and don't grow with font sizes. They are fixed (no matter if they are fixed to a number of pixels or a percentage and not flexible.

      I'm quite happy using CSS

      Me too, but I don't and will not (any more) use it for layouting.

  5. Other browsers too then, I guess by Peter+Cooper · · Score: 4, Insightful

    Perhaps what they're really trying to say is that 10% of the sites are IE-specific, as if a site does not work in FireFox, it is unlikely to work in Safari, Opera, and other browsers. It's not a FireFox specific problem.

    1. Re:Other browsers too then, I guess by Anonymous Coward · · Score: 0

      I vote you mod the parent up.

      It may be obvious to the original poster, but the above is what the title line should have said.

    2. Re:Other browsers too then, I guess by archen · · Score: 5, Funny

      Hell, 10% of websites don't work in IE either (or any browser) just because whoever made the page didn't know what in the hell they were doing.

    3. Re:Other browsers too then, I guess by barzok · · Score: 1

      I've seen plenty of sites that tell me "This site requires Netscape, IE or Opera. Please upgrade."

      It's really just terrible bad browser sniffing combined with myopic or just plain cluless web "masters".

    4. Re:Other browsers too then, I guess by xphase · · Score: 1

      That's not necessarily true. At my school we use PeopleSoft(tm) to do everything (including enrolling in classes and getting our grades). One day during registration someone decided to "upgrade" PeopleSoft(tm) and suddenly Firefox started to cause some weird infinite recursion of the javascript code. I opened up the site in Konq and it worked fine. My guess is that since the school officially supports Macs (most of the staff use Macs and all of our e-mail kiosks are eMacs) that Safari (and hence konq) are tested and known to work.

      Anyway, just my 2 cents.

      --
      The following sentence is TRUE. The previous sentence is FALSE.
    5. Re:Other browsers too then, I guess by Builder · · Score: 1

      Not true! My accountant's site doesn't work on Firefox (Linux or Apple) or Safari. It works just fine on opera thought!

    6. Re:Other browsers too then, I guess by H0p313ss · · Score: 1

      whoever made the page didn't know what in the hell they were doing

      :-)

      I'm beginning to think that webauthoring should be licenced so that if you're not knowledgable enough to write W3 compliant xhtml from memory you should have to use a tool that does.

      Similarly, Frontpage is a crime against humanity!

      All kidding aside, how do we educate the unwashed masses? The grand majority of web users out there don't even know what raw HTML looks like, much less nebulous issues like CSS compliance and xhtml. Why should they even care?

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    7. Re:Other browsers too then, I guess by Anonymous Coward · · Score: 0

      Indeed, and it's this sort of thinking that's really starting to annoy me. Over the last year or so, I've been seeing more and more sites that are now designed "for IE and Firefox".

      Why do these people not understand that they're making exactly the same mistake as before. Coding to standards is a far better choice than just making your site work on one, two or more specific browsers.

    8. Re:Other browsers too then, I guess by justforaday · · Score: 1

      The story from yesterday had someone from Opera saying that it identifies itself as IE by default. It's possible that could be part of it...

      --
      I'll turn into a supernova and burn up everything. Well I'll turn into a black little hole and you'll turn into string.
    9. Re:Other browsers too then, I guess by Peter+Cooper · · Score: 1

      Luckily, coding for FireFox is almost the same as coding for standards. I can't immediately think of any commonly-used features that are FireFox specific, and essential to viewing a site (the moz rounded corners don't count as essential ;-))

    10. Re:Other browsers too then, I guess by m50d · · Score: 1
      Take a look on the left hand side of your screen for a good counter-example

      I think what they are trying to say is what they actually say, that 10% of sites do not work with Firefox.

      --
      I am trolling
    11. Re:Other browsers too then, I guess by Anonymous Coward · · Score: 0

      I just looked at your site: http://www.bigbold.com/

      You might want to make the background colour white to match the gradient image for those of us who have different default bg colours...

    12. Re:Other browsers too then, I guess by whitehatlurker · · Score: 1
      Well, the examples used in TFA (Job Centre and Odeon) seem to work fine in Opera (once I figured out that they need the www in front).

      I have in the past experienced problems with sites that didn't work properly (as recently as yesterday) in Opera, but worked fine in IE. The typical problem was poor web site design.

      Make the web a nicer place.

      --
      .. paranoid crackpot leftover from the days of Amiga.
    13. Re:Other browsers too then, I guess by Anonymous Coward · · Score: 0

      the sad part is that it's true

  6. Heh by Ailure · · Score: 2, Funny

    When I see a site that don't work in Firefox, I usually don't bother open up IE for that site.

    Damn, it reminds me when I told about a certain webmaster how his page wasn't working good with other browsers than IE.

    He added a "Designed for IE" claim... -_-

    1. Re:Heh by packetl0ss · · Score: 1

      One time, I was searching for web hosters and saw a site that looked absolutely awful in Firefox with broken up images and overlapping text all over the site's pages. I emailed the web hoster and said their site doesn't look too good in Firefox. They responded that they "didn't know that" and "out of 5000 hits, only 80 or so were of browsers that weren't Internet Explorer, so it isn't worth making the site work in Firefox". I guess they didn't want a sale from someone willing to purchase web hosting service who was browsing their site in Firefox.

    2. Re:Heh by William+Robinson · · Score: 1
      Damn, it reminds me when I told about a certain webmaster how his page wasn't working good with other browsers than IE.

      True. Guess, it is better to point them that 'their web site is non compliance with so and so standards of w3c(or anything else)'. That scares shit out of them.

      Of coz, (s)he might add "Non compliant to w3c" tag somewhere...:)

    3. Re:Heh by maxwell+demon · · Score: 1

      To which the correct answer would be: I prefer web pages designed for visitors. If it's a commercial web site, replace "visitors" with "customers".

      --
      The Tao of math: The numbers you can count are not the real numbers.
    4. Re:Heh by mrjb · · Score: 2, Interesting

      Reminds me of a banking website that didn't work in Firefox due to non-standard Javascript. I sent them a fix, they put it online a few weeks later. From then on I could use their site for online banking.

      --
      Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
    5. Re:Heh by Ailure · · Score: 1

      Yeah, but he was also my teacher. In Web design too. Plain irony.

      Thought I did tell him about W3C compliance but he didn't care about it apparently. Oh well, the site works in the latest version of Firefox anyway but it's still not W3C compliance.

  7. Surprised it's not higher by kalpol · · Score: 1

    Most casual web site designers use whatever design tool they can get their hands on, and that's usually Frontpage sinec it's bundled with Office (I think).

    --
    12:50 - press return.
    1. Re:Surprised it's not higher by NetNifty · · Score: 1

      True, however the sites the article mentioned are companies or government sites, not just random "here are my kittens" personal sites where that's to be expected.

    2. Re:Surprised it's not higher by quantum+bit · · Score: 1

      But despite being awful tag-soup, pages created by Frontpage usually render correctly in Firefox. Most people deisning pages in it don't know enough about HTML/JavaScript to create anything that's incompatible.

    3. Re:Surprised it's not higher by Anonymous Coward · · Score: 0

      Sweet .signature!

  8. Re:Text by Hieronymus+Howard · · Score: 0, Offtopic

    This is on the BBC website, which can withstand any amount of slashdotting. There's no need to post an unformatted copy of the article here.

  9. Stats by Penguinoflight · · Score: 2, Interesting

    No matter how accurate these statistics are, there will be plenty of people arguing about them. What makes this study any more accurate than others?

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
    1. Re:Stats by 0x461FAB0BD7D2 · · Score: 3, Funny

      What makes this study any more accurate than others?

      This study is one of the 3.75% of all studies of which the statistics are not pulled from a derriere.

    2. Re:Stats by Anonymous Coward · · Score: 0

      Actually if you read the story, it seems they only examinied 100 'leading' sites, 10 of which had problems.

      Having tried a couple of the "problem" sites myself, it seems this data is outdated - e.g. www.companieshouse.gov.uk was listed as being incompatible, but this site now displays the w3c compliance logos on their page.

      Yet another non-story being hyped on /.
      What a shame.

    3. Re:Stats by Anonymous Coward · · Score: 0

      Given the margins of error in any of these "market share" studies, it is a little strange that the reported percentages are given to .01% precision.

      When no margins of error are posted, I would assume the margins are large (e.g. 5%)...

  10. Well... by ImaLamer · · Score: 2, Insightful

    Ten percent isn't bad. At one point, for about ten seconds in Internet time, you couldn't do *anything* on the web without IE and some ActiveX control.

    I'm happy that I can switch clueless users to Firefox now because sites like Yahoo! know to play nice. No longer do I get calls late at night asking why Euchre doesn't work.

    1. Re:Well... by a_peckover · · Score: 1

      Who modded this funny ? Take that back or Sir Tim Berners-Lee will take the web back! :-)

    2. Re:Well... by bogaboga · · Score: 1

      Are you saying that Yahoo now fully supports Firefox and that its music/video service (launchcast?) works without a hitch? I cannot check it out now, as our internet activities are always monitored. I'm posting this from an HP SuSE Linux server with Lynx!

    3. Re:Well... by ImaLamer · · Score: 0

      ahh, you got me there you slick bastard

    4. Re:Well... by Inda · · Score: 1

      Only today the vacuum cleaner broke so I thought I'd look at http://www.electrolux.co.uk/ for some phone numbers. I wouldn't have minded a blank page but crashing Firefox with half a dozen tabs open was not funny.

      Speaking of clueless users too; I had an amusing experience with my clueless user mate the other day. It started with an instant message...

      Clueless mate: the racing post keeps crashing ie
      Clueless mate: something about java

      Me: I used to get that too. Use Firefox. www.getfirefox.com

      10 minutes later:

      Clueless mate: shit hot it works a treat
      Clueless mate: firefox is alright

      A week later I go round his house. In his taskbar I see Firefox with the Racing Post title displayed. Good I thought. Next to that was 10 or so instances of IE grouped together...

      He only uses Firefox for the Racing Post. I tried.

      --
      This post contains benzene, nitrosamines, formaldehyde and hydrogen cyanide.
  11. More details by k4_pacific · · Score: 3, Funny

    It turns out that on these 10%, they render just fine. It's just that the content is an insult to the intelligence of the average Firefox user.

    --
    Unknown host pong.
    1. Re:More details by pure_equanimity · · Score: 1
      Another one that does this is the O2 website. It's quite funny but annoying that it tells you that your brank spanking new version of Firefox is out of date. For whatever reason Konqueror (eurgh!) works fine.

      Even funnier and more lame is their explanation of why they won't let you see the site in Firefox

    2. Re:More details by Anonymous Coward · · Score: 0

      Err... It works justs fine with Firefox...

    3. Re:More details by pure_equanimity · · Score: 1

      It doesn't work with mine and never has.

      Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

    4. Re:More details by Anonymous Coward · · Score: 0
      It turns out that on these 10%, they render just fine. It's just that the content is an insult to the intelligence of the average Firefox user.

      Wow. I didn't know the republicans had that many websites up.

  12. Re:In Other News by pandrijeczko · · Score: 1
    ...even though there's probably more Windows users than Linux users, by overall number, running Firefox as a browser.

    Idiot.

    --
    Gentoo Linux - another day, another USE flag.
  13. It's just business by Anonymous+Brave+Guy · · Score: 2, Insightful

    It's a commercial decision. Making your site work completely with IE gets you around 90% of the market. Making your site work completely with W3C standards gets you around 10% of the market. Making your site work completely with both costs you more money. If the extra money is more than the 10% of the market is worth, you're going to go with the 90%-only option.

    It sucks, but businesses don't run to make Firefox users happy, they run to make a profit. When the cost of losing the smaller market share (and the resulting negative PR etc.) outweighs the cost of making a site that works completely with both types of browser, businesses will support both types of browser.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:It's just business by emmetropia · · Score: 2, Insightful

      It doesn't cost extra money, if you have coders that at least half knowledgable on the subject. I think people stay away from it because people *say* it costs more money. Writing something from scratch, it shouldn't take any more time to work across browsers. I'll admit that porting an existing web-layout/javascript to work in multiple browsers can be time consuming, and a pain in the ass. But ground up shouldn't cost you anything extra.

    2. Re:It's just business by bedroll · · Score: 1

      Even at that, it doesn't require too much time/effort to attempt to make your website compatible with other browsers. Even before other browsers had 10%+ of the market I was testing my Internet-facing sites to make sure they were at the very least viewable in the other browsers. Then if I happened to use a few IE-only features I'd just make sure they were add-ons to the design. Thus, my IE-using clientele and majority of visitors got a rich experience, but user of alternative browers still got the content. If you build your development process around such thinking then you spend 5% of your time to not alienate 10% of the market.

    3. Re:It's just business by Anonymous Coward · · Score: 0

      Ask any business what would happen if they lost 10% of their sales...

    4. Re:It's just business by BobVila · · Score: 0

      So basically, Mozilla Firefox still needs more market share.

    5. Re:It's just business by rpjs · · Score: 4, Insightful

      Except that if you code to W3C standards it will work in IE and Firefox and a whole lot more besides, so how does it cost more money?

      On the site I work on, a major UK mobileco, we code to XHTML 1.0 now and browser compatiblity is usually a non-issue - in fact I find it easier to code using Firefox (with the utterly wonderful Web Developer extension) and then cross-check in IE.

      We used to have far more headaches back when we had to provide backwards-compatibility with NS4.0, but now that the numbers of such users have dropped to single-digit numbers per month, we're XHTML all the way.

    6. Re:It's just business by LocoMan · · Score: 1

      There's also the thing that it might not even be 10% of the market. I'd like to know which % of the people that use firefox use it in windows, so they have internet explorer installed.

      I'd guess that most of the people using firefox in windows, when they find a website that they want to go to and doesn't work, will just load IE and open it (I know I do at least, with the open in IE extension). If course there are quite a few geeks that will refuse to open a site that doesn't support their choice of browser (be it firefox, opera, lynx or anthing else), but I doubt they are a majority (I might be wrong, though).

    7. Re:It's just business by EraserMouseMan · · Score: 1

      businesses don't run to make Firefox users happy, they run to make a profit

      Wow! Finally a post from someone who understands what's going on in the real world!

      Here's another concept. Instead of 10% of the world's web developers rewriting their websites, why doesn't Firefox just spend it's time and money to develop support for the extra non-standard features that IE already supports??

      Think about it:
      Firefox hires 10 new developers
      VS
      Rewrite 300,000 websites

      Which do you think would be a better solution given the situation the world is CURRENTLY in?

    8. Re:It's just business by Rogue+Pat · · Score: 1
      Except that if you code to W3C standards it will work in IE and Firefox and a whole lot more besides, so how does it cost more money?
      Unfortunately that's not true. Because the browsers themselves render pages differently, even if the pages are W3C/ECMA etc. standards-compliant.

      Just compare a W3C compliant page in IE 5, IE5 for Mac, IE 5.5 and IE6. I don't have the link handy, but i think David Hyatt had a nice write-up of IE's rendering, with elements jumping around.

      So to make things work as intended in eg. IE you sometimes have to DEVIATE from standards.

      Another example, my site renders completely different in Firefox if i change the document header, that is, triggering going from Strict to Quirks mode in Gecko. The page is still W3C compliant but the rendering is COMPLETELY different.

      With current browsers as they are, W3C adherence is not a recipe for cross-browser compatibility.
    9. Re:It's just business by bunratty · · Score: 1
      Because the browsers themselves render pages differently, even if the pages are W3C/ECMA etc. standards-compliant.
      Web standards don't dictate the exact rendering of a page. If you're trying to make the page look exactly the same in every browser, yes, it's going to be more work for every new browser you try to support. But if you accept that you don't have pixel-for-pixel control and let the browser lay out the page the way it wants, you don't need to write different code for different browsers in general. Sometimes you do have to write different code for IE because it supports so few standards and has so many layout bugs.
      --
      What a fool believes, he sees, no wise man has the power to reason away.
    10. Re:It's just business by bunratty · · Score: 1

      Great idea! Now all you need to do is give the Mozilla Foundation the several million dollars needed to hire 10 new developers for the years it would take to do this.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    11. Re:It's just business by fr0dicus · · Score: 2, Insightful

      So coders that know more about the subject don't cost extra money?

    12. Re:It's just business by EraserMouseMan · · Score: 1

      Last time I checked, software developers were not getting paid a million dollars a year.

    13. Re:It's just business by Anonymous+Brave+Guy · · Score: 1
      It doesn't cost extra money, if you have coders that at least half knowledgable on the subject. [...] Writing something from scratch, it shouldn't take any more time to work across browsers.

      Yes, it really does, and yes, it really will.

      For a start, there are numerous standards bugs in all browsers, IE more than many. You have to include numerous hacks in things like CSS to get consistent rendering across the range of browser software in use.

      Then there are issues with tools. IE lets you use ActiveX controls, for example, which Firefox clearly doesn't. Regardless of the merits of ActiveX, if you have a tool that will do the job quickly and easily in IE, and you don't have it in other browsers, it takes time and money to produce an equivalent.

      Next up, there's testing effort. If you're going to support users of different browsers, you need to check all your styles, scripts, etc. work everywhere. That means configuring machines with all supported browser software (or at least a representative sample if you're cutting corners), and investing the time to check everything out, with various combinations of supported browser options for text size, cookies, scriptings, etc. etc. This can require a vast amount of time to do properly on large site.

      You should speak to coders who are fully knowledgeable about their subject; half-knowledgeable ones tend to think this stuff comes for free. ;-)

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    14. Re:It's just business by Hal_Porter · · Score: 1

      A few years back, I worked on a website for buying stuff online. Nothing fancy - just some Javascript on the client and ASP/ActiveX on the server. It was all a frantic rush to get stuff working. I mentioned to my boss that we should spend a couple of days to get it working in Netscape, and older IE - some of the pages were broken. This is back when Javascript was completely different on Netscape and IE in things like date handling - there weren't standards to code to.

      She vetoed it, on the grounds that people should just install IE 4.0. As it happened, my fix for Netscape was hidden in other fixes - I was scared of people managing to screw up orders by using the wrong browser and then suing us soI fixed it anyway. But the politically correct way to do it would have been to stop them logging in completely.

      But that's the argument - people that are savvy enough to use a non mainstream browser are also savvy enough to switch back to a mainstream one if you tell them to. Also, most of our client companies - this site was not open to the public - wouldn't let people install an alternative browser in the first place.

      And most of these companies will just ignore emails from activist types about how the website is broken on some browser with 90% market share. They know that you're not going to buy anything from them.

      You'd be better off campaigning for your right to drive on the other side of the road quite frankly.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    15. Re:It's just business by Anonymous Coward · · Score: 0

      Years, kiddo. More than one. That's how not-so-trivial it is.

    16. Re:It's just business by 99BottlesOfBeerInMyF · · Score: 1

      Except that if you code to W3C standards it will work in IE and Firefox and a whole lot more besides, so how does it cost more money?

      That is true if you code to five-year-old W3C standards and avoid using certain parts of that standards IE still has not implemented. All browsers, but mostly IE, have bugs and parts of the spec they don't implement properly. Coding to the spec just does not work. You really have to code to the spec and then find workarounds for IE and any bugs in other common browsers.

    17. Re:It's just business by Taladar · · Score: 1

      It depends. I usually refuse to open pages saying that my browser is too old (newest opera version, UA-String Opera) or that this site can only be viewed with IE and I usually hate pages (and don't return) when they have a bloated layout that doesn't render nicely in Opera since IE is not an option in Linux and rebooting for a dumb webdesigner isn't either.

    18. Re:It's just business by bunratty · · Score: 1

      Of source not. Competitive salary + benefits + infrastructure costs about 100K per year. Hiring 10 developers for several years will therefore cost several million dollars. Now cough it up so that great plan of yours can be put into effect. We're waiting!

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    19. Re:It's just business by EraserMouseMan · · Score: 1

      If you want a cheap and easy solution just switch to IE. The "great plan" I proposed is much cheaper than overhauling hundreds of thousands of websites.

      What would your solution be?

      BTW: Making stupid developers code to standards == overhauling hundreds of thousands of websites. That's my point. The Firefox crowd seems to prefer sitting around and complaining about the problem (lack of standards compliance). STOP WHINING AND PROPOSE A SOLUTION! My solution was to update Firefox. M$' solution enabled sloppy HTML to render properly. What's your solution? We're waiting!

    20. Re:It's just business by Dan+Ost · · Score: 1

      Whenever I find a site that doesn't handle my browser correctly, I send a
      polite email telling them so. I include pointers to web resources that will
      help them learn how to support more browsers.

      Very often, I get an email some time later from the developers thanking me
      for my email and telling me that their site will either soon be fixed or
      inviting me to visit their already fixed site.

      Bank sites have been the most responsive. Software vendors whose products are
      windows only seem to be the least responsive.

      --

      *sigh* back to work...
    21. Re:It's just business by masklinn · · Score: 1
      Just compare a W3C compliant page in IE 5, IE5 for Mac, IE 5.5 and IE6. I don't have the link handy, but i think David Hyatt had a nice write-up of IE's rendering, with elements jumping around.
      That was a problem with floats, because MSIE has a lot of problems handling floating elements, in fact it damn fucking sucks at floating anything.

      But you know, you do not HAVE to use floats, and experienced web designers (ones who've already been hit fair and square by IE's bugginess quite a few times) can sense where it'll become buggy, and if they don't they know how to work around the problem or where to find the resources that'll help them
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    22. Re:It's just business by masklinn · · Score: 1
      Here's another concept. Instead of 10% of the world's web developers rewriting their websites, why doesn't Firefox just spend it's time and money to develop support for the extra non-standard features that IE already supports??
      Do you mean the buggy stupid borked sorry excuse for an implementation of the standards that IE features or the magical security tar pit that ActiveX are?

      Non standard features? Most if not all of the sensible ones have already been reimplemented in other browsers (opacity? done; xmlHttpRequest? done), and usually in a much better/more stable/more efficient way.

      Not to mention that all the nice MSIE "features" are awfully undocumented and that it's behaviors are inconsistantto the point that it may be considered a quantic software.
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    23. Re:It's just business by EraserMouseMan · · Score: 1

      Yep. Just more complaining. I didn't see a single solution to today's problem in your post.

      I'll help you out and describe the implied solution that you were getting at.

      MASKLINN's solution: M$ should invent a time machine to go back in time about 10 years and stop it's developers from implementing non-standard, undocumented features.

      We're all still waiting for a better solution to today's problem!

    24. Re:It's just business by bunratty · · Score: 1
      Switching to IE means that tens of millions will have to switch to Windows, and that means buying new computers for all those people. Congratulations. Now your plan costs an order of magnitude more than before. Glad you've got the money to foot the bill, Bill! ;-)

      My solution is for sites to follow the standards. They're the ones with the incentive to get the visitors.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    25. Re:It's just business by masklinn · · Score: 1

      How about teaching web designers and website creators so that they create standards compliant websites?

      Oh wait, that's what happening as of today...

      I guess your problem doesn't exist. It doesn't for me anyway, if a website doesn't work in Firefox or Opera (whichever i'm browsing with at the moment) I'll just drift away from it, to the concurrence for example, effectively lowering the income of the fleed seller and getting closer to driving them out of business

      Darwinian selection at it's best baby

      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
    26. Re:It's just business by julesh · · Score: 1

      But if you accept that you don't have pixel-for-pixel control and let the browser lay out the page the way it wants, you don't need to write different code for different browsers in general.

      True. But the clients never accept this, and if you insist too hard that it's true, they leave and take their business to somebody who will tell them they can. And then when you tell them it doesn't work in firefox, they say they don't care.

      It used to happen all the time to me, when I was in the web design business.

    27. Re:It's just business by Brandybuck · · Score: 1

      Bullshit. If you had nine million customers last year, each paying you one dollar, then you can earn an extra ONE MILLION DOLLARS per year catering to that last 10%. Do the math. It's not going to cost you anywhere close to that margin to write proper HTML.

      --
      Don't blame me, I didn't vote for either of them!
    28. Re:It's just business by Rogue+Pat · · Score: 1

      The David Hyatt story was just an example of course. For instance, IE's lack[ing] CSS1&2 support is well known.

      Point being: the aforementioned in combination with other rendering quirks LIMIT the number of standards that you can apply with cross-browser compatibility.

      See again my comment about different rendering modes in Mozilla http://www.mozilla.org/docs/web-developer/quirks/q uirklist.html tells that you can get wildly different results for instance when it comes to tables by changing the rendering mode in Mozilla by changing the header, all the time remaining W3C compliant. This is up to the point that width/heights are reduced to nearly nothing.

      So W3C compliant coding by itself isn't enough to get browser independent results. Taking all into consideration, as it is now, only a subset of the W3C/ECMA etc. recommendations is truly browser-independent.

    29. Re:It's just business by Brandybuck · · Score: 1

      The web development community could learn from architects. You do NOT tell an architect how to design a building!

      The web development community needs to learn from interior decorators. You NEVER go to an interior decorator with a complete finished specification for your new living room. You give them an idea of what you want, and then they come back with three or four proposals.

      --
      Don't blame me, I didn't vote for either of them!
    30. Re:It's just business by zcat_NZ · · Score: 1

      Yeah, like XHTML that validates; For example I tried to redo my homepage in XML

      It validates, of course, and it worked just fine in every browser I tried. You really HAVE to see it in MSIE.

      --
      455fe10422ca29c4933f95052b792ab2
    31. Re:It's just business by zcat_NZ · · Score: 1

      While you're at it, develop a screen reader that can make sense of all these crap web pages. For a blind user almost half the web is totally unusable due to Javascript/Flash navigation (that has to be clicked on and can't be tabbed to), use of images for navigation without sensible ALT tags, etc.

      I believe Google could make a huge contribution, just run every page in their index through the existing validation tools; +1PR if it validates, +2PR if it passes accessability checking. Google would start returning well designed and accessable pages ahead of MSIE-only crap (which is a bonus all on it's own) and for an extra +3PR one hell of a lot of web designers would start rewriting their pages to validate, overnight.

      --
      455fe10422ca29c4933f95052b792ab2
    32. Re:It's just business by aztracker1 · · Score: 1

      I work hard to make sure that things I do work accrossed browsers, with scripting/dhtml etc, I will generally start with the layout, tweak to make sure it works in ie6/windows (note some bugs are fixed in xp, but not in other versions, find this out the hard way) especially with css-p which is the correct way of using xhtml.

      I test in the big 3 (Firefox/gecko, IE6, and Opera 8) which are 99% compatible with eachother. That 1% inconsistancy usually costs me 4x the time. Even though what I start with may be 100% compliant, they get treated oh so slightly differently in the three. (Opera is actually less likely to render okay, but more likely that scripts will work, than either gecko or ie's rendering engines)

      Now, I don't work cheap, but what I produce works and pretty well, From pre 2000, I worked mainly on ie4+ and nn4+ models, which were so different it wasn't funny... from 2001 to about 2003 I concentrated on quirks mode for the different browsers, and more server-side, less scripting. from late 2003 I've been working more towards xhtml-transitional (to support a few older attributes which helps a bit) and w3c-dom for the most part.

      In concentrating on xhtml-transitional, css, and mostly compliant JS, I still have to tweak a lot so things work right... the fact is even *with* standards it isn't shake and bake easy... The standards were a long time coming, and are only now pretty widely implimented in a usable way. IE has serious bugs when combining certain types of tags (don't mix div-table-div or table-div-table in any way for a lot of content), it just stops rendering, or only does partial rendering, this sucks... at least AJAX methods can replace a lot of more legacy systems, and helps a lot...

      IE7 being geared for XP + Longhorn lines only, will leave a few people behind, I've been getting people converted to Firefox as much as I can, note: when you convert someone to firefox tell them to click the little red circle in the top right when it shows up... may even want to start with 1.0.1 or something older, to *show* them how to update, so they know... Though a more streamlined updater, not full installer, would be much nicer than what's currently there...

      --
      Michael J. Ryan - tracker1.info
    33. Re:It's just business by StrongAxe · · Score: 1

      I guess your problem doesn't exist. It doesn't for me anyway, if a website doesn't work in Firefox or Opera (whichever i'm browsing with at the moment) I'll just drift away from it, to the concurrence for example, effectively lowering the income of the fleed seller and getting closer to driving them out of business

      Darwinian selection at it's best baby


      The (say) 90% of websites that use buggy CSS and ActiveX and IE-friendly will lose 10% of their business from "savvy" Firefox users, while retaining the 90% business from "clueless" IE users.

      Meanwhile, the 10% of websites that are standards-compliant and Firefox- friendly will retain the 10% of Firefox users, while losing the 90% business from the IE users.

      Just which of these two models do you think Darwinism will favour?

  14. Microsoft.co.uk by OctoberSky · · Score: 4, Funny

    What TFA doesn't tell you is that the UK is a tiny little island inhabited by hobbits, leprechauns and the Oasis brothers. A tiny little island where www.microsoft.co.uk makes up 9% of the accessible websites.

    The other 1% is the Beckham/Adams fansite, which we all know is poorly coded.

    1. Re:Microsoft.co.uk by I+confirm+I'm+not+a · · Score: 5, Funny

      the UK is a tiny little island inhabited by hobbits, leprechauns and the Oasis brothers.

      Strictly, the leprechauns come from Ireland. You're maybe thinking of Robin Cook, former Foreign Secretary?

      --
      This is where the serious fun begins.
    2. Re:Microsoft.co.uk by OctoberSky · · Score: 1

      I was thinking what could be better than the Gallagher brothers and Leprechauns in the same sentance.

      Truthgylly though, I'm just glad you were able to read that, I posted it on www.slashdot.org.uk which is NOT FF friendly.

    3. Re:Microsoft.co.uk by pandrijeczko · · Score: 1
      Correcting your errors:

      1. Leprechauns are from the Republic of Ireland which is part of the British Isles not the UK.

      2. Hobbits were captured recently on film in New Zealand but not in the UK.

      3. The Oasis brothers hail from Manchester but all those of us in the UK outside of Manchester do not consider Manchester as part of the UK - it's merely a buffer zone to stop the Liverpudlian Scousers from stealing our cars.

      4. David & Victoria are far too busy whoring themselves to advertising companies trying to sell us Police sun glasses and "Posh crisps" to find the time to go to computer school to learn to code HTML properly so you leave them out of it. I will have nothing bad said against our illustrious "new Royal Family" - at least this new lot don't have big ears like that other bunch of Germanic in-breds.

      --
      Gentoo Linux - another day, another USE flag.
    4. Re:Microsoft.co.uk by Turn-X+Alphonse · · Score: 0

      Take that back! The Beckham's fucked off to Spain. Now we just have giant footed freaks and the Scotish to deal with

      --
      I like muppets.
    5. Re:Microsoft.co.uk by PhilHibbs · · Score: 1
      1. Leprechauns are from the Republic of Ireland which is part of the British Isles not the UK.
      I was aggressively informed that they prefer the term "Northwest European Archipelago" by an Irish friend of mine.
    6. Re:Microsoft.co.uk by Anonymous Coward · · Score: 0
      ... inhabited by hobbits, leprechauns and the Oasis brothers

      By hobbits, gnomes and trolls, yes.
    7. Re:Microsoft.co.uk by Anonymous Coward · · Score: 0

      Yeah, that's really hilarious you stupid stuck-up Southern inbred.

    8. Re:Microsoft.co.uk by HogynCymraeg · · Score: 1

      No he was thinking of Ronnie Corbet.

  15. How do they manage? by Ithika · · Score: 1

    How is it possible for so many sites to be like this? I have designed a fair number of websites but I really don't know how I'd go about making it difficult for Firefox users (not that I'd ever want to). Surely it's easier to just follow the standards? After all, there are whole shelves of books and online tutorials telling people how to follow them; there aren't many books with titles like "Creating Non-Standard Websites" or "How to Create Inaccessible Sites". It seems this 10% of sites must have been trying extra hard to break on non-IE browsers.

    1. Re:How do they manage? by I+confirm+I'm+not+a · · Score: 4, Funny

      How is it possible for so many sites to be like this? I have designed a fair number of websites but I really don't know how I'd go about making it difficult for Firefox users

      (Aside: web standards seems to be replacing SEO as the new web buzzword). We've got a client who runs his own web development house, focusing on standards. His methodolgy is: (1) we develop an accessible, validating site. (2) since he's the boss, and also an *expert*, he tweaks everything in Frontpage. (3) some sarcastic barstard actually validates the site, and discovers it no longer validates. They email our client. (4) our client contacts us to complain that the site "isn't valid HTML and CSS!" Et voila, instant pile of non-validating, Firefox-hating poo.

      It'd be funny if it wasn't so sad.

      --
      This is where the serious fun begins.
    2. Re:How do they manage? by dleewo · · Score: 1

      I know if you use CSS for layout, you could break it for Firefox.

      E.g, I visited a web site this week where the layout was all screwed up in Firefox. divs were overlapping with others when they shouldn't be. When viewed in IE, it looked fine.

      The same is true for the reverse. I was working on a website this weekend and got it working great in Firefox, but when viewed in IE, the layout was all screwed up. I had to then hack it to work in both IE and Firefox.

    3. Re:How do they manage? by Ithika · · Score: 1

      Yeah, but you should be able to turn off the CSS and have a perfectly usable site. After all, it's possible to do things with CSS which make websites unusable for everyone, but that doesn't mean use of CSS is necessarily bad.

    4. Re:How do they manage? by dleewo · · Score: 1

      I wasn't implying the use of CSS was bad....just that it's one way to break a website for some browsers and not others.

      I agree that the website should degrade gracefully if CSS is disabled.

    5. Re:How do they manage? by Secrity · · Score: 1

      One word: "Active-X"

    6. Re:How do they manage? by bedroll · · Score: 1
      It seems this 10% of sites must have been trying extra hard to break on non-IE browsers.

      ...or they could be using ActiveX plugins, VBScript, or WMP.

      Maybe they don't read books and just find the msdn library easier? Wait, who am I kidding?

  16. Books suggest designing for IE only by acomj · · Score: 3, Interesting

    My GF picked up a book on CSS (for dummies). The author suggested that standards didn't matter so much as the market was pretty much all internet explorer, so why bother checking with any other browser.

    I couldn't beleive I was reading this. Its actually repeated in a different section of the book. But then again the book was for dummies.

    For what its worth firefox plugins like webdeveloper make designing/checking web pages (especially css) so much easier, hopefully it will make traction into web development shops.

    1. Re:Books suggest designing for IE only by WankersRevenge · · Score: 1

      I use this Chris Pederick's web extension to assist me with my web development. A few years back I would have happily paid a hundred dollars for this baby. Viva open source.

    2. Re:Books suggest designing for IE only by jrumney · · Score: 3, Insightful

      Perhaps they should rename that book to "CSS (for people who want to look like dummies)"

    3. Re:Books suggest designing for IE only by everphilski · · Score: 1

      CSS for Dummies was published in 2001, according to Amazon.com. That's 4 years ago. Back then IE was king and held a 95%+ market share on Intel boxes. (IE still is king and holds what, 85-90% market share? that's still not bad... not *wise* to design only for IE but in a pinch its not bad) Designing for 95% of your target market isn't bad.

      -everphilski-

    4. Re:Books suggest designing for IE only by tedhiltonhead · · Score: 1

      My GF... Girlfriend... hmm... you're new here, aren't you?

    5. Re:Books suggest designing for IE only by Anonymous Coward · · Score: 0

      Check the slash id.. Old timer..

    6. Re:Books suggest designing for IE only by CoolBru · · Score: 2, Insightful

      Perhaps, but the 2005 edition still says the same thing, so that's no excuse now. The book is missing any mention or concept of semantic markup, and almost every other paragraph is some kind of apology or excuse for IE's lameness. This is a book which fails to mention XHTML other than that it exists and then only reprimands it for case-sensitivity. Learning CSS without semantic markup is just a waste of time, negating most of the things that make CSS so cool, and therefore, I have to opine that this book is a complete waste of trees. Anyone reading it in the hope of learning CSS will be worse off than not reading it at all as it seems to set out to deliberately teach you every bad habit going.

      IE is the albatross around the neck of the web, pulling everyone down to its level. Hard to believe that IE 6 has not had a single feature or bugfix upgrade (plenty of security patches though) for 4 years (Spot the monopoly?). IE is perfectly entitled to have proprietary features, it's just entirely unnecessary for MS to have implemented them in a non-standard way (i.e. outside of CSS extensions, gotta love that ActiveX) so that they break in other browsers. Someone should tell MS to grow up and not pee in the pool (the MS IE7 blogs comments are quite hilarious). As if it wasn't bad enough living with what MS did wrong deliberately, there's all the bugs too.

    7. Re:Books suggest designing for IE only by ryanvm · · Score: 1

      Or CSS From Dummies.

  17. 10% - don't think so by Hieronymus+Howard · · Score: 2, Informative

    I doubt that it's anywhere near as much as 10% of sites that don't work with Firefox. I use Firefox as my main browser on my work PC and my home Linux, Mac and PC. I very rarely find a site these days that doesn't work properly with Firefox, the Odeon and Jobcentreplus sites mentioned in the article being a couple of the most notable exceptions. I'd put the figure at far less than 1%.

    1. Re:10% - don't think so by telbij · · Score: 1

      I doubt that it's anywhere near as much as 10% of sites that don't work with Firefox.

      Being that I use Safari 99% of the time, and only switch to Firefox for compatibility I would have to agree. But perhaps they mean 10% of sites have some isolated feature or layout element that doesn't work in Firefox.

    2. Re:10% - don't think so by taskforce · · Score: 1
      Odeon's site is very strange, I've found it doesn't work with Firefox but does work with Opera 7/8. Normally Opera tends to be the most pedantic about different sites, so I thought it was quite a strange occurance.

      Fortunately Opera is my primary browser, it just means I can't check film times on my Parent's PC, who I have given Firefox and Thunderbird. (The combination is a huge success, I haven't had to format for them since I switched them to the Moz programs 100%)

      For my parents I chose Firefox rather than Opera because I know that Opera isn't for everybody, it's really a very different browser to anything else because of the different layout and features which come as standard.

      --
      My 3D Texturing Skinning work (under construction)
    3. Re:10% - don't think so by julesh · · Score: 1

      The article doesn't say 10% of sites; it's 10% of the top 100 sites. That's a big difference -- the sites that put the most effort into being popular are the ones most likely to push the edge of browser compatibility, because they're trying to cram more and more features into the pages all the time.

      One of my clients recently insisted on switching to a page layout that renders shaded areas using MS's non-standard 'behaviour' CSS tags, because they felt it would help the pages load faster. Faster page loads is more important to them than compatibility, because their market surveys tell them that people prefer to visit sites that load faster.

  18. Government sites listed by La+Gris · · Score: 2, Interesting

    Government sites should leed to show proper behaviour and standard compliance and work hard not to tie users to a specific brand or configuration.

    How does Uk compare to other countries in Europe and around the world on that matter ?

    --
    Léa Gris
    1. Re: Government sites listed by Gyarados · · Score: 1

      Wondering about your question, I found Tagish's Directory of UK Government Offices' Web Sites and was shocked to find that the first four Web sites listed were running Microsoft Internet Information Server.

      While it is possible to use IIS to serve standards-compliant mark-up, I've found that it is usually the case that people who use IIS have little or no regard for users of other web browsers or other operating systems. I think this is mainly due to the bad examples which Microsoft set.

      In the United Kingdom, Microsoft seems to dominate the thoughts of almost everyone who requires any ICT solution, such as a web site. I find this both annoying and worrying.

      You can be sure that if you make use of Web sites based in the UK, or provided for citizens of the UK, you will regularly face:

      • mark-up which only renders correctly for Internet Explorer;
      • documents which are only available in Word format; and
      • downloads which only work on Windows.

      Furthermore, in the UK, matters related to ICT are very rarely, and usually never covered on televised news. You won't hear about software patents, the dangers of using Internet Explorer or anything related to open source software--nada.

  19. IE/Firefox/BBC by curtisk · · Score: 2, Interesting
    That's interesting, I wonder what percentage of US sites are IE biased? And really how thorough are these studies?

    TFA mentions that this is due to devs targeting IE, or testing their work under IE. I do just the opposite. I work in mozilla/firefox, THEN test in IE. If any issues arise, its alot easier coming from a "mozilla" than from "ie" build and working out the kinks.

    Although it is annoying that MS tends to make their own tags, leading to situations like this...its a competitve market, so any bells, whistles or extras you can throw in makes your product stand out. Most people don't even know or care about W3C standards, valid CSS etc. Does it look cool and work for them, thats all they care about. Hell, even the latest PHPBB uses IE only tags...

    In somewhat related news, British Comedy stylings alienate 10% of world population.

    --

    Sehr geehrter Toilettenbenutzer!

    1. Re:IE/Firefox/BBC by TheRaven64 · · Score: 2, Insightful

      The thing I found most interesting was that they described Firefox as an open source web browser, without any explanation of whay open source means. While I would expect this from a tech site, the BBC technology section is very much mainstream press, and I find it interesting that they now believe that open source is a sufficiently well-known term that they don't need to define it for the general public.

      --
      I am TheRaven on Soylent News
  20. Standard Response to Complaint by blackhelicopter · · Score: 1

    I continually moan at the techies at the sites that don't support Firefox (and often Safari). Like the UK National Lottery site.

    I get the same response - "We don't support that browser".

    When I'm building a web site, I've always thought that it was up to the *browsers* to support my open-standards *code*, not the other way round.

    1. Re:Standard Response to Complaint by jrumney · · Score: 1

      My standard response to that standard response is "so if you were running a shop, would you consider it acceptable to only admit customers who were wearing Nike trainers? Do you think you would stay in business long once a few Reebok and Adidas wearers had got the word out what an arrogant prick you are?"

    2. Re:Standard Response to Complaint by BigBadBus · · Score: 1
      I thought the Lotto website did, at last, support such browers? Have a look at this site for a run-down on one man's fight against the "IE is God" mantra.

    3. Re:Standard Response to Complaint by packetl0ss · · Score: 1

      Too bad someone didn't think of having browsers send a "standards-supported" header instead of a "user-agent" one.

    4. Re:Standard Response to Complaint by 16K+Ram+Pack · · Score: 1
      and my answer is then "well, I'm not buying ... from you".

      We have limited power in this world. The odd vote every few years. One area that we can try and improve things is in our spending choices. And I avoid non-FF sites. 2 sites at similar prices and one gives me a "best viewed with IE". I'll buy from the other guy.

    5. Re:Standard Response to Complaint by julesh · · Score: 1

      They'd only reject based on "standards-supported: activex/2.0" or something.

    6. Re:Standard Response to Complaint by julesh · · Score: 1

      But there are many things that there isn't a reasonable choice for -- look at the sites listed:

      Odeon.co.uk - this company operates the only cinema I can get to within half an hour on public transport. I don't have much choice but using them (however they do have a text only site that works well, I've found, so I wouldn't actally complain about them myself).

      Jobcentreplus.gov.uk - a government agency, not much choice there.

      Companieshouse.gov.uk - another government agency

      So, out of 8 that are listed, 3 are people I have no choice but to deal with.

  21. Oxymoron by Shinaku · · Score: 1

    I'm not sure if this is just me or what, but I actully find it easier to develop websites for Firefox than I do for IE. Firefox supports transparent PNGs.. CSS2..

    --
    -- :>
    1. Re:Oxymoron by the+plant+doctor · · Score: 1

      *sigh* It is MUCH easier to make a page that works in Opera, Gecko Based Browsers, and Safari and Konq all at once than to make one that works will all those AND IE.

  22. Its Not Just Common Browsers by Zane+Hopkins · · Score: 2, Insightful

    Its not just firefox and safari that have problems with these sites, more folk are using pdas of even mobile phones to browse for info on the net, and Sites with fancy frontpages especially using flash or IE specific javascript are alienating customers every day.

    Isn't there someway we can shame the developers into always ensuring there is a simple way into their sites.

    This also applies to blind surfers who use browsers that speak the page to them. So many sites are inaccessible to them

    1. Re:Its Not Just Common Browsers by Anonymous Coward · · Score: 0

      If it's a British corporate site then the Disability Discrimination Act could be used to force them to make their sites accessible to blind surfers.

      If I can manage to make my hobby site accessible to disabled people with the limited time I've got available, it can't be that difficult for businesses to do it.

  23. Lazy Webmasters by Szaman2 · · Score: 1

    This is probably because the lazy webmasters do not feel like learning the standards, or don't get paid enough to actually care.

    Or they don't have enough technical know how to fix the page they made in FrontPage.

  24. ACID test by genocyde · · Score: 0, Troll

    I'm a die hard firefox user, but firefox doesnt even pass the acid test. Don't complain that "firefox is being alienated" when it doesnt even pass rudimentary web tests

    1. Re:ACID test by Cat_Byte · · Score: 1

      Thank you. All I could think of reading all these comments was how biased it was (yet ppl claim to not like biased news on here). Firefox needs to be able to render this stuff. If they could, people would flock to it the first time they got an IE exploit. I have firefox but it doesn't work with my bank website. I don't blame the bank or Microsoft, I blame Firefox for being the only dung heap on my system that can't render it. Opera, Netscape, IE...they all work. I'm sure even the POS AOL browser works with it but I don't have it to try it.

      --
      Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
    2. Re:ACID test by TheRaven64 · · Score: 2, Informative
      The ACID2 test is not a rudimentary test. ACID2 tests the browsers support for some really obscure corner cases in CSS (and IE fails it very badly).

      I use Safari, the development branch of which does pass ACID2 (although the version I'm using does not, and I can't be bothered to roll my own version of WebKit), but saying a browser is no good because it doesn't properly display ACID2 is ludicrous. As far as I know, the only browser where the release version correctly renders ACID2 is Konqueror.

      Firefox, Opera, Safari and Konqueror (not in that order) all come much closer to correctly displaying CSS2 than IE.

      --
      I am TheRaven on Soylent News
    3. Re:ACID test by 99BottlesOfBeerInMyF · · Score: 1

      I have firefox but it doesn't work with my bank website. I don't blame the bank or Microsoft, I blame Firefox for being the only dung heap on my system that can't render it.

      So let me get this straight. You're blaming Firefox for not properly rendering a page that is written to an unpublished specification (Lets call it MS-HTML), with multiple versions, whose only reference implementations are closed source and patented and owned by one of the most litigious companies on the planet and only run on a closed source operating system that the program has been compiled into. And does you banking site specifically check for a user string and deny access on that basis? I'm sure the firefox developers would have no problem making Firefox work with your banking site if that was their goal. Making it work with your banking site and the thousands of other banking sites and the millions of other sites, all of which follow this invisible MS-HTML spec is a lot harder though.

      If you banking site is coded to spec then, yup it's Firefox's fault. If not, then it is the banking site's fault. Why the hell do you think we have a published HTML spec in the first place?

  25. Re:In Other News by thezapper77 · · Score: 0

    I was simply pointing out that this is hardly newsworthy...

    10% of sites in UK are incompatible with firefox?
    Thats nice to know... Next please...

  26. Opera: Firefox user figures 'inflated' by Anonymous Coward · · Score: 0

    The chief executive of Opera Software claimed on Monday that the market share figures for Mozilla Firefox are inflated, due to its support for link prefetching.

    Read more here:
    http://news.zdnet.co.uk/0,39020330,39204643,00.htm

  27. Greasemonkey by MartinG · · Score: 1

    What would be good is if there was a greasemonkey script for these sites that rewrote the broken javascript into something standards compliant, then firefox users need not worry. ... or would that be a bad thing because the site owners would no longer have as much incentive to fix their sites properly?

    --
    -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    1. Re:Greasemonkey by MartinG · · Score: 1

      apologies for replying to myself. I just noticed there are some.

      here is one that fixed the jobcentreplus site:

      http://dunck.us/collab/GreaseMonkeyUserScripts#hea d-49b3c2b6e238f0b8656eed10bc8f782230a75eb4

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
  28. This pops up an idea in my mind by Alarash · · Score: 1
    What we, tech savvy people, should do, is open a website where we'd list all the websites compliants only with IE, and list portions of their source code that make it so. Maybe it's time to educate webdesigners and decision makers of the cons (and pros, if any) of being compatible only with one browser, all possible exploits, etc...

    Basically, just being productives instead of just looking at the market share figures. Like, pro-active, you know.

    1. Re:This pops up an idea in my mind by Anonymous Coward · · Score: 1, Interesting

      If you want to contribute to an existing project rather than start off on your own, there's a whole section of the Opera forums devoted to such things. Some of the sites on their list do work in Firefox, and there are others that work in Opera but not FF and others, but it's a good place to start from at least.

  29. No IE allowed by tigerd · · Score: 1

    my danish blog page, can be viewed in any browser, except IE. He he, fight back, I do...
    http://blogwars.blog.com/

    1. Re:No IE allowed by SolidGround · · Score: 0

      Funny considering how it seems to like mine just fine :).
      You did get me to click though so A+ for effort and cleverness.

    2. Re:No IE allowed by tigerd · · Score: 1

      well i get lots of bitching from ie users, and it doesnt work on mine either(all the text is pushed to the right)

    3. Re:No IE allowed by SolidGround · · Score: 1

      IE breaks the title after 'det' but other than that I don't see a difference.

    4. Re:No IE allowed by Anonymous Coward · · Score: 0

      Pulls up fine in IE for me.

      After reading it, I kinda wish it hadn't.

  30. Breaking News...UK only has 40 websites! by sweetnjguy29 · · Score: 2, Informative

    From the actual study located at http://www.scivisum.co.uk/press-releases/200506_Fi refox_Web_Test_Study.htm

    "Guilty websites

    Odeon (http://www.odeon.co.uk/ a major cinema chain has received criticism for months for accessibility issues - even now its' opening 'splash page' seems at first glance to be working fine but click on the 'enter' button and Firefox users are offered a blank page.

    On the Jobcentreplus (http://www.jobcentreplus.gov.uk/ home page, Firefox users find that the 'Job search' button opens a new page, but the user can't perform a search, because the first choice "Select a Job Group from the list" is an empty box.

    Online insurance site, http://www.insurance.co.uk/ run by Lloyds TSB works, but gives the user the visual impression that it is broken - menu items have 'missing images' icons in Firefox, but not IE.

    Similarly, a FTSE100 tobacco company, British American Tobacco's website (http://www.bat.com/ effectively hides most of it's pages from Firefox users - their menu system doesn't show sub-menu choices if you're not using IE."

    Well, thats 4 websites...so, if thats 10%, that means that there are only 40 websites in the UK, according to my Athlon XP 3200+ Clawhammers FPU...

    1. Re:Breaking News...UK only has 40 websites! by smallguy78 · · Score: 1

      http://www.datagrid.com/ is another guilty one

      --
      Nothing costs nothing
    2. Re:Breaking News...UK only has 40 websites! by djmurdoch · · Score: 4, Informative

      I think you missed this: "Of 100 UK leading consumer websites that SciVisum tested...".

      I imagine they chose that sample size to make the percentage calculations perfectly accurate.

  31. Vindication! by saintp · · Score: 1, Insightful

    And this, ladies and gentlemen, is why Opera self-identifies as IE: Fully 3% of the sites they tested turned away non-IE users without even trying.

    1. Re:Vindication! by GigsVT · · Score: 2, Interesting

      All the more reason for browsers to identify themselves correctly. If no one is aware of the problem, no one will complain to get it fixed.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:Vindication! by saintp · · Score: 1
      Slow down there, Mr. User Friendly! You think that Opera would *win* if it broke more websites for its users? Your key element of design is, "It Doesn't Work, so complain"? Here's some advice: don't apply for a job at Apple any time soon.

      In case you didn't notice, it's not a problem for Opera users. (Or much of a problem for Firefox or Safari users who know how to change how their browsers self-identify.)

    3. Re:Vindication! by Anonymous Coward · · Score: 0

      It doesn't appear to be helping opera much. They barely register on web site stats.

    4. Re:Vindication! by GigsVT · · Score: 1

      You think that Opera would *win* if it broke more websites for its users?

      In the end, yes.

      It's like putting on layer after layer of deodorant instead of taking a bath. Taking a bath might take longer in the short run, but it's the only way to address the root of the problem.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
  32. Why are they picking on Firefox users? by webgit · · Score: 2, Interesting

    The BBC article and the original SciVisum article (and of course the slashdot article) are all aimed at Firefox users. However, this survey is just pointing out that these web sites are IE-centric and don't work with most other browsers, not firefox specifically.
    I guess the reason they pick on Firefox is because they're starting to become a very popular competitor to Internet Explorer for Linux and Windows users, and of course this means that we've got to make it look bad in comparison.

  33. Re:Text by jasoncart · · Score: 0, Offtopic

    Nice, but the BBC site is one of the most popular in the world and gets a lot more traffic that this one hence it is impossible to slashdot.

  34. Patience, you'll see a counter effect by NigelJohnstone · · Score: 1

    So? One of my sites doesn't work so well on IE, a moving progress bar doesn't update if you use IE but does work if you use Firefox.

    (Its just an animated GIF I set to visible before a slow page switch, for some reason it didn't work on IE).

    Because I used FF for the better Javascript console to develop it with, the site works slightly better with FF and I only noticed it when I came to test it on other browsers at the end.

    The way I figure it, Firefox is increasingly being used by the tech savvy people and so we'll see lots of things like this, sites that work slightly better on Firefox because thats what they were developed on, and no so well on Internet Explorer.

    I can't ignore IE, but its a pain to cope with its quirks and 'good enough' is 'good enough'.
    IE users won't miss the little animated bar.

  35. Odeon is terrible by Mr_Silver · · Score: 4, Informative
    Although it'll probably annoy a lot of people here, I can generally put up with sites that render stuff badly or try to get you to "upgrade" to IE when you're using Firefox because at least I can still get at the content.

    However, the Odeon site is completely inaccessible. It's not a case of stuff not looking or formatting correctly, but once you followed the "entire site" link it was more a case of nothing actually being displayed to the user - no listings, no cinemas, nothing.

    Even worse, if you emailed them to complain, they told you the site was undergoing a re-design. To my mind that has had to be at least a couple of years ago all because they couldn't be arsed to change some IE only javascript.

    Anyway, if you've got GreaseMonkey this script will make the site accessable again.

    ps. Whilst we're at it, if you have a phone or PDA then you might be interested in Movie Guide which provides you with you with detailed listings of all films showing in UK Cinema's.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
    1. Re:Odeon is terrible by TwistedSquare · · Score: 1

      Yes! The Odeon site really bugs me, besides the slightly iffy design it simply won't do anything under Firefox as you say. I'm glad that I now have a choice of cinemas where I live, so I can book online without having to faff around. Thanks for the GreaseMonkey link.

    2. Re:Odeon is terrible by Frogg · · Score: 1

      since the whole debacle with www.odeon.co.uk over accessiblity (wherein odeon tried to sue some guy who scraped their site and served it up text only) they now provide a text-only version of their film times (it's linked from their front page).

      adding that info on text-only pages /was/ their site redesign!

  36. other news by RasendeRutje · · Score: 0

    And in other news, 99% of all website don't comply to any standard... jeez

    --

    If Microsoft was mass, stupidity would be gravity.
  37. Not Easy to Keep it Simple by ehaggis · · Score: 2, Interesting

    As someone who uses Firefox and also is a novice at making websites, I find it is difficult to create a dynamic site without extending it beyond someone's standard.

    However, many times when I am faced with a site with which I must do business (i.e. insurance, commerce, etc...) and they are not accessible via Firefox, I call and complain. Otherwise they will not know. If I can, I will let them know I have chosen a competitor.

    --
    One ring to bind them - should probably have more fiber and less rings in their diet.
    1. Re:Not Easy to Keep it Simple by mike.newton · · Score: 1

      There is almost nothing that can't be done in any modern browser. What exactly do you mean by "dynamic"? Check out some of these sites.

  38. ActiveX by Szaman2 · · Score: 3, Insightful

    Some companies simply do not care about this. I'll give you an example:

    My company has a web based time tracking system where you enter your hours. It is the most horrible piece of garbage I have seen in my life! It requires ActiveX to display stupid menus which could have been done in javascript, and the layout is nested frames. If you view that thing in antything but IE you get empty frames all over the place - half of the content is somewhere off screen and you can't navigate the site at all

    When I brought it to their attention they had three questions:

    1. What is that firething you talk about?
    2. Who uses it except you and the other computer nerds?
    3. Why should we care if it works fine for all of us except you Mr. "I'm to good to use IE"?

    Needles to say I work with technically retaded people - but they make the decissions, not me...

    1. Re:ActiveX by tomstdenis · · Score: 1

      1. It's an open source browser written by a group of people who want nothing more than to bring high quality tools to people for low to no cost. The more commercial entities like us support them the more financial backing the developers can get through employement, grants and donations to continue the work.

      2. People who are progressive and sick of paying high premiums for low quality software.

      3. You should care because it's more modern, standards compliant and secure. Also see #1.

      Tom

      --
      Someday, I'll have a real sig.
    2. Re:ActiveX by pandrijeczko · · Score: 3, Funny

      The impact of your more than adequate reasons would be further enhanced if he hits those same people over the head with a bit stick while he's telling them.

      --
      Gentoo Linux - another day, another USE flag.
    3. Re:ActiveX by Szaman2 · · Score: 1

      This would be more or less what I told them... And the bosses just shruged and wandered away muttering something about "those damn IT people and their toys" :P

      I have converted quite a few people to Firefox... However some people simply refuse to even look at something different than IE because this is what they have learned to use (with some great pains along the way apparently) and they are affraid of change...

    4. Re:ActiveX by Szaman2 · · Score: 0

      LART!!! hehe - Good idea, I will apply this! :D

    5. Re:ActiveX by tomstdenis · · Score: 1

      You mean a BFCB... Big Foam Clue Bat.

      Tom

      --
      Someday, I'll have a real sig.
    6. Re:ActiveX by pandrijeczko · · Score: 1
      No, remember the training:

      Foam Bat for Opera users, Spiked Concrete Baseball Bat for the Microsofties...

      --
      Gentoo Linux - another day, another USE flag.
    7. Re:ActiveX by tomstdenis · · Score: 1

      I clearly have much to learn. My training is of yet incomplete.

      Hehehe.

      Tom

      --
      Someday, I'll have a real sig.
    8. Re:ActiveX by courtrrb · · Score: 1

      The attitude I recieved was your supposed to use IE if we can't/wont do a dam thing about if you don't! I then tell them we use linux in our department and IE dosn't run on Linux. Then they say "your the only one complaining". I later found out the the whole department complained and everybody just gave up and works around the problems because the company just don't give a dam.

    9. Re:ActiveX by Anonymous Coward · · Score: 0

      Here is your response:

      > Firefox is an alternative browser which, along with Safari and a few others, is used by 10 to 15 percent of web surfers.

      > Given our current webpage design, those 10 to 15 percent of web surfers cannot use our site.

      > If you are satisfied with losing 10 to 15 percent of our potential customers, for reasons that are entirely avoidable, then that is, of course, your decision to make. I just wanted to ensure that your are aware of the situation.

      By the way, the opposite situation occurred at the company where I work. One of the previous sysadmins was fired because he would not stop using ActiveX in our website. So, yes, you can get fired for choosing Microsoft.

    10. Re:ActiveX by westlake · · Score: 1
      "those damn IT people and their toys"

      people simply refuse to even look at something different than IE because this is what they have learned to use (with some great pains along the way apparently) and they are affraid of change...

      Firefox can become a toy, with all its configuration options, add-ons, and embellishments.
      But most IE users are simply readers, moving from page to page, occasionally stopping along the way to shop on line, fill out a form, play a media file, or a game.

    11. Re:ActiveX by Stone+Pony · · Score: 1
      "it's more modern, standards compliant and secure" really isn't going to cut it with the kind of decision makers that the GP is talking about. Well, the "more secure" bit might, but the rest certainly won't.

      Modernity and standards compliance aren't reasons for action in themselves. There has to be a pay-off, and if a system works with a non-compliant browser then what is the pay-off in reworking it to comply with these "web standards" of which some whiny tech-guy speaks?

      A small part of my job involves intranet development in an organisation where roughly 30% of the staff use IE6 and the rest use IE5.5. There are complicated contractual reasons for this, but the fact is that our intranet has to be designed around those restrictions and the powers-that-be don't care so long as the system works within its own borders.

    12. Re:ActiveX by sapped · · Score: 1

      So they use Niku at your place as well heh?

    13. Re:ActiveX by Szaman2 · · Score: 1

      Actually no. It's a custom made application which was written for us long before I ever started working there...

      Sad part is that even though it is a piece of crap, we still pay big bucks for hosting and maintenance of that thing every month :(

    14. Re:ActiveX by ajs318 · · Score: 2, Insightful
      most IE users are simply readers, moving from page to page, occasionally stopping along the way to shop on line, fill out a form, play a media file, or a game.
      Or pick up some software ..... whether they want it or not .....
      --
      Je fume. Tu fumes. Nous fûmes!
    15. Re:ActiveX by Java+Ape · · Score: 1

      Ahh, we must work for the same company! We apparently spent a small fortune to develop something called "e-time". Biggest bodge-job I've seen in my life! But it was all developed with state of the art Microsoft tools, by certified code monkeys, so it must be good (or so the reasoning goes). Bah Humbug!

    16. Re:ActiveX by Szaman2 · · Score: 1

      Heh. Ours is called Velocity :) Funny thing - the log in page includes a 800x600 image background which takes forever to load :P

      What baffles me is that the same guys who produced that run a linux on their email server. Why didn't we go for LAMP (Linux, Apache, Mysql, PHP) for this project is beyond me. But hey - I'm not the decision maker around here :(

    17. Re:ActiveX by Alsee · · Score: 1

      the log in page includes a 800x600 image background which takes forever to load

      Oops, I almost forgot you had to use IE to access the site. I was about to ask:

      Do you have adblock installed? You could just add the image to the blocklist.

      Oh well. Heh.

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
  39. Who cares? by Turn-X+Alphonse · · Score: 1

    I'm from the UK and I have to say theres next to nothing I care about here website wise. Other then the BBC and a Tv guide I couldn't carless if it's hosted in the UK or else where, if it doesn'twork with my browser I'll google what I want and find it that way.

    --
    I like muppets.
  40. 10% of all websites, but not 10% of all page views by egghat · · Score: 1

    All big sites now support Firefox (which means they're somewhat standards compliant). The 10% of all websites will consist of a lot of obscure, badly maintained and small sites that nearly noone cares for (of course exeptions proves the rule).

    Bye egghat

    --
    -- "As a human being I claim the right to be widely inconsistent", John Peel
  41. IE only sites by DeadSea · · Score: 4, Interesting
    Are sites IE only because IE has features that firefox does not, or because developers are lazy and don't check in multiple browsers.

    In the later case, of developing in IE, and not checking with Firefox, does anybody know what the most common things that break are?

    In the IE features category, I have seen one thing that IE does really well that Firefox does not do: Image transition filters such as the fade in/out effect when you switch photos. Are there other things the you as a developer want, but are only implemented in IE?

    I know on the other side, that I want rounded corners on divs and alpha transparency in pngs to be properly implemented in IE.

    1. Re:IE only sites by ephemeraleuphoria · · Score: 3, Informative

      However, those features can be implemented using standard javascript and CSS, people just choose not to: http://nocturne.net.nz/webdev/imgfade.php

    2. Re:IE only sites by ajs318 · · Score: 1, Troll

      I develop sites to work in Firefox. Frankly, I don't give a flying toss if they run in IE or not. Anyone can run Firefox. Not everyone can run IE.

      I believe it is morally very dodgy indeed to insist for someone to run a piece of closed-source software.

      --
      Je fume. Tu fumes. Nous fûmes!
    3. Re:IE only sites by Anonymous Coward · · Score: 0

      This site seems to work in Mozilla.
      http://www.subiacreative.com/print-portfolio.html/

    4. Re:IE only sites by john_lewmanny · · Score: 1
      That was by no means Standarts Compliant. It's just a solution for 4 different browsers at the same time:
      // IE/Win
      obj.style.filter = "alpha(opacity:"+opacity+")";
      // Safari<1.2 Konqueror
      obj.style.KHTMLOpacity = opacity/100;
      // Older Mozilla and Firefox
      obj.style.MozOpacity = opacity/100;
      // Safari 1.2, newer Firefox and Mozilla, CSS3
      obj.style.opacity = opacity/100;
    5. Re:IE only sites by Anonymous Coward · · Score: 0

      I believe it is morally very dodgy indeed to insist for someone to run a piece of closed-source software.

      How often does that happen? Only if you must run that software in order to get basic services common to all your peers. Let's say the government said that the only way to get healthcare is to visit a website that only works with IE. That would be morally dodgy. But if Bank A's website requires IE, it's not so bad because you can always bank by phone or in person, or use another bank.

    6. Re:IE only sites by orionware · · Score: 1

      That's actually pretty stupid. There are several occasions where something will render in Firefox that will not look correct in IE. Most of the time it's from Javascript and DHTML.

      If I were a client and your attitude was , "Well screw those 90%+" I'd surely take my business elsewhere.

      --


      Karma means nothing to me, so suck it...
    7. Re:IE only sites by stuntpope · · Score: 1

      All I know is that the Korean sites my wife likes to visit work poorly, with reduced features, on anything other than IE on Windows. Even IE on Mac blows with these sites. Pretty piss-poor, designing a fancy site that requires the user to not only use a particular browser, but a particular operating system. A lot of it is non-compliant JavaScript (watch those error message fly by in FF JavaScript console!), and I suppose ActiveX.

    8. Re:IE only sites by Brandybuck · · Score: 1

      Instead of fixing the problem, you instead migrate stupidity into the Firefox domain. Not everyone can use Firefox, because some people do not have the ability to install Firefox on the systems they use. Others can use Firefox, but they're not about to stop everything and install and learn a new browser just because you cop an attitude.

      And then there's people like me. We've got Firefox installed, but we happen to be using another browser (Konqueror, Opera, Safari, etc). That's our right. It's our choice. It's our freedom. We're not going to shut down our current browser and start up Firefox, just to see you're site. They annoyance isn't worth it. So instead we make a mental note never to visit your site ever again.

      --
      Don't blame me, I didn't vote for either of them!
    9. Re:IE only sites by tom's+a-cold · · Score: 1
      Are sites IE only because IE has features that firefox does not, or because developers are lazy and don't check in multiple browsers.
      I see a lot of things. A lot of sites use non-compliant Javascript (that is, the extensions that are not ECMAscript) for tabs and menus. Quite a few also use ActiveX controls.

      The main reasons are: the developers are ignorant, the coding and testing effort is greater with multiple browsers (as you mentioned), and some people (particularly certain businesses and government agencies) have a take-it-or-leave-it attitude. Like utility companies: we don't care-- we don't have to. This is even more flagrant in intranet applications, where IT departments seem to think that a locked-down environment means that they don't have to be standards-compliant. Then along comes a new desktop standard, or a new platform such as handhelds, and the IT department end up looking like morons because the enterprise apps don't play nicely with non-IE browsers.

      If the non-standard features in IE were delivering critical functionality, I could understand it. But more often they're just little bells and whistles or shortcuts that don't really matter to anyone all that much (besides those low-skill developers who have never ventured outside the MS cocoon).

      These bozos are nearly as bad as the corporate idiots who regard the Internet as nothing but a giant file system to upload their shitty PDFs to.

      --
      Get your teeth into a small slice: the cake of liberty
    10. Re:IE only sites by Brandybuck · · Score: 1

      Are sites IE only because IE has features that firefox does not, or because developers are lazy and don't check in multiple browsers.

      Both, though the latter is more frequent. Everytime I come across an IE-only site in my work's intranet, and oftentimes when I encounter one outside of work, I fire off a message to the webmaster complaining about it. The responses I get back tell me a little bit about how they think.

      My company is deeply in bed with Microsoft, so it's no surprise that many of the IE-only sites at work are due to IE-only applications and infrastructures. The prime example is Microsoft Sharepoint. You cannot use it without IE. Then there's our timecard application that is a IE-only Java applet. Yup, you read that one right: an IE-only Java applet. I guess they're getting in practice for a move to .NET.

      I've never yet met a developer who deliberately used IE-only features. The culprit instead is laziness. They never test their pages. Sometimes they get very irate when you suggest they test their pages. As a software developer I have to test and have reviewed everything I check in. But to your average web developer, testing and reviewing (or even acknowledging bugs) is simply not done. For all you web developers that do practice quality, bless you! Unfortunately you're in the tiny minority.

      I've even had one developer tell me he didn't have the financial resources to test on Mozilla. Being Free Software didn't deter him. "I'll have to get IT to install it and they'll charge my department..."

      p.s. Some are even lazier than that, though, and transcend the bounds of mere monobrowserism. I've met more than one developer who hardcoded in a width of 800 pixels for the total width of their pages, just so the pages would be "guaranteed" to fit in 800x600 screens. If they had ever bothered to actually text their pages on such a screen, they would have discovered the rude fact that 800 pixel wide pages do not fit on 800 pixel wide screens.

      --
      Don't blame me, I didn't vote for either of them!
    11. Re:IE only sites by 1110110001 · · Score: 1
      That was by no means Standarts Compliant. It's just a solution for 4 different browsers at the same time:
      // IE/Win
      obj.style.filter = "alpha(opacity:"+opacity+")";
      // Safari<1.2 Konqueror
      obj.style.KHTMLOpacity = opacity/100;
      // Older Mozilla and Firefox
      obj.style.MozOpacity = opacity/100;
      // Safari 1.2, newer Firefox and Mozilla, CSS3
      obj.style.opacity = opacity/100;


      The last line is the standard - it's in CSS3. The other lines are just for older browsers.

      b4n
    12. Re:IE only sites by Anonymous Coward · · Score: 0

      put down the crackpipe son, if it renders in firefox it will work just fine in safari/opera/whatever

    13. Re:IE only sites by mike.newton · · Score: 1

      In the later case, of developing in IE, and not checking with Firefox, does anybody know what the most common things that break are?

      Mostly it's javascript based sites, that rely on javascript to display the contents of the page. These sites aren't just broken in Firefox, they're often broken in any browser other than IE and Netscape 4. Yes, that's right: Netscape 4. The crap 7 year old browser that has a market share of probably 0.3%. Look at the code for one of the sites in this article. You'll see things like:

      if (document.layers) {
      ...
      }
      else if (document.all) {
      ...
      }
      //do stuff

      For the non-programmers, that's saying "is it Netscape 4? Well if it's not, it must be IE" and not checking for anything else. This is because these people learned to design web sites in 1996, and haven't taken the trouble to update their skills. Any "web developer" should seriously question their sanity when they make a conscious decision to support a dead 7 year old browser.

    14. Re:IE only sites by ajs318 · · Score: 1

      Exactly. IE is the problem.

      Anyone thought of having a malicious ActiveX control that downloads and installs Firefox?

      --
      Je fume. Tu fumes. Nous fûmes!
    15. Re:IE only sites by Brandybuck · · Score: 1

      Exactly. IE is the problem.

      Wrong. Browser-centric sites, no matter how free the browser in question may be, are the problem. It was wrong when Netscape was a monopoly, it is still wrong now that IE is the monopoly, and it will be wrong in the future if Firefox/Mozilla ever gets to be a monopoly.

      The essence of HTML is that it is content, not layout. This means that every browser will render the page differently. As long as website are targeted towards a specific browser to the detriment of other browsers, we have a problem. This is true even if standards are used, because there are always dark corners in every standard, especially when it's something like HTML/CSS that changes every couple of years.

      --
      Don't blame me, I didn't vote for either of them!
    16. Re:IE only sites by aztracker1 · · Score: 1
      generally, I do something like..
      if (document.getElementById) {
      //do my stuff
      } else {
      location.replace("/old_browser.htm");
      }
      ....
      [n oscript]
      Javascript, Cookies, and a modern browser are required for this site. [a ...]Click Here[/a] for more information.
      [noscript]
      In any case, unless you're in a firefox1.0+ or mozilla 1.6 (at least late 2004 gecko) or ie6, or opera 8... you should update for security reasons alone, though IE is still pretty open, though not as wide as before.

      I just don't get it, honestly 99% of anything today can be done with html, css/styles, javascript and ajax. For sites that are more than 3-4 years old, it's kind of understandable, IE was way ahead at the time, but they're probably (sites that old) at a point where they *should* be updated..
      --
      Michael J. Ryan - tracker1.info
  42. or... by Anonymous Coward · · Score: 0

    Firefox is incompatible with 10% of UK websites. In the mind of the end user, if it worked with A and doesn't work with B then the problem lies with B.

  43. more common that you might think by Anonymous Coward · · Score: 1, Interesting

    A lot of mass-market, public facing sites are horribly built and designed, and have clearly been built without any consideration to other browsers at all.

    For instance, I (unfortunately) bank with The Woolwich, which has possibly the most pointless online banking service in the world.

    The online banking site only works in PC IE and Netscape 4. I've emailed them a few times, and have only got a response once. My initial email was inquiring as to why I couldn't gain access to my bank account in Firefox/Windows, Firefox/Mac OSX, or Safari - god knows what *nix users are supposed to do. I also pointed out that under the terms of the Disability Discrimination Act, they are clearly and flagrantly breaking the law.

    They only saw fit to answer my questions about Mac support, ignoring the wider browser, accessibility, and you-might-get-sued issues, but nonetheless, their response was hilarious :

    Dear Mr xxxxx,

    I refer to your recent email of dissatisfaction with the Woolwich Internet Bank.

    Firstly, I would like to apologise for any inconvenience caused for not supporting Apple Macintosh with the Woolwich Internet Banking site. During the design phase of the current Internet Bank, we had every intention of supporting a range of Apple Mac systems. However, as the functionality of the Internet Bank increased, so did the complexity of the code.

    Our Technical Team have recently conducted a full review of the Woolwich Internet bank, and to make our site Apple Mac compatible we need to rewrite all the code which sits behind the site. Due to the complexity and time/resource required, we have taken the decision not to support Apple Macs.

    We have updated our site to reflect our decision, and this information can be located in the FAQ, and in the 'What you need' section within the Internet Banking hub.

    Thank you for taking the time and trouble in writing to us. Your comments have been sent to the appropriate team to review.

    Kind Regards,

    Mark Robbins Technical Support Analyst E Commerce Technical Support SupportE-Commerce@woolwich.co.uk 0845 600 0999 (Option 1)

    Which sounds very much like an admission of incompetence, no? "Our code was so vendor-specific and umaintainable that we'd need to bin it and start again. Sorry!"

    It's worth bearing in mind that their site has been in this case for at least three years. What, that's not long enough to rewrite the clientside code of a relatively simple webapp. WTF are you people, monkeys?

  44. Includes javascript? by m85476585 · · Score: 1

    Does this include JavaScript? Because in IE, you have to use document.all and in Netscape (firefox), you have to use document.layers (I think), and it is understansable for some sites not to support both, because it is a lot more work to.

    1. Re:Includes javascript? by Anonymous Coward · · Score: 0

      Actually, IE since version 4, netscape since 6.0, all other browsers in their actual versions support
      document.getElementById();

      Unless you are coding a site for ie = 3 (document.all) or Netscape = 4.x, you should not need anything else.

      On a side note, this does not apply to coding for forms, as the javascript interface for this has been stable for ages:
      formname.elementname.value ...

      This is also the only way to properly address radio buttons (exercise left to the reader).

    2. Re:Includes javascript? by Rogue+Pat · · Score: 1
      Because in IE, you have to use document.all and in Netscape (firefox), you have to use document.layers

      Incorrect. Use the W3C standard here: document.GetElementByID
      That is supported by ALL browsers since the stone age [1998]. The document.all is to make it work with IE4 specifically [market share 1%], and only implemented in more recent IE's for backwards compatibility. And document.layer is for Netscape 4 only. More recent Netscapes [6 and up] are build on "Mozilla Technology" and don't support .layer anymore, but instead use .GetElementByID
    3. Re:Includes javascript? by masklinn · · Score: 1
      This is also the only way to properly address radio buttons (exercise left to the reader).
      That's wrong, and since you need an ID to use labels on form elements (nifty thing if you have anything but IE) you'll usually be able to use getElementById on pretty much anything
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
  45. Inraweb by SAP by spectrokid · · Score: 1

    Our intraweb apps (mostly SAP) are IE only. And these should be made by people who actually know something about coding. Seesh..

    --

    10 ?"Hello World" life was simple then

    1. Re:Inraweb by SAP by frank_adrian314159 · · Score: 1
      And these should be made by people who actually know something about coding.

      And the sad thing is that they probably were.

      All of the big enterprise suites are highly customizable. The companies who deploy these apps pay hundreds of thousands of dollars to customize them. They are designed to be skinned and the javascript used in them can be tweaked to within an inch of its life. And, believe it or not, the companies providing and/or implementing these apps don't go out of their way to hire idiots. Most of the time, the coders who do the implementation are driven toward bad design because the companies who buy the app don't want to pay for the extra time it takes to make these systems standards compliant. For the deploying company, it's cheaper to put an underpowered PC on each Mac user's desk than to pay for the design necessary to support Safari. Nor does the company that supplies the app want to eat the cost of making the app portable - it's cheaper to convince the customer that making it IE-only is just fine (though to be fair, a lot of them actually are flexible enough to work on any browser if the customer is willing to pay). The company doing the implementation has generally won its bid based on a fixed functionality, fixed-price contract, so it would be suicidal to have their page monkeys do anything that's not specified in the contract.

      So don't blame the page designers (who generally do know enough to design good, standards compliant pages and who have very little say in the matter) - blame the companies who are too cheap to pay for them to do a good job.

      You can also blame companies who deploy customer-facing web applications that don't work on non-IE browsers. They should know better (or they do know better and have specifically chosen to alienate a potential customer segment). And the best way to get the message accross is to complain frequently and loudly and to vote with your wallet.

      --
      That is all.
  46. Easy standards for those who are "not so stupid" by standards · · Score: 3, Interesting

    Firefox is slowly making inroads. Its share of the browser market grew to 8% in May, up from 5.59% at the beginning of the year, according to US-based analysts NetApplications.

    That may be true over all, but in my world (a large site primarily attracting the 18 - 29 year old demographic within the US) we see something different: FireFox (16%) and Safari (5%).

    We have a small development shop (5 developers), but we find it extremely easy to build and deploy a sophisticated web user interface that is compatible with IE, Mozilla + varients, Safari, Opera, Konqueor, and more.

    The "trick", if you want to call it that, is to reuse good UI code. Such a strategy saves us time and money, and keeps us lean and keeps us (at least usability-wise) well ahead of the competition. Oh, and we also support accessibility standards.

    I have a feeling that we do it well because most all of our developers are professionals - they didn't just "stumble into the webmaster job by creating a webpage".

    Anyhow, just as well - our competitors' sites look and work like crap.

    I remember when a competitor's site crapped out was broken for weeks when a new version of IE was released... they had many versions of their UI code splattered throughout their site - I feel bad for the people that have to deal with all that crap.

  47. Firefox needs to change. by xplenumx · · Score: 0, Flamebait

    I really think a lot of people here have forgotten (or never experienced) what it's like to be a non-technical savy individual. As far as most people are concerned, IE has been the only browser that they've ever known, probably even heard of, for as long as they've been introduced to the internet. IE is the standard. So when this new broswer, Firefox, doesn't work with 10% or so of the webpages, for the vast majority of the people out there it's not a 'lazy web-developer' issue, it's a 'Firefox is broken' issue. Not a great way to gain marketshare. Right or wrong, Firefox absolutely must work with the standards that IE has set.

    1. Re:Firefox needs to change. by dlefavor · · Score: 1
      "Say what?" department:

      Right or wrong, Firefox absolutely must work with the standards that IE has set.

      No, no, no.

      Microsoft doesn't set "standards" for browsing any more than Ford or GM sets "standards" for parking lots.

      At least, that's the way it's supposed to work...

      I'm reminded of why railroad guages are what they are and just who conforms to whom.

    2. Re:Firefox needs to change. by Anonymous Coward · · Score: 0

      So true! Firefox implemented a 'security' policy for files being uploaded where you can't access selected files for display due to the file not being in the same domain (local:// vs http://./ Granted this is to javascript spec, but it effectively prohibits any display of graphic files to upload...

      All the answers that I've gotten indicated that the javascripts which need to get access to the local file system must be signed. All attempts to locate the tools to sign them have been ended in URL not found.... lovely. And even if the scripts where signed, it means the Firefox has a totally different set of scripts that the other browsers... sigh.

      It be better, IMHO, if Firefox would actually implement a means to allow javascript access to a user selected file to be uploaded without having to restort to signed scripts. This way I could code a branch within the javascript instead of a entirely different set....

      Having said that, my site is broken right now and I'm considering implementing new screen that says "Firefox does not support access to your local drive for preview of uploaded images. Please use IE instead and complain to Firefox development team about missing lack of functionality for javascript."

    3. Re:Firefox needs to change. by Anonymous Coward · · Score: 0

      Do you really want a for-profit corporate entity like Microsoft setting standards, as opposed to a non-partisan group? That would be like letting the BNP sit on the Comission for Racial Equality...

    4. Re:Firefox needs to change. by Secrity · · Score: 1

      "Firefox absolutely must work with the standards that IE has set."

      *BZZZT* Ohhh, that's the wrong answer. Thank you for playing, we have some lovely parting gifts for you.

  48. Where's the button? by paiute · · Score: 1

    What I want is a button at the top of Firefox that automatically sends an email to webmaster@whateversiteI'mlookingatnow.com that complains about viewability and notifies them that they just lost my business/eyeballs.

    --
    If Slashdot were chemistry it would look like this:Cadaverine
  49. Vote with Your Feet by Anonymous Coward · · Score: 0

    When I find a site that doesn't recognise my non-IE browser (usually Firefox), I like to return to it later and tell the owner which of his competitors received my business. I don't how often the message gets through but it makes me feel better!

  50. 90% of sites ARE compatible with firefox! by JoeCommodore · · Score: 2, Insightful

    Sounds like a winner to me!

    --
    "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
  51. OT [ wasRe:Microsoft.co.uk] by I+confirm+I'm+not+a · · Score: 1

    www.slashdot.org.uk

    I'm using the regulation "slashdot.org", but I just tried that URL - all I got was a listing, suggesting the existence of a cgi-bin - but I didn't have permission to enter. So... what is this slashdot.org.uk business all about? They're not going to monkey with my 'fox, like Google, are they?

    Back on topic: the Gallaghers and Leprechauns in the same sentence? Sir, I salute you!

    --
    This is where the serious fun begins.
  52. comments from bugzilla 1 by Anonymous Coward · · Score: 0

    The whole thread comes down to usability versus standards compliance. I
    understand the logic for standards compliance. However, this is such a glaring
    issue to Mozilla newbies that it is a MAJOR factor inhibiting its general
    acceptance.

    I have put several clients on Firefox and frequently I get requests to shift
    back to MSIE because the web pages don't look right under Firefox (or Mozilla).
    I hear "It looks right in MSIE. Why doesn't it in Mozilla (Firefox)?" End
    clients are more concerned about the operation of a business than a whole
    explanation of why it wont work right because of a technical standard. At their
    request I shift them back to MSIE. Future clients, I have to give them a verbal
    disclaimer telling them that things might not look/work "perfectly", which is
    pretty tough to "sell" a "broken" product to a business owner. I bet I could get
    25% more of my clients to continue to run Firefox/Mozilla IF I HAD THE OPTION to
    set the scroll bar to the permanent "on" position.

    Everybody would be happy if we had an option to manually turn on/off the scroll
    bar at the browser. Those that want strict browser compliance can leave it off.
    Those that deal in the world of asthetics can turn it on. It would be an
    EXCELLENT solution instead of just walking away at the expense of the Mozilla
    project.

    1. Re:comments from bugzilla 1 by masklinn · · Score: 1
      The whole thread comes down to usability versus standards compliance.
      Does it?
      Do you really consider most "IE Only" website to be "usable"? I find most of them to be bloated pieces of crap, barely usable with a mouse and not at all without one, and I won't even touch security issues such as surfing with ActiveX or javascript disabled...

      Usability versus Standards? my ass
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
  53. Colleges and universities seem to be the worst by scolby · · Score: 1

    We have a campus pipeline here at school used for email, news, signing up for classes, that sort of thing...it gets a bit pissy when you try to talk to it with anything but IE. This is a tech school, supposedly at the forefront of modern technology and standards. Why do they insist on implementing tools that only work in one browser?

  54. Re:90% of sites = not good enough by walterbyrd · · Score: 1

    I'm sorry, but it's not. What about those few sites you actually need? MSIE is compatible with 100%, and that is what people think they need.

    I use firefox myself. Msft anti-competitive practises piss me off. But I must admit, they do work.

  55. Re:In Other News by pandrijeczko · · Score: 1
    Sorry about the "idiot" statement.

    But Slashdot is the site for all things hardly newsworthy...

    --
    Gentoo Linux - another day, another USE flag.
  56. I don't understand thats works perfectly by Anonymous Coward · · Score: 1, Insightful

    You might try that link you gave in Firefox it works perfectly!

  57. careful with IDE settings by yagu · · Score: 1

    This incompatibility would not be a surprise if Microsoft's default settings for Visual Studio .NET are the same as last time I used it. It has been a while since I worked on a .NET project, so I don't if Microsoft has "fixed" this, but I'm guessing not.

    It's an effective approach by Microsoft.... We discovered almost immediately incompatibilities with .NET code/projects and Mozilla, but even after admonishing team members to ensure their settings were appropriate to create Mozilla compatible code, we would find settings not set appropriately, and features in our application not working in Mozilla. Finally, higher management (already a bit Microsoft-centric) waved their hands (funny how they get that kind of power) and deemed by fiat it no longer necessary to have a Mozilla compatible app. Wow!

    Any other developers out there have any similar experiences?

    1. Re:careful with IDE settings by Anonymous Coward · · Score: 0

      Could it be related to this problem (and fix)...?

      http://www.garykeith.com/browsers/index.asp

  58. Official UK lottery site does work with Moz/FF... by rklrkl · · Score: 1

    Actually the official UK lottery site has allowed Firefox/Mozilla into its online registration/play for a few months now, but this is after *years* of only supporting a weird set of browsers (IE, AOL and, er, Netscape 7?), despite numerous phone call and e-mail complaints from me and other users. Luckily, their latest design has finally allowed the Bugzilla bug (226258) on this issue to be closed.

  59. I'm an ass by glsunder · · Score: 1

    I write the companies website & intranet for firefox, then force my users to only use IE.

    Next, I'll force them into IMAP and make them use OE.

  60. Lucky For Me by SomeOtherGuy · · Score: 1

    it is the 10% that I don't care about. I can live with only being able to use 90% of the InterWeb.

    --
    (+1 Funny) only if I laugh out loud.
  61. Dodgy statistics by JaF893 · · Score: 1

    So someone did a survey of 100 websites and ten didn't work with Firefox. That doesn't mean that 10% of all UK websites don't work in Firefox does it? If I look out the window and see 3 blue cars and 2 red cars does that mean that 60% of cars are blue?

  62. Here's even an excerpt by Psychic+Burrito · · Score: 4, Informative

    I couldn't believe that, but look at this exerpt of the book (pdf).

    On page 19, the author actually says:
    In my view, you should design Web pages for Internet
    Explorer (IE) version 6 running on a typical 17'' monitor. Why? Here are the reasons:
    -more than 95 percent of the people visiting your Web site use IE 6.
    -You can take advantage of lots of cool effects that work only in IE or IE 6. Your job is much easier if you're designing for a predictable, stable canvas.


    It's extremely stupid to give such an advice. I suggest that people email either the author, Richard Mansfield or the publisher, Wiley.

    1. Re:Here's even an excerpt by tunnie · · Score: 2, Funny
      [...] lots of cool effects that work only in IE or IE 6
      What, like these?
    2. Re:Here's even an excerpt by poot_rootbeer · · Score: 1

      In my view, you should design Web pages for Internet Explorer (IE) version 6 running on a typical 17'' monitor.

      Okay... but what resolution is that "typical 17'' monitor" running at?

      Back when I was stuck with a puny 17-incher, I used to run at 1024x768, but I had good eyesight. Other users may be more comfortable at 800x600 or even 640x480. Screen size is pretty much irrelevant to web design.

    3. Re:Here's even an excerpt by Anonymous Coward · · Score: 1, Insightful

      It also makes you 5% poorer, if the job of the website is to make money. And who doesn't want to make 5% less money.

    4. Re:Here's even an excerpt by fermion · · Score: 2, Insightful

      The 17" monitor is what really identifies the author as a idiot. This is a constraint that is unneccesary. I mean, do we design cars only for people 5'10". Well, in American and Japan they do, which is one reason so many people still buy from Germany. The Japanese has the sales to handle it, but the American car market continues to suffer from lack of creativity.

      --
      "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    5. Re:Here's even an excerpt by Anonymous Coward · · Score: 0

      Other users may be more comfortable at 800x600 or even 640x480.

      Actually, less than 0.5% of the users out there will look at a given site at 640x480 resolution. I do design my sites to handle this resolution (with the exception of Dillo, which has completely broken table layout, and is used by less than .01% of the web browsing public), but it's essentially a non-issue.

      800x600, however, is viewed by about 30% of the web browsing public, and a web site needs to work at this resolution.

    6. Re:Here's even an excerpt by indiechild · · Score: 1

      The book even goes into MS' proprietary Internet Explorer "filters".

      Jesus Christ, what kind of fucking idiotic "webdesigner" could write a book like this? He should hang his head in shame.

  63. Opera by Anonymous Coward · · Score: 0

    Look out for all the opera users! Internet Explorer actually has only 10%...

  64. I could only imagine the content from this 10% by Austin+Milbarge · · Score: 1

    I'll bet these sites contain 100 different scripts, languages, Java applets and flash and shockwave advertisements, utilizing every ML language ever invented and getting it all to work on one page! Enough crap to slow down your computer and cause the router at your ISP to melt. In other words, CORPORATE WEB JUNK! No thanks, I'll stick with the other 90%.

  65. Browser features, perhaps by SkiifGeek · · Score: 1

    If I Remember Correctly, the new flavour of the month on the Internet, XMLHttpRequest, was an Internet Explorer only feature, until it was copied by the other browsers for eventual integration with their own codebases. And, as you brought up, there are differences in rendering and transitions between the browser types, so I dare say that the browser unique features would account for a fair portion.

    The remainder, I would guess, are sites that require an Active X control, have poor DOM checking / browser sniffing in place, rely upon non-standard coding, or are dead sites that are no longer being maintained, and are a fallback to the late 90s.

    Personally, I feel that a 10% failure rate is pretty good, actually, that was the level that the UK Government was aiming for with their recent EDS / Pension debacle (where they encountered around 20% failure).

  66. Mods, the parent is a troll by Anonymous Coward · · Score: 2, Informative

    Even though he sais he is a die hard firefox user, he is a troll. The link he has provided is a link to the ACID 2 test. Which is recent, not rudimentary at all, and when it was released a couple months ago, no browser was capable to pass.

    Now, Safari and Konqueror are able to pass that test, but it has taken a month to port Safari patches to Konqueror.

    Imprementing the ACID2 bugfixes for Firefox from scratch is bound to take more than a month. The question is: How much is going to take IE6 to be ACID2 compliant?

    1. Re:Mods, the parent is a troll by masklinn · · Score: 1
      Currently, 3 browsers pass Acid2 (not the original Acid test): Safari (first to), Konqueror and iCab3, 2 of which are avaible only on Macintosh and one on *nix platforms.

      However none of the Acid2 compliant browsers are in a release state, only development versions pass Acid2.

      Firefox devs don't seem to be too concerned with Acid2 right now because they feel that their other problems with Gecko 1.8 are much more important, Acid2 won't be seriously worked on until Gecko 1.9 development starts (~Firefox 1.1 release)

      Acid2 support is being worked on at Opera, you can find the dev's progress posted from time to time on their forums, and Opera Software intends to implement full CSS2.1 in their handled version as soon as the main one will be Acid2 compliant.

      Meanwhile we've learnt that MSIE7 will have no less than 4 CSS1 bugfixes (whoa), no word on Acid2/CSS2.1 compliance... and they try to teach us how to make crappy bloated table-based rounded corners instead...

      sooo
      The question is: How much is going to take IE6 to be ACID2 compliant?
      Probably until Sam's project succeeds
      The question is: How much is going to take IE7 to be ACID2 compliant?
      See above
      The question is: How much is going to take IE8 to be ACID2 compliant?
      See above
      --
      "The way we can tell it's C# instead of Haskell is because it's nine lines instead of two." -- wadler
  67. try this for browser detection by ajs318 · · Score: 1

    <?
    if (preg_match("/msie/i", ($browser = $_ENV["HTTP_USER_AGENT"]))
    && !preg_match("/opera/i", $browser)) {
    # MSIE-specific code
    }
    elseif (preg_match("/opera/i", $browser)) {
    # Opera-specific code
    }
    elseif (preg_match("/lynx/i", $browser)) {
    # Lynx-specific code
    }
    elseif (preg_match("/links/i", $browser)) {
    # Links-specific code
    }
    elseif (preg_match("/konqueror/i", $browser)) {
    # Konqueror-specific code
    }
    elseif (preg_match("/googlebot/i", $browser)) {
    # whatever you want to see listed for your site on Google .....
    }
    else {
    # standards-compliant code
    };
    ?>

    --
    Je fume. Tu fumes. Nous fûmes!
    1. Re:try this for browser detection by imgumbydammit · · Score: 0

      Speaking of standards, you should avoid using the short open tags in php. You'll find that when you switch to XHTML that php will get confused between the xml markup and the php code.

      --
      That's right: I'm gumby dammit.
  68. 99% of All Sites Incompatible with Lynx by ehaggis · · Score: 1

    A recent survey has indicated a staggering conspiracy afoot to oust the Lynx browser as a contender in the browser wars. "They web site designers add all kinds of non standard things like pictures, tables, sounds. It's an obvious ploy to unseat us as the rightful heirs to the internet."

    --
    One ring to bind them - should probably have more fiber and less rings in their diet.
    1. Re:99% of All Sites Incompatible with Lynx by Anonymous Coward · · Score: 1, Informative

      A bigger (and more real) problem than you think. Accessibility should have ALT tags and how can a screenscraper turn your flash page into text for ingestion into text-to-speech?

      You should be able to get all reasonable content from a text-only browser for your site.

  69. Damnit U.K. by Excelsior · · Score: 1

    ten percent of UK websites alienate Firefox users.

    Damnit, first a huge tax on tea, and now this.

  70. Sarcasm, People! by sweetnjguy29 · · Score: 1

    Arg! The original post was supposed to be funny!! I got a good laugh out of seeing it get mod'ed as informative.

    But seriously...the point was...how can you say 10% of consumer websites are not firefox friendly if you only test 100 websites??? I am sure the UK has more than 100 consumer websites. And for the record...100 is a piss poor sample size for any study. Do they even define what a consumer website is?

    From my own anecdotal experience, I only have problems with about 1 webpage not displaying properly every week that I visit while using firefox. That website is usually Slate, a Microsoft site.

    Any company that writes code to specifically cater to only one browser is shortsighted and not business savy. As the study suggests, companies should wake up and smell the coffee. (no, that was not a Java joke...)

    1. Re:Sarcasm, People! by ralmeida · · Score: 1

      But seriously...the point was...how can you say 10% of consumer websites are not firefox friendly if you only test 100 websites??? I am sure the UK has more than 100 consumer websites.

      Because there's not much variability between the websites and 100 is a representative sample?

      From my own anecdotal experience, I only have problems with about 1 webpage not displaying properly every week that I visit while using firefox.

      And we all know that anecdotal experience can be extrapolated to general behavior...

      --
      This space left intentionally blank.
    2. Re:Sarcasm, People! by djmurdoch · · Score: 1

      Arg! The original post was supposed to be funny!! I got a good laugh out of seeing it get mod'ed as informative.

      I didn't think it was funny, you insensitive clod.

  71. Re:Ignorance, Laziness, and Microsoft Sabotage by Anonymous Coward · · Score: 0

    For an example of ignorance and laziness at work, see the post titled "It's just business" by Anonymous Brave Guy, above.

    His argument, that it's just business, has been used to justify immoral and lazy actions by weak, incompetent, and/or greedy followers, throughout history.

    And in this case, his argument isn't even true, as shown by the many excellent and successful standards-compliant websites on the Net.

  72. Flash, Too by SEWilco · · Score: 1

    Those sites which require Flash alienate me also. They make me flash over to the next site which provides the same service.

  73. I love it..... by burdicda · · Score: 1

    I always check their web site first before making
    that vital million dollar govt purchase decision
    so keep it up ie assholes.....

    I use only Firefox....
    Can't buy what you can't order.....LOL

  74. odeon.co.uk by matt+me · · Score: 2, Interesting

    Even when I still used IE and Windows, I always went straight for the "text-only film times" page on the Odeon site. So much quicker to load, and I don't have to select where my cinema on a map, just scroll down to O(xford). I don't care about pretty pictures. 90% of the content I want should be found in one click. Oh yeah, and in the words of the W3C tips, don't say click, cos not everyone will be clicking. I use lynx when I get sick of the web.

  75. Active X controls by DeadSea · · Score: 1

    Having never developed sites for IE, I'm not sure what active X can do. What features can you implement using active X that are so much harder, or impossible to implement using javascript?

    1. Re:Active X controls by Anonymous Coward · · Score: 0

      ActiveX is a native Win32 application running in the browser. That should give you some idea of what ActiveX can do that JS cannot (and also why it is not portable).

    2. Re:Active X controls by Anonymous Coward · · Score: 0

      Flash is cross-platform unlike most ActiveX controls.

    3. Re:Active X controls by Anonymous Coward · · Score: 0

      An ActiveX control can do anything a normal Windows application can do, including writing to the hard drive, installing device drivers, patching software (including MSIE) in memory, or even overclocking your video card. Even if you could get ActiveX mostly working in Firefox, you would still have problems with ActiveX controls that rely on in-memory patching of the browser, device drivers, or other dirty tricks that won't work except on certain versions of MSIE and Windows. Even applying a security patch can break some ActiveX controls because the code offsets will change.

  76. MOD PARENT INSIGHTFUL! by Spy+der+Mann · · Score: 1

    because whoever made the page didn't know what in the hell they were doing.

    You're ABSOLUTELY RIGHT. Check out this daily WTF:

    The great pyramids of DIV

    Warning: Don't scroll too fast. Might cause motion sickness.

  77. IE has huge rendering issues... by Kjella · · Score: 2, Informative
    ...at least if you use CSS layout, and IMO XHTML/CSS is the way to go.

    1. Every CSS box needs to be duplicated, to fix IE's flawed box rendering model.
    div id=foo
    div id=foo-design
    ../div
    /div
    2. IE can't handle objects close to a float
    div id=floatright
    (...)
    /div
    div id=imagemap
    img src="...-full"
    /div
    must become
    div id=floatright
    (...)
    /div
    div id=imagemap+image_as_background
    img src="...-cut"
    /div
    so the cut image doesn't come close to the edge.

    3. If you ever adjust the width of a div tag which has floats either left or right, you will have a world of hurt.

    4. If any object inside a CSS is bigger than the CSS, IE will override your settings unexplainably overriding even a fixed pixel width.

    That is just some of the major annoyances I've had in recent weeks. I could go on and on. IE6 is so flawed, everything needs to be tweaked. On the bright side, the solution almost never breaks Opera/Firefox. But making a modern site that renders well in IE is a huge PITA.

    Kjella
    --
    Live today, because you never know what tomorrow brings
  78. Incompatible? Go to a competitor. by Animats · · Score: 3, Insightful

    I encounter incompatible sites now and then. But so far, I haven't found an incompatible site that didn't have a compatible competitor. So what if "Weather.com" goes into an infinite redirect loop? There's Yahoo Weather.

    1. Re:Incompatible? Go to a competitor. by julesh · · Score: 1

      I encounter incompatible sites now and then. But so far, I haven't found an incompatible site that didn't have a compatible competitor. So what if "Weather.com" goes into an infinite redirect loop? There's Yahoo Weather.

      At least one of the sites on their list is a government site. Can you recommend a competing government to me? I don't know of any locally... ;)

    2. Re:Incompatible? Go to a competitor. by gilgongo · · Score: 1

      Here's a mail I've just sent to info@odeon.com:

      I am trying to access your website using Firefox. It doesn't work.

      I see that www.ugccinemas.co.uk works fine. So I've just booked four tickets to see Sin City tomorrow night.

      If your website worked, you'd have got my money.

      Make your website work with Firefox!

      --
      "And the meaning of words; when they cease to function; when will it start worrying you?"
  79. kick them off the 'net by Anonymous Coward · · Score: 0

    Web sites that fail to conform to w3 standards should be kicked off the 'net. You can't have a car that doesn't meet highway traffic standards, and there are similar public standards for aircraft and rail. If a web site fails to follow w3 standards, they should be kicked off the 'net. It's shape up or ship out time. Similarly, if Microsoft decides that they don't want to conform to w3 standards, they can sell their product on their own internet, and leave the world wide one alone. Shape up or ship out!

  80. Photo Transitions by Lagged2Death · · Score: 2, Informative

    They can be done under Mozilla/Firefox with a bit of Javascript, I beleive.

    And personally, I think style issues like these are better handled by scripts or other non-browser-specific systems. Styles change, and it would be just as well to avoid changing the browser for every little whim of fashion.

    1. Re:Photo Transitions by aztracker1 · · Score: 1

      it is a browser-specific script.. it just hides it... try the same page in opera and in ie.. opera (using 7.54 here) and ie don't show it properly...

      True: scripting can overcome most browser specific issues, but things like this are mostly done in a method that is outside w3c dom + ecmascript specifications.

      True: most advanced features can be implimented in a browser agnostic fashion, and can be implimented with script + html + css/style alone.

      False: all these sites that don't follow standards are just being difficult.

      Many intranet/extranet sites that require IE only where started when there were *NOT* comparable technologies that were implimented... AJAX was a really difficult thing to do in a browser agnostic way back when the version 4 browsers had come out, IE was way ahead as far as building usefull web based applications. The IE object model, though a little flawed was leaps and bounds better than the Netscape Layers system.

      A lot of these applications are > 4 years in their origins, and in 1999-2000 there wasn't a good level of cross-platform compatibility within browsers as a standard. (About the only thing that irks me today, is that the byte-order for integers in JS is based on the platform, not consistant like Java or .Net, which is rarely an issue, but comes up if you want to impliment hashing, or flags in JS...)

      Anything fairly new, there is little or no reason to *not* work in Firefox, IE, and Opera (being the big browsers, firefox including other mozilla/gecko variants) ... personally, would love to see an XUL addon for IE, as well as Opera embracing the standard.

      --
      Michael J. Ryan - tracker1.info
    2. Re:Photo Transitions by aztracker1 · · Score: 1

      looks like it does work under opera 8 (just upgraded), though it doesn't actually do the transition, but the pause makes it seem like it's still doing the transition calculations before changing the picture.. not sure if it is an opera thing, looking at the script, seems to call a specific Moz.. property, which may be gecko specific, and not blow up in opera, but still not quite right..

      --
      Michael J. Ryan - tracker1.info
  81. Great headline by Anonymous Coward · · Score: 0

    "10 Percent of UK Sites Incompatible with Firefox"

    as opposed to....

    "Firefox incompatible with 10 Percent of UK Sites"

    The first thing I think of is "Those UK webmasters had better fix their sites to work with Firefox, because Firefox can't have any bugs in it!" /rant

  82. NatWest Online Banking however... by Cybertect · · Score: 1

    will *only* work with Firefox if you're running Mac OS X - they've dropped support for the (now defunct) IE 5.x for Mac and they don't support Safari. https://www.nwolb.com/secure/denial.asp?reason=v4 Service Denied: Reason: Unsupported Browser The version of the internet browser you are using is not supported by NatWest OnLine Banking. Please use one of the following browsers: Internet Explorer Version 5.00 and up (Windows only) Netscape Navigator 7.1 and 7.2 Firefox 1.0 Mozilla 1.5 and up AOL 6.0 and up (Windows only/AOL subscribers only) Apple Macintosh users who currently have OS v 8.0 or OS v 9.0 installed will require IE v 5.1.7 or Mozilla v 1.2.1

  83. However ... by Wordsmith · · Score: 1

    However, they were just fine with Firefoux.

  84. Hobson's Choice by cocoamix · · Score: 1

    You really can use any browser for these sites.

    It's just depends on what your dfinition os "use" is.

    Getting dead link even counts as use. You're just limited to their 404 page.

  85. or look at it the other way - 90 percent fixed by ray-auch · · Score: 1

    Firefox has been at v1 for only a few months, and there were rendering/standards issues with earlier versions - you were much more trying to hit a moving target.

    So, what we are really saying is that within about 6 months of Firefox release, 90% of sites have been updated to work with it.

    Seems to me that is a pretty good record.

    [ and yes I do know you can design you sites to "standards" rather than browsers, I also know how much still goes wrong, in even the most recent browsers, when you do ]

  86. Travelocity by Anonymous Coward · · Score: 0

    There are some "features" on Travelocity I can not get to work, such as booking a flight. Since I am such a lsave to travelocity, I log in to Windows just to search for flights. So sad.

  87. Is that actually an important statistic? by clk23 · · Score: 1

    I think it would be much more worthwhile and relevant for BBC to cite a study on the percentage of websites which alienates individuals with disabilities. I am guessing that number would be a bit larger than 10%.

  88. What a shame by Anonymous Coward · · Score: 0

    Firefox users tend to be the more tech-savvy and tech-aware members of our society. We are the people that other Internet users come to for advice. If Firefox users can't get to your site, we can't give good (or bad) advice on it and will send someone to another, Firefox-compatable, site instead. You may have the best product and price anywhere, but if we can't see it we can't recommend it. I wonder how much business is lost due to incompatable sites?

  89. If Opera switched to default to Firefox, not IE by WillAffleckUW · · Score: 1

    then those 10 percent of websites would be forced to switch, as the number would shift from 8 percent of all web browsers to 15 percent of all web browsers in the UK.

    --
    -- Tigger warning: This post may contain tiggers! --
  90. headline should read by hammeredpeon · · Score: 1

    10% of UK businesses don't want my business.

    --
    best college pickem site ever: pickem.terrbear.org
  91. sites rewritten anyway by GunFodder · · Score: 1

    Businesses make a profit by keeping their customers happy. There are literally millions of potential customers out there that are not using IE. Implementing new web sites that work in most browsers isn't rocket science. And most companies end up redoing their websites every couple of years anyway. So why bother hacking up Firefox when a little advocacy could take care of the problem?

  92. Um.. so? by Guppy06 · · Score: 1

    10% of the websites out there are inaccessable to 10% of the browsers? Even assuming that every website is visited equally, that still leaves us with a problem that only affects 10% * 10% = 1% of the people out there.

    Odds are, the sites that are incompatible with Firefox aren't heavily visited, anyway.

  93. Make that 99% incompatable web for South Korea by oktokie · · Score: 1

    Make that 99% incompatable web for South Korea.

    They often have established news sites and large portals and banks installing Korean version of gator with utility install which is must in order to do online banking reading news and checking free mails...

    It's a true example of security by obsecurity.

    ()()
    (@@)
    oktokie

  94. Alternative to Jobcentreplus.gov.uk by Tyrathect · · Score: 1

    "Websites that proved difficult for Firefox users to navigate included the government website Jobcentreplus.gov.uk ..."

    It's buried away in the FAQ, but "you can also search the Jobcentre Plus jobs database by visiting http://www.worktrain.gov.uk/", which does work with FireFox.

    It's not perfect. There are too many pages before you get to results, they don't make logging in very easy and it doesn't handle having multiple tabs open well, but it's better than the Jobcentreplus.gov.uk site and seems to find more relevant results.

    Having said that I still seem to find more jobs I want to apply for on http://www.jobsite.co.uk/ than any other site.

    --
    "They just use your mind and they never give you credit"
  95. It depends on who your visitors are by houghi · · Score: 1

    If you make a website with pictures of your cat intended to show to your grandmother who only uses IE. Not a real issue.

    If it is a site to do your online banking, then the problem is huge as they shut out a lot of their customers.

    Sometimes just removing the test of what browser you have is enough to get it working.

    --
    Don't fight for your country, if your country does not fight for you.
  96. Microsoft Astroturfers Trying to Hide the Truth by Anonymous Coward · · Score: 0

    I see that my parent post has been modded down to "-1".

    I consider that to be an abuse of the moderation system.

    Of course, I have gotten used to such abuses on Slashdot recently. There are too many astroturfers on the site, manipulating the moderation system. As a result, it has become very difficult to point out the truth about Microsoft without having your post hidden from view.

    The honest moderators, unlike the astroturfers, know that posts like the parent do not belong down with the GNAAs and First Posts.

    The parent post is not rude, nor is it a troll. It is on topic, it is making a valid point, and it is stating the truth. Furthermore, it provides links and quotes to back up the points made.

    I guess the truth no longer counts on Slashdot.

  97. It works in Opera by JimTheta · · Score: 1

    I just tried it in Opera. Looks like it works. I only mention this because of the recent Opera story in which a bunch of posters said "Who cares about Opera. FF is free and good enough!"

  98. They all work in Opera by JimTheta · · Score: 1

    There was some Opera bashing in a recent story. But all of these problem sites render fine in Opera.

    That doesn't excuse them from being non-compliant, but it does illustrate why some people may like Opera over FF.

  99. Good news!!! by Tharald · · Score: 1

    As firefox is closing in on 10% now, this is good news. These companies are shutting out 10% of their customer base. In any competitive environment, this is gonna be too big a disadvantage to compete successfully, and the companies will die. It is amazing how the free market economy and Darwin's theory of evolution correlate.

  100. Re:90% of sites = not good enough by JoeCommodore · · Score: 1
    If it was Microsoft talking they would blast 10 percent of sites that didn't work with MSIE. As long as you use your argument people will *think they need* MSIE, as long as I use mine people will know better.

    It's all a matter of perspective, and mine isn't an MS only one.

    --
    "Enjoy what you're doing! If it becomes drudgery, you're doing it wrong!" - Jim Butterfield
  101. Code for the w3c standards by Anonymous Coward · · Score: 0

    Everytime I code a web application or website I always follow the w3c webstandards and make sure my website validates to valid HTML or XHTML.

    Sometimes if I see a website that dont follow standards (you can easy see if no doctype) then I email them and inform them.

    I think that it is important that we all follow the webstandards and not just code and hope that it works.

    I have begin to use XHTML alot lately and in conjuction with CSS and it works great and looks lovely. I never use JavaScript, Java, Shockwave or Flash!