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.'"

25 of 340 comments (clear)

  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 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)
    2. 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
  2. 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.

  3. 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.

  4. 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 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.

    3. Re:It's just business by fr0dicus · · Score: 2, Insightful

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

  5. 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
  6. 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

  7. 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.

  8. 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)"

  9. 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.

  10. 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 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!
  11. 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.
  12. 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
  13. 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
  14. 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.

  15. 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!

  16. 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.

  17. 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.

  18. 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.

  19. 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