Slashdot Mirror


Firefox 3.5 Hits Release Candidate Milestone

macupdate writes "Firefox 3.5rc1 has started trickling to users (mirrors and appropriate pages should all be updated soon). You can read the release notes. RC1 still scores a 93/100 on the Acid3 test."

202 comments

  1. A little anti clamantic... by SchizoStatic · · Score: 1

    Since chrome did 100/100 and its "beta"

    --
    https://www.speakservers.com/
    1. Re:A little anti clamantic... by samexner · · Score: 1

      Midori got 100/100 too.

    2. Re:A little anti clamantic... by snl2587 · · Score: 1

      And both the latest Opera and Safari 4 already score 100/100...

    3. Re:A little anti clamantic... by Yvan256 · · Score: 3, Funny

      To be fair, Chrome is from Google. It's going to be beta for another three years.

    4. Re:A little anti clamantic... by Anonymous Coward · · Score: 0

      You're right. We need an iPhone plug to punch this up.

      "Mozilla shuns iPhone users with Firefox 3.5RC1"

      or

      "Firefox 3.5RC1 Released for the iPhone!"

      I don't know if it runs on the iPhone or not. The beauty of it is: it doesn't matter. Now you've got yourself a bonafide news article; Acid or no Acid.

    5. Re:A little anti clamantic... by kaaposc · · Score: 1, Informative

      just three? Gmail is beta for already five years..

    6. Re:A little anti clamantic... by ArsonSmith · · Score: 4, Insightful

      yet don't work 100% in real world webpages. Standards compliant be damned if you can't render real pages.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    7. Re:A little anti clamantic... by Zarel · · Score: 1, Redundant

      To be fair, Chrome is from Google. It's going to be beta for another three years.

      What are you talking about? Google Chrome has been stable since December 2008, and Chrome 2 has been stable since mid-May (and scores 100/100 on Acid3).

      --
      Want a high quality FOSS RTS game? Try Warzone 2100!
    8. Re:A little anti clamantic... by Just+Some+Guy · · Score: 3, Insightful

      Such as...? I use Safari (at home) and Konqueror (at work) nearly exclusively and haven't had problems with these mythical IE-and-Firefox-only pages.

      --
      Dewey, what part of this looks like authorities should be involved?
    9. Re:A little anti clamantic... by snl2587 · · Score: 1

      Standards compliant be damned if you can't render real pages.

      I think that's the crux of the problem. If both the pages and browser were standards compliant this wouldn't be an issue, but alas, neither truly are. Especially the pages.

    10. Re:A little anti clamantic... by Hangin10 · · Score: 1

      Gmail is stable too, and STILL has the little "BETA" tag on it.

    11. Re:A little anti clamantic... by Freetardo+Jones · · Score: 1

      Something being beta doesn't necessarily imply that it's not stable. Beta just means it's a pre-release version.

    12. Re:A little anti clamantic... by Enleth · · Score: 2, Interesting

      That's interesting. Which version of Konq? On 3.5.10, the Slashdot discussion system is FUBAR for a few weeks now. It was working fine, in-place replies, dynamic comment loading and all, but it stopped at some point.

      --
      This is Slashdot. Common sense is futile. You will be modded down.
    13. Re:A little anti clamantic... by A12m0v · · Score: 2, Informative

      Every WebKit browser should be getting 100/100.

      --
      GENERATION 25: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    14. Re:A little anti clamantic... by Anonymous Coward · · Score: 0

      I've had problems with Firefox ever since Slashdot added in the thick border to the left of people's comments for no appreciable reason.

      Slashdot's Javascript has never been anything but appalling however. The programmers should go and buy a book on data structures and algorithms. No excuse for multi-second browser pauses because of poor algorithm choice.

    15. Re:A little anti clamantic... by master5o1 · · Score: 1

      However, the parent is saying that the version that has scored 100/100 in the Acid3 test is the version that has no beta tag. There still may be a beta-tagged Chrome version, but it is not the only Chrome version to have a 100/100 score in the Acid3 test.

      --
      signature is pants
    16. Re:A little anti clamantic... by Just+Some+Guy · · Score: 4, Informative

      4.2.something. The only problem I have is that /. changed their CSS in the last couple of days so that now the message header sometimes fills the whole screen and pushes the message text against the far right edge.

      --
      Dewey, what part of this looks like authorities should be involved?
    17. Re:A little anti clamantic... by MrHanky · · Score: 1

      Konqueror 4.2.4 seems to work well enough with Slashdot. It's actually a fairly decent browser, although I use Iceweasel out of habit (and ABP+ and NoScript). The only site I have found it doesn't work properly with is Gmail. It scores better than Firefox and Iceweasel on Futuremark's Peacekeeper benchmark, but feels a bit slower in reality.

      I'm posting from it now, mostly to test it with Slashdot, and everything from logging in to using the slider thingy, previewing, continuing editing and posting (hopefully) seems to work.

      Also, when Slashdot suddenly stops working with something, it's most likely Slashdot's fault.

    18. Re:A little anti clamantic... by Goaway · · Score: 1

      The few times I've encountered this problem in the last year or so, it has been in Firefox, and Safari has worked fine.

    19. Re:A little anti clamantic... by Goaway · · Score: 1

      And Chrome doesn't.

    20. Re:A little anti clamantic... by Enleth · · Score: 1

      Oh, well. They must've fixed something important in 4.x. Well, good to know. Even though I'm not switching to KDE4, still no OS X xtyle menus there...

      --
      This is Slashdot. Common sense is futile. You will be modded down.
    21. Re:A little anti clamantic... by Anonymous Coward · · Score: 0

      And Chrome doesn't.

      No, Chrome didn't. It's back in beta.

      But I'm glad it got burned. Think of all the things we learned for the people who are still alive.

    22. Re:A little anti clamantic... by alexborges · · Score: 1

      No "extra" browser will ever be accepted by apple in the store. Period.

      --
      NO SIG
    23. Re:A little anti clamantic... by M3rk1n_Muffl3y · · Score: 1

      right

      --
      This is not the sig you are looking for...
    24. Re:A little anti clamantic... by selven · · Score: 1

      That's for windows. The linux version is in the "developer" stage (it's like alpha, but it has some marketing twist to suggest that you're part of some clique of "developers" allowed to see this early version).

    25. Re:A little anti clamantic... by Dr.Fujitronic · · Score: 1

      Do you use big screen letters? I encountered the same odd behavior. Try to shrink the lettersize a bit, (ctrl+minus key) the layout propably goes back to normal, at least it worked for me.

    26. Re:A little anti clamantic... by SydShamino · · Score: 2, Interesting

      The amusing part is that, on my screen, your post looks exactly as you describe.

      I've found the problem goes away if I increase the window width sufficiently.

      I'm running Firefox 3.0.11 on Windows XP, but I see the same problem on Firefox 3.0.? on MacOS Leopard at home.

      --
      It doesn't hurt to be nice.
    27. Re:A little anti clamantic... by atamido · · Score: 1

      Heh, the same for me. His post was squished up against the right.

    28. Re:A little anti clamantic... by Anonymous Coward · · Score: 1

      Subject: A little anti clamantic...

      Anti... loud?

      (When you make a mistake in a Subject, every reply rubs it in.)

    29. Re:A little anti clamantic... by Goaway · · Score: 1

      Just like Firefox is "back in beta". Come on, that's a ridiculous thing to say.

    30. Re:A little anti clamantic... by Anonymous Coward · · Score: 0

      So we have to wait until Clamantic Capybara for Ubuntu to include an Acid 3 compliant Firefox in its release?

      :(

    31. Re:A little anti clamantic... by Brad1138 · · Score: 2

      and Konqueror (at work)

      You are the first person I have ever heard say "I use Konqueror", I didn't think anyone used it. I figured it was some throw back browser that was still included in Linux distros for nostalgic reasons. What does it do for you that Safari or FF wouldn't/doesn't do?

      --
      If you could reason with religious people, there would be no religious people
    32. Re:A little anti clamantic... by Anonymous Coward · · Score: 2, Funny

      And for those who still don't get it, the correct spelling is "anticlimactic".

      It's from "anticlimax".

      You know what a climax is, right? This is slashdot; you've surely read about them, even experienced them by yourself.

    33. Re:A little anti clamantic... by complete+loony · · Score: 1

      Yeah, but I've been seeing that in Firefox 3.5 as well.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    34. Re:A little anti clamantic... by PuercoPop · · Score: 3, Informative

      Don't hog all my memory. Konqueror 4.x broke Slashdot and digg so I had to stop using it and use firefox instad. But now Slashdot works properly again. I can use dig but I get a regexp exhaust error if I try to login in digg. I still have to use firefox for gmail and facebook though.

    35. Re:A little anti clamantic... by dudpixel · · Score: 2, Insightful

      yet don't work 100% in real world webpages. Standards compliant be damned if you can't render real pages.

      What?

      If the browser follows web standards 100% and yet some webpages render incorrectly - doesn't this mean the issue is with the web page and not with the browser?

      Web standards exist so that we shouldn't have to answer the question of whether the web browser is designed for the web pages or whether the web pages are designed for the browser.

      --
      This seemed like a reasonable sig at the time.
    36. Re:A little anti clamantic... by Just+Some+Guy · · Score: 1

      Nope. Maximizing and restoring the window seems to temporarily fix it, though.

      --
      Dewey, what part of this looks like authorities should be involved?
    37. Re:A little anti clamantic... by zobier · · Score: 1

      They have
      ul#commentlisting.d2 div.full div.commentBody {
          clear:none;
      }

      in their CSS, it should be clear: both; which I tried in FireBug and can confirm works.

      --
      Me lost me cookie at the disco.
    38. Re:A little anti clamantic... by miceuz · · Score: 1

      don't you all know already that "BETA" is a new very popular cliche that means product is new innovative and fun to use and as soon as it gets out of the beta it becomes old boring stagnating crap?

    39. Re:A little anti clamantic... by tyrione · · Score: 1

      Oh, well. They must've fixed something important in 4.x. Well, good to know. Even though I'm not switching to KDE4, still no OS X xtyle menus there...

      It's called merging parts of WebKit into Kdelibs.

    40. Re:A little anti clamantic... by Just+Some+Guy · · Score: 1

      It "feels" faster on my machine. It's better integrated with my KDE desktop. It uses KWallet to store passwords. It uses a lot less memory. It loads instantly. I have nothing against Firefox and use it for web development because of the nice plugins, but I slightly prefer Konqueror for daily browsing.

      --
      Dewey, what part of this looks like authorities should be involved?
    41. Re:A little anti clamantic... by plague3106 · · Score: 1

      If the browser follows web standards 100% and yet some webpages render incorrectly - doesn't this mean the issue is with the web page and not with the browser?

      And as an end user, I don't give a shit. If it renders fine in IE and not in Safari, I'll use IE. The site is more important than the browser.

    42. Re:A little anti clamantic... by Burz · · Score: 1

      eBay barely works in Firefox if you're a Seller. And even then, some nice features will be missing or broken (in-browser image editing, and certain Paypal-based label printing functions -- the ones that use a combination of Java and embedded PDF, ironically).

      OTOH, now that Macs have a much larger market share, and Chrome is out there too, maybe it is time for Mozilla to push the 100% standards compliant agenda (instead of the wannabe-IE-compatible one). All together, these browsers should get the laggard web developers to wake up.

    43. Re:A little anti clamantic... by Anonymous Coward · · Score: 0

      Personally, I like having one app that handles both web browsing and file management

    44. Re:A little anti clamantic... by Randle_Revar · · Score: 1

      Plenty of people on Planet KDE use Konq. KHTML is not up to Gecko or WebKit standards, but it is still rather good. And Konq has the advantage fully integrating with KDE.

    45. Re:A little anti clamantic... by ArsonSmith · · Score: 1

      If all roads were perfectly smooth we wouldn't need suspensions in our cars.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    46. Re:A little anti clamantic... by jZnat · · Score: 1

      WebKit is based on KHTML. KDE adds patches back from WebKit when they can, but they're not that different when it comes to web standards and performance.

      --
      'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
  2. Beta "99" by xigxag · · Score: 2, Insightful
    --
    There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
    1. Re:Beta "99" by Freetardo+Jones · · Score: 5, Informative

      That's the old preview build. This is the RC link.

    2. Re:Beta "99" by David+Gerard · · Score: 3, Informative

      This is actually the one after that - I had 3.5b4, got 3.5b99 last week and "3.5" today. The user agent string is:

      Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1) Gecko/20090615 Firefox/3.5

      (yes, this is the NT laptop - haven't checked Karmic yet)

      --
      http://rocknerd.co.uk
    3. Re:Beta "99" by neiby · · Score: 2, Informative

      That's incorrect. That is the Release Notes page for the RC, but the download link (mislabeled) actually leads you to Beta 4, which obviously predates Beta 99. If you install Beta 4 after Beta 99, you'll corrupt some files that you'll need to delete manually afterward. I learned this the hard way today. If you already have Beta 99, just check for updates from within the browser.

    4. Re:Beta "99" by Matt+Perry · · Score: 1

      That still links to the beta 4 download.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    5. Re:Beta "99" by Anonymous Coward · · Score: 0

      that still only offers the beta 4 release. i found i had to go elsewhere to download the release candidate directly.
      like...http://www.filehippo.com/download_firefox/

    6. Re:Beta "99" by Anonymous Coward · · Score: 0

      (yes, this is the NT laptop - haven't checked Karmic yet)

      You don't have to justify yourself. Windows is a very respectable OS nowadays. On the other hand, that Karmic Linux you seem to be using is insecure by default. Better not to use it at all.

    7. Re:Beta "99" by Anonymous Coward · · Score: 0

      here is the link to download Firefox RC1 for English (British)

      http://download.mozilla.org/?product=firefox-3.5rc1&os=win&lang=en-GB

    8. Re:Beta "99" by Quantumstate · · Score: 1

      I got upgraded for 3.5b99 to 3.5 (presumably RC1 but it is like yours) and that is on Jaunty.

  3. 93/100... by mejogid · · Score: 5, Insightful

    I still don't understand the obsession with Acid tests - they measure performance in incredibly obscure areas and have a comparatively small bearing on real world performance. Webkit and Opera in particular have designed to the test to an extent, resulting in good scores but not necessarily comparable general compliance. I'm also slightly confused by the use of the word "still" - none of these bugs are severe enough to risk breakage leading up to a release candidate. I believe far more relevant are performance, bug fixes, features and HTML5/CSS3 support (which make far more of a contribution to moving the web on that Acid Test scores do) - areas in which Firefox 3.5 has improved dramatically. Talk about focusing on the negatives...

    1. Re:93/100... by Anonymous Coward · · Score: 4, Funny

      No. You're wrong and an ignoramus. I only visit websites which use those obscure areas of compliance, and I visit them ALL THE TIME, and the more I visit them, the more I can brag about how much better MY browser is than YOURS. Do you see how useful this is now?

    2. Re:93/100... by glop · · Score: 5, Insightful

      Why don't I have mod points today?
      The parent is so right. The video tag means that youtube and all the web streaming websites can work without Flash. And since Firefox users update quickly, this means 20% of Internet users will be able to do that within 6 months. That's pretty big when you think some people try to make us believe that HTML5 is 10 years away...

    3. Re:93/100... by Anonymous Coward · · Score: 0

      Yet that codec sucks.

    4. Re:93/100... by dvice_null · · Score: 0, Redundant

      > I still don't understand the obsession with Acid tests

      It is about marketing. It is something that can easily be measured and you can put products in quality order (or so it seems from the point of viewer) according to it. Reality is irrelevant in marketing.

    5. Re:93/100... by gbarules2999 · · Score: 1

      Talk about focusing on the negatives...

      It's open source. If it doesn't conquer the world, massage your back and bake you cookies all at the same time, it was a failure. Don't you know how these things work?

    6. Re:93/100... by Anonymous Coward · · Score: 0

      What about buttering my bread?

    7. Re:93/100... by theodicey · · Score: 1

      Bad measurables are worse than no measurables. Counting enemy combatants killed didn't get McNamara or the army results in Vietnam.

      ACID 3 sure came along at a convenient time for Google's browser marketing strategy. And it was designed so every browser would start from around the same score, not to test the most useful standards or the real-world web, so it wasn't very hard for Google and Apple to get to 100 when they focused on it.

      The author of the test works for Google, of course...clearly it's a conspiracy, and frankly one I'm sick of hearing about.

    8. Re:93/100... by Tubal-Cain · · Score: 2, Insightful

      So make a better patent-free codec, or buy a licence for the world.

    9. Re:93/100... by tepples · · Score: 1

      Bad measurables are worse than no measurables.

      A lot of people would disagree with you that Acid3 is in fact a bad measurable.

      And it was designed so every browser would start from around the same score, not to test the most useful standards

      A lot of people would disagree with you that the parts of the DOM that Acid3 tests are not useful.

      or the real-world web

      When Gecko-based browsers first came out, the real-world web still included ActiveX, which was already recognized as a security hazard.

    10. Re:93/100... by Darkness404 · · Score: 0

      A lot of people would disagree with you that Acid3 is in fact a bad measurable.

      And so what does Acid3 measure? Obscure things that don't matter because unless IE gets better than a 20 on it, I can't see it being used for actual pages. Until IE at least scores an ~80 or so, those nice standards will simply be used in tech demos.

      A lot of people would disagree with you that the parts of the DOM that Acid3 tests are not useful.

      Useful for what? For measuring standards that aren't really used? Its like advertising your sound system as supporting some strange format of jack that doesn't matter to 99.99999% of potential customers. Its not a bad thing that its included, but when you advertise it like its a necessary thing, the advertising loses momentum.

      When Gecko-based browsers first came out, the real-world web still included ActiveX, which was already recognized as a security hazard.

      There isn't that much difference in time periods though. Gecko was developed in 1997 while ActiveX was developed in 1996.

      --
      Taxation is legalized theft, no more, no less.
    11. Re:93/100... by Phroggy · · Score: 5, Interesting

      Acid tests are designed to highlight rendering bugs in current browsers, giving browser developers a chance to easily see where something is going wrong. All major browsers currently pass Acid2, which means if you create a web page that only uses the kind of code that Acid2 tests for, you can be sure it will render precisely the same way in current versions of Firefox, Internet Explorer, Safari, Opera, Chrome, etc. This is a huge step forward; ten years ago, it wasn't uncommon for a page to work correctly in one browser but be completely unusable in another.

      Now that all the major browsers pass Acid2, we need to find other ways in which web pages can display differently between different browsers. Since there is an official standard that defines what the correct behavior should be, we have something to test against; this is what Acid3 does. You're absolutely correct that passing Acid3 should not be the top priority, and failure to pass Acid3 is not a good reason for a user not to choose Firefox. However, the remaining things that prevent Firefox from passing Acid3 are indeed bugs, and eventually, they do need to be fixed. There are also other bugs in Firefox, that also need to be fixed, and many of these are more important than the bugs that cause Acid3 to fail.

      I agree that HTML5 and CSS3 are awesome, but if browsers can't render them correctly, they're not much good. Acid tests are an incredibly useful tool for browser developers to ensure that this happens. Acid4 is already being planned, and will help to find bugs in the way browsers handle HTML5 and CSS3 and SVG and other stuff, taking into account some of the lessons learned from problems with the Acid3 test (for example, Acid3 tests rendering speed; Acid4 will not).

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    12. Re:93/100... by alexborges · · Score: 1

      Why do you say this?

      Please elaborate: is it poor in bandwidth, is it poor in quality, is it poor in what area?

      --
      NO SIG
    13. Re:93/100... by tepples · · Score: 1

      And so what does Acid3 measure? Obscure things that don't matter because unless IE gets better than a 20 on it, I can't see it being used for actual pages.

      For one thing, it appears to be designed to shame Microsoft into improving Windows Internet Explorer. Had there been no Acid2, there might not have been an IE 8.

      Useful for what? For measuring standards that aren't really used?

      Just because a standard isn't used on June 17, 2009, doesn't mean it won't be used on June 18, 2009. Be it your intent or not, you are giving off an impression that bug-for-bug compatibility with a non-free program called Windows Internet Explorer is more important than following published standards.

      When Gecko-based browsers first came out, the real-world web still included ActiveX, which was already recognized as a security hazard.

      There isn't that much difference in time periods though. Gecko was developed in 1997 while ActiveX was developed in 1996.

      By "came out", I meant as general releases, not as technology previews. Mozilla Application Suite didn't hit 1.0 until the horrors of ActiveX were already apparent.

    14. Re:93/100... by Mystra_x64 · · Score: 1

      When Firefox fail it's always that other "designed to the test", yeah, yeah.

      --
      Quick way to get 30% Funny 70% Troll: defend Opera browser on /.
    15. Re:93/100... by Darkness404 · · Score: 1

      For one thing, it appears to be designed to shame Microsoft into improving Windows Internet Explorer. Had there been no Acid2, there might not have been an IE 8.

      Actually I think that there would have needed to be an IE 8 otherwise with the OEMs in Europe being allowed to bundle browsers of their choosing and wanting to have sites that look like they should in 2009, not in 2001, would bundle Firefox, Chrome or Safari leading to dwindling marketshare for MS and ultimately leading them to abandon their browser market or release a better browser.

      Just because a standard isn't used on June 17, 2009, doesn't mean it won't be used on June 18, 2009. Be it your intent or not, you are giving off an impression that bug-for-bug compatibility with a non-free program called Windows Internet Explorer is more important than following published standards.

      Ok, but IE still has the majority of marketshare and there are still legacy sites out there. The fact that it is non-free should only add to the fact that a free browser that is widely used should work with all sites, even those not coded up to specifications, otherwise if there was an IE only site that you had to access you would either be hand-parsing the HTML files, would have to emulate IE if you were using a different platform other than Windows, or run Windows in a VM. Myself I prefer the web to "just work", be secure, and not be a pain to code for. Firefox has all that and compatibility with IE only helps those goals. If that means that I don't get a standard that isn't used, thats fine with me. Its sorta like reverse engineering the iPod Dock connector to use with your own MP3 player so it can work with existing accessories rather than spending development on an ultra-free connector that may or may not be used. Sure, if time allows include both, but I'd rather have compatibility with existing sites than sites that may or may not be used in the future.

      --
      Taxation is legalized theft, no more, no less.
    16. Re:93/100... by tepples · · Score: 1

      Actually I think that there would have needed to be an IE 8 otherwise with the OEMs in Europe being allowed to bundle browsers of their choosing and wanting to have sites that look like they should in 2009, not in 2001, would bundle Firefox, Chrome or Safari leading to dwindling marketshare for MS and ultimately leading them to abandon their browser market or release a better browser.

      And the point of the Acid tests is to demonstrate whether a given web browser acts like a 2009 browser or a 2001 browser.

      The fact that it is non-free should only add to the fact that a free browser that is widely used should work with all sites, even those not coded up to specifications

      No web browser can Do What I Mean in all cases.

      otherwise if there was an IE only site that you had to access you would either be hand-parsing the HTML files, would have to emulate IE if you were using a different platform other than Windows, or run Windows in a VM.

      Or d) finding a way not to have to access the site, such as by going to a competitor's site. On the whole, Mac owners tend to spend more online than owners of PCs that run Windows. Since Microsoft stopped making Internet Explorer for Mac, it didn't make sense to turn away potential customers who use Safari, whose WebKit acts more like Gecko than like IE's Trident. That's why there aren't a lot of IE-only sites anymore as of June 2009.

      but I'd rather have compatibility with existing sites than sites that may or may not be used in the future.

      About a decade ago, did you continue to use AOL even after standard dial-up Internet became popular, because the "existing" sites were still on AOL?

    17. Re:93/100... by Darkness404 · · Score: 0

      And the point of the Acid tests is to demonstrate whether a given web browser acts like a 2009 browser or a 2001 browser.

      True, however anything better than an 80 should be deemed "acceptable" in acting like a 2009 browser. A 94 isn't much different than a 100 when it comes to web standards whenever there are competitors who score a 20.

      No web browser can Do What I Mean in all cases.

      No, but Firefox comes pretty close, in my experience it does a better job of rendering than WebKit based browsers or IE.

      Or d) finding a way not to have to access the site, such as by going to a competitor's site. On the whole, Mac owners tend to spend more online than owners of PCs that run Windows. Since Microsoft stopped making Internet Explorer for Mac, it didn't make sense to turn away potential customers who use Safari, whose WebKit acts more like Gecko than like IE's Trident. That's why there aren't a lot of IE-only sites anymore as of June 2009.

      What happens if you go to a site for a small bit of information but the site hasn't been updated in a while and uses IE only code? I'd much rather my browser render it like its supposed to look (how the web designer wanted it to, not how standards necessarily dictate) than have an unusable site. Sure, there aren't many sites like that anymore but there are some.

      About a decade ago, did you continue to use AOL even after standard dial-up Internet became popular, because the "existing" sites were still on AOL?

      There is a difference though, AOLs system was 100% proprietary, compared to simply bad code which has A) a reference implementation (how it looks in the browser it was coded for) along with B) an OSS rendering engine that due to hard work can render it almost as good as the reference. implementation. There is no reason to simply drop compatibility modes for the sake of enforcing standards which will never work on those older sites because they are simply archives.

      --
      Taxation is legalized theft, no more, no less.
    18. Re:93/100... by xanadu-xtroot.com · · Score: 1

      What about buttering my bread?

      Yes! It will! You have to supply the butter, though. (Unless you're running body-levels/cholesterol >=200.0, then you'll need to downgrade to margarine, which will satisfy the =body-sense/taste-5.0" to prevent your flavor from being upgraded in the future).

      Just sayin'...

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    19. Re:93/100... by Anonymous Coward · · Score: 0

      It's great to see morons wasting their mods points on something that clearly isn't flamebait.

    20. Re:93/100... by tepples · · Score: 1

      True, however anything better than an 80 should be deemed "acceptable" in acting like a 2009 browser. A 94 isn't much different than a 100 when it comes to web standards whenever there are competitors who score a 20.

      Agreed. I was under the impression that at least someone in this thread thought a 20 was as good as a 94.

      What happens if you go to a site for a small bit of information but the site hasn't been updated in a while

      If it's info I'm after, and my web browser is making a mess of the layout, I'll shut off its style sheet to read the info.

      There is no reason to simply drop compatibility modes for the sake of enforcing standards

      Unless the compatibility modes increase the complexity of testing the application. Having the equivalent of six rendering engines (one for today's code and one to match the defects in five previous browsers) makes testing take several times longer and allows more of a chance for crashes, data loss, or privilege escalations to slip through testing. Besides, how is a web browser supposed to know which of several quirks modes to use on a given page?

    21. Re:93/100... by Millennium · · Score: 4, Insightful

      The thing about Acid tests is that specs are ambiguous: there are often multiple possible meanings to a given section, and inevitable different people will implement them in different ways. Some of those will be incompatible, yet both can claim compliance, so this helps no one. Tests, on the other hand, are unambiguous: either you pass or you do not.

      This is why Web platforms of the future will not be based on specifications, but on the test suites. Acid tests are not perfect at this, but they are light-years better than previous practice. If Mozilla wants to be seen as taking standards seriously again, they are going to have to start taking these tests seriously, and that means 100% as soon as possible.

      They've improved over Acid2, at least, when even iCab -a browser developed by one person- beat them to full compliance by months. But they still have a long way to go. When major tests like this are developed, 100% needs to be a dealbreaker goal for the next major release, not something put off until 2-3 big releases in the future. Opera gets this, and the WebKit folks get this. Mozilla used to, back in the days of the first CSS Acid Test. But somewhere along the way, they lost sight of it, and they need to be reminded.

    22. Re:93/100... by Anonymous Coward · · Score: 1, Insightful

      Acid tests are designed to highlight rendering bugs in current browsers, giving browser developers a chance to easily see where something is going wrong.

      ACID isn't comprehensive enough to do this, and futhermore it encourages browser vendors to develop for the test.

      In practice ACID acts to promote adoption of bleeding edge features (some of which aren't even standardized yet), and quantitiavely says IE sucks. As an actual QA tool or something web developers need to worry about, it's mostly useless.

    23. Re:93/100... by NaCh0 · · Score: 1
      and futhermore it encourages browser vendors to develop for the test.

      Since the test is for standards compliance, I'm more than happy that products are developed with the ACID tests in mind. Encourage away!!

      Prior to ACID, the only reliable cross platform HTML was a, br, b and i tags. Heck, even the img tag in IE6 is broken because it doesn't do PNG transparency.

    24. Re:93/100... by BZ · · Score: 3, Informative

      > This is why Web platforms of the future will not be based on specifications, but
      > on the test suites.

      Actually, no. This is why people are much more careful about not writing ambiguous specifications now.

      You can't "test suite" your way to full coverage of something like CSS 2.1: too many features, too many combinations, too many things to test.

      > If Mozilla wants to be seen as taking standards seriously again

      Which standards? Some standards are more important than others. It might just be that stuff the acid test is not testing is more important than stuff it should be... (and is in fact the case with parts of acid3).

      It might also be that supporting the standard and not supporting it at all are both better options than supporting just the part that the test tests.

      So no, 100% test-compliance should never be the primary goal. Support for the standards that are useful to support should be.

    25. Re:93/100... by Chuck+Chunder · · Score: 1

      ACID isn't comprehensive enough to do this, and futhermore it encourages browser vendors to develop for the test.

      And what is? Even if it only covers x% of the overall specs it is good to have an open set of tests that all browser makers can work with to get some common ground in how their browsers behave.. Without a common set of tests two browser makers might both manage to cover 90% of the specs right but the 10% they get wrong might not be the same, ie there could be a 20% difference in browser behaviour. The problem with development isn't just the overall correctness of individual browsers, it's the degree of commonality between them. That the ACID tests help promote commonality in known areas is useful to web developers.

      --
      Boffoonery - downloadable Comedy Benefit for Bletchley Park
    26. Re:93/100... by Anonymous Coward · · Score: 0

      Except Acid's x% is like 1%. I believe W3C is working on a more comprehensive compliance test

    27. Re:93/100... by mgblst · · Score: 1

      And I don't understand people who don't understand that it is a quick visualization of how well the browser is doing css standards wise.

      It is a quick benchmark, wtf is not to understand about that?

    28. Re:93/100... by Ilgaz · · Score: 2, Interesting

      What makes you think Youtube will move to video tag? Youtube's main reason for success was relying on Flash, a plugin which everyone has and trusts to.

      Do you really think Youtube would lose that convenience? Do they really care if H264 is patented? I don't really. All I see is a platform neutral, documented standard which was designed with media professionals. I don't see some "evil monster" when I look to Flash or h264. I know what would happen if Flash and h264 didn't exist. We would be arguing about WMV and evil Microsoft not releasing a player/plugin for Linux and threatening some open source developers with lawsuit.

      I am all for standards but thinking a proposed thing will replace Flash, even while MS is just being joked with their Silverlight billion dollar failure supposed to rival it...

    29. Re:93/100... by Ilgaz · · Score: 1

      There are some people remembering the Firefox/Mozilla original mission. It is all about standards. Earliest Mozillas worked like junk but they have always beaten the rest of the market regarding standards support.

      They could be reminding their mission. A standard, open web with all standards. Not thousands of hacks to show google something .com fine, to perfect the standards support first and hack later.

      BTW, does "So what?" asking Firefox community also say "So what?" to Microsoft/IE regarding standards compliance?

    30. Re:93/100... by gzipped_tar · · Score: 1

      You don't have to understand it. As I said in another post, Acid3 score is the new penis size.

      --
      Colorless green Cthulhu waits dreaming furiously.
    31. Re:93/100... by xtracto · · Score: 1

      Dear pirates--if copyright law is wrong, then the GPL has no legal standing.

      AAhhh... so that's why I hear some heads popping every now and then that I read the slashdot comments!

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    32. Re:93/100... by msclrhd · · Score: 1

      TBH, 93% is a *very* respectable score. Yes, it's not 100% like Opera and WebKit (Safari, Chrome, ...), *but* it is leagues better than IE.

      If you want to help out, see http://www.wg9s.com/mozilla/firefox/ for an Acid3 testing build of FF (currently at 97%). The thing to remember is that care needs to be made so that the fixes (a) don't break extensions, (b) don't cause rendering regressions for popular websites. The remaining issues seem to be (1) that some of the tests are failing intermittently (bug 335998), (2) lack of SVG font support, (3) favicon being dispalyed at the end of the tests and (4) some of the tests running slowly, failing the smooth animation requirement.

      The thing that really annoys me, though is the piece of crap that is IE. IE doesn't have support for the CSS min-width attribute. IE doesn't support SVG. Just about the only thing that IE has going for it is that it has native JSON support.

      It is not Firefox that is holding back the web - the competition with Opera, Safari and Chrome is a good thing - IE is holding back the web. In the new web wars around standards compliance, Acid test conformance and JavaScript performance IE is losing. So take back the web!

    33. Re:93/100... by MrNemesis · · Score: 1

      I hereby proclaim that ACID tests should no longer be the gold standard for obscure CSS edge cases, and instead we should wait for the next generation of browsers that can render slashdot correctly - since over the last few months I've not used any browser that's rendered a page the same way in any other browser ;)

      --
      Moderation Total: -1 Troll, +3 Goat
    34. Re:93/100... by Anonymous Coward · · Score: 1, Informative

      Youtube are owned by Google.
      A Google employee is chairing HTML5, and Google have a lot invested in HTML5, including the video tag.

      Also, http://www.youtube.com/html5

      Yeah, I think they have plans.

    35. Re:93/100... by BZ · · Score: 1

      I think you're preaching to the choir here. As far as helping out, I am in fact running nightlies, for obvious reasons. Have to eat my own dogfood...

    36. Re:93/100... by plague3106 · · Score: 1

      And the point of the Acid tests is to demonstrate whether a given web browser acts like a 2009 browser or a 2001 browser.

      Except that not passing the tests hasn't stopped me from seeing sites using IE. So as the OP said, Acid tests are irrelevent.

      No web browser can Do What I Mean in all cases.

      That's not what he wants; he wants it to "do what IE does when its clearly not up to standards." A much narrower scoope.

      Or d) finding a way not to have to access the site, such as by going to a competitor's site.

      Oh please. I could give a shit what browser I'm using.. the content on site is what's important. I'm going to use the browser that works with the most sites, so switching to IE over FF will allow me to do that, that's what I'll do.

      On the whole, Mac owners tend to spend more online than owners of PCs that run Windows.

      I see you like to make things up. Glad to see your imagination is healthy.

      Since Microsoft stopped making Internet Explorer for Mac, it didn't make sense to turn away potential customers who use Safari, whose WebKit acts more like Gecko than like IE's Trident.

      Can't argue there; if you find a significant number of people are accessing your site with a Mac, and you want those people, you should try to accomodate them. But if they're pretty insignficant (and they are), I'm not sure you make a good ROI.

      That's why there aren't a lot of IE-only sites anymore as of June 2009.

      Do you have any actual evidence, or are you just making things up? FF has arguably done more to push things along than Safari.

      About a decade ago, did you continue to use AOL even after standard dial-up Internet became popular, because the "existing" sites were still on AOL?

      What is this all about? First off, the "sites" were already outside of AOL, because anyone could put a site on the internet, but not necessarly on AOL exclusively. Just to be clear though, I kept AOL for long after I even after I had broadband, because there were some things that were exclusive (that it only cost $5 / month helped too). It did eventually stop offering anything I couldn't get elsewhere, and they tried to raise the rate (even though they promised they never would), so I dropped it.

    37. Re:93/100... by BZ · · Score: 1

      Oh, and testing the SMIL-enabled builds is not as good as use of my time as you probably think. ;)

    38. Re:93/100... by dominator · · Score: 1

      even iCab -a browser developed by one person- beat them to full compliance by months

      That's disingenuous. The version of iCab (4.6) that passed the Acid3 test uses the same WebKit rendering engine as Safari and Chrome. And it beat Safari 4 to market by 1 day.

    39. Re:93/100... by Eskarel · · Score: 1

      All of the above. The quality is overall lower, that lower quality requires more bandwidth, and since it's not hardware accelerated it's also more resource intensive.

      The only thing Theora has going for it is that it's theoretically legal to use it without licensing anything. As far as I understand it there are a number of companies who claim this isn't actually the case, and the cases have yet to be settled, so it's only theoretical so far.

    40. Re:93/100... by Phroggy · · Score: 1

      ACID isn't comprehensive enough to do this,

      It's not designed to be comprehensive, it's designed to highlight a selection of common problems.

      and futhermore it encourages browser vendors to develop for the test.

      This is absolutely true, and it's one of the criticisms of ACID3 that will be taken into account when designing ACID4. However, as NaCh0 said, there's not really anything wrong with browsers designing for the test, as long as the test is based on standards that we all want implemented. ACID4 will be better about this.

      In practice ACID acts to promote adoption of bleeding edge features (some of which aren't even standardized yet),

      Which features tested in ACID3 aren't standardized? Can you be specific? Sometimes the development of an ACID test uncovers deficiencies in the standards documentation, which is also good to fix.

      and quantitiavely says IE sucks.

      It also quantitatively says IE8 doesn't really suck that much. Microsoft is a few years behind, but they're back on board now and working hard to catch up.

      As an actual QA tool or something web developers need to worry about, it's mostly useless.

      It's not intended for web developers (people who create web pages) at all; it's intended for browser developers (people working on Gecko, WebKit, Trident and Presto). Web developers get the indirect benefit of having the code they write work across more browsers without needing browser-specific hacks to work around all the incompatibilities.

      ACID3 isn't perfect. Ian Hickson, the guy in charge of HTML5 and who created ACID3, is well aware of that, and he'll do better next time. Users shouldn't avoid Firefox because it doesn't pass ACID3. Developers should continue to fix the problems in Firefox that prevent it from passing ACID3, in addition to other bugs in Firefox that ACID3 doesn't test for. Developers should also tell hixie what they do and do not want tested for in ACID4!

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    41. Re:93/100... by Millennium · · Score: 1

      even iCab -a browser developed by one person- beat them to full compliance by months

      That's disingenuous. The version of iCab (4.6) that passed the Acid3 test uses the same WebKit rendering engine as Safari and Chrome. And it beat Safari 4 to market by 1 day.

      True, but out of scope: I was talking about Acid2, not Acid3.

    42. Re:93/100... by Millennium · · Score: 1

      > This is why Web platforms of the future will not be based on specifications, but
      > on the test suites.

      Actually, no. This is why people are much more careful about not writing ambiguous specifications now.

      Ultimately, that isn't enough: human language inherently introduces ambiguities that will plague standards specs until the end of time. A large part of the point of test suites is to resolve those ambiguities.

      This is not to say that human-readable specs are bad things. They're necessary for almost anyone to be able to understand the standard being implemented. But they are, and should be, the first line; not the final word.

      You can't "test suite" your way to full coverage of something like CSS 2.1: too many features, too many combinations, too many things to test.

      Certainly you can. This is what QA is for. It takes a lot of initial effort, which is the point of automated testing, but a properly-designed suite can deal with basically anything that is deemed to matter by the people who created the specs. It's all a matter of how much the test makers and standards creators are willing to do.

      > If Mozilla wants to be seen as taking standards seriously again

      Which standards? Some standards are more important than others.

      Indeed they are. The most important being HTML, CSS, ECMAScript, and the DOM: standards out there in the wild right now, being used in pages the world over, and claimed to be supported by most major browsers.

      It might just be that stuff the acid test is not testing is more important than stuff it should be... (and is in fact the case with parts of acid3).

      No, it's not the case. Quite an easy statement to make, when you don't have to back anything up.

      So I challenge you: what makes XBL more important than, say, CSS? Acid3 tests real-world problems that prominent developers have been complaining about for years. Sure, these aren't the latest shiny tech toys, but they provide the infrastructure necessary to make the newer up-and-comers practical.

      It might also be that supporting the standard and not supporting it at all are both better options than supporting just the part that the test tests.

      Better still would be to make test suites that actually cover the whole standard. Until that happens, Acid3 -testing the parts that people care about to solve the problems people care about- are the best we have.

      So no, 100% test-compliance should never be the primary goal. Support for the standards that are useful to support should be.

      If you don't pass the tests, you do not support the standard. Period.

    43. Re:93/100... by Millennium · · Score: 1

      TBH, 93% is a *very* respectable score.

      Only in the absence of competitors that have been doing 100% for months. Once that happens, 99% is as bad as zero.

    44. Re:93/100... by BZ · · Score: 1

      > human language inherently introduces ambiguities that will plague standards specs until
      > the end of time

      Specs are more heavily relying on algorithmic definitions of behavior, precisely for this reason.

      > Certainly you can.

      I don't think you understand.... fully testing all possible combinations of CSS2.1 features is likely to result in a total size of tests that exceeds currently available global storage capacity. It's not just a matter of "effort"; it's actually a matter of fundamental physical resource limits.

      > anything that is deemed to matter

      Then you're not actually testing the whole thing. You're testing some subset of it... and what matters will change over time. This way lies madness.

      > The most important being HTML, CSS, ECMAScript, and the DOM

      There is no "the DOM". There are 1-2 dozen different DOM specs; again, some are more important than others. Interoperability on the important ones is pretty good, forcing Acid3 to focus on the unimportant ones.

      > No, it's not the case. Quite an easy statement to make, when you don't have to back
      > anything up.

      Sure it is. By design, Acid3 does no testing of most of CSS3 Selectors. On the other hand, it tests some aspects of handling of invalid UTF-16 input (unpaired surrogates), tests some edge-cases of DOM Traversal involving the iterator throwing an exception, and tests DOM Range operations on children of a document. I can assure you that by the "anything that is deemed to matter" metric the CSS3 Selectors stuff is more important.

      > what makes XBL more important than, say, CSS?

      Sorry, straw man. Nowhere did I make this claim (which I happen to think is false).

      > Acid3 tests real-world problems that prominent developers have been complaining about
      > for years

      I have yet to see a single prominent developer complain about handling of unpaired UTF-16 surrogates. Got a reference? Or did you just buy the hype about what it's testing instead of actually... reading the test?

      > Better still would be to make test suites that actually cover the whole standard.

      Like I said above, physically impossible. You can do test suites that test features in isolation, and test some "common" combinations, but for a standard the size of CSS2.1 (or SVG of any version, or HTML of any version) testing all possible inputs is not doable.

      > Acid3 -testing the parts that people care about

      If that were what Acid3 were testing, I'd care a lot more about Acid3...

      > If you don't pass the tests, you do not support the standard. Period.

      Sure. And I don't think support for some standards should be a primary goal, even if those happen to be the ones with overhyped tests for them. In fact, I don't think 100% support for any standard should automatically be the _primary_ goal. It should depend on exactly what that 100% support entails. If the standard is just dumb (which often they are), then getting errata to happen may be a better primary goal.

    45. Re:93/100... by Millennium · · Score: 1

      > human language inherently introduces ambiguities that will plague standards specs until
      > the end of time

      Specs are more heavily relying on algorithmic definitions of behavior, precisely for this reason.

      And again, it helps to some degree. It is not, however, a panacea, nor does it remove the absolute necessity of proper testing. That the Web has somehow limped along for a few years without proper test suites does not mean they are not necessary; it only means that there is a serious problem that needs to be corrected. Tests are the cure.

      > Certainly you can.

      I don't think you understand.... fully testing all possible combinations of CSS2.1 features is likely to result in a total size of tests that exceeds currently available global storage capacity. It's not just a matter of "effort"; it's actually a matter of fundamental physical resource limits.

      That would indeed be impractical, but fortunately it is not necessary. Continuing with your CSS example, you do not in fact have to generate all possible combinations of CSS or all possible CSS documents to show that these tests will pass. A large part of the the QA task is determining which tests are needed in order to prove that the others would pass.

      There are 1-2 dozen different DOM specs; again, some are more important than others. Interoperability on the important ones is pretty good, forcing Acid3 to focus on the unimportant ones.

      The DOM Events module would like to have a word with you. Interoperability has indeed improved in parts of the DOM. This has made those areas in where interoperability hasn't improved more important, because the interoperable areas are frankly a solved problem. It's true that this is pure infrastructure, rather than the latest shiny object to come along. This does not make it less important.

      And I don't think support for some standards should be a primary goal, even if those happen to be the ones with overhyped tests for them. In fact, I don't think 100% support for any standard should automatically be the _primary_ goal. It should depend on exactly what that 100% support entails.

      100% support should only be a goal for those standards one claims to support. On those standards, however, 99% is a failing grade. Support it all or not at all, and finish what you start before moving on to the next shiny object.

    46. Re:93/100... by BZ · · Score: 1

      > nor does it remove the absolute necessity of proper testing

      Oh, sure. Testing is needed to make sure people actually try to implement the spec. But testing can't ensure they actually do, so it too is not a panacea. You need both: unambiguous specs and test suites with reasonable coverage. Then you can with certainty say that the precise things being tested were in fact implemented per spec.

      > you do not in fact have to generate all possible combinations of CSS or all possible CSS
      > documents to show that these tests will pass

      Actually, you do, for black-box testing. If you happen to know something about the precise implementation details you might be able to limit the scope of testing, but if you're a standards test suite author, you have no way to know what the implementations will do.

      A simple example: an implementation may have different codepaths for values of CSS property A (say "position") that affect how CSS property B (say "border-color") is handled. This isn't a hypothetical case but a pretty concrete example I pulled from a browser's bug database. Existing UAs have had just such differences, due to applying certain layout/rendering optimizations for some values of properties but not others. So sadly, you cannot test things in isolation and deduce that they will continue to work when used together, because different codepaths are used for those cases...

      So a minimal testsuite for CSS2.1 conformance testing would include one test per possible set of values of all CSS properties for a given node... That would not catch issues involving containing blocks or whatnot, of course.

      > The DOM Events module would like to have a word with you.

      That's mostly harmed by the fact that some UAs aren't making any attempt to implement it at all. But yes, interoperability on DOM Events is much worse than it should be for the UAs that do implement it; point granted.

      Interestingly, Acid3 didn't seriously test DOM Events....

      > 100% support should only be a goal for those standards one claims to support.

      In that case, claiming to support standards should be a non-goal. The goal should be implementing, correctly, functionality that's useful.

      > finish what you start before moving on to the next shiny object.

      I suggest reading http://www.jwz.org/doc/worse-is-better.html

  4. Still the slowest browser. by Nightspirit · · Score: 4, Interesting

    Yes, even slower than IE8. From start up times to rendering pages firefox is by far the slowest. If you don't believe me download IE8, use it for a week, and you'll see for yourself. IE8 sucks for other reasons (crashes more, no plugins, forgets log-ins), and firefox is my main browser, but it is seriously falling behind. It's speed, private browsing, and I would argue even security (no sandbox/protected mode) are subpar compared to the competition. And they really need to fix private browsing, it's pretty sad when an IE feature works better than the open source alternative. As repeated ad-nauseum here firefox is still my main browser due to plugins, but everytime the browser freezes because one tab decides it wants to do something I re-evaluate this decision.

    1. Re:Still the slowest browser. by mejogid · · Score: 5, Informative

      CNet show firefox being substantially faster as of March in terms of browser performance. Admittedly firefox is a dog to start up, but that's one of the major goals for 3.6 last I checked. Having used the betas for a while, it's been a long time since I've felt I'm waiting on my browser as I did in versions 3 and particularly 2. I don't think anyone with a decent PC is going to be frustrated by the performance on 3.5, and with additional improvements already underway in trunk I don't think firefox is in any way falling behind. Oh, and how is private browsing broken in 3.5?

    2. Re:Still the slowest browser. by Nightspirit · · Score: 0, Redundant

      I don't care about benchmarks. I have the most up to date versions of chrome, firefox (previously 3.5b4 I believe), and IE8. Firefox is patently the slowest in nearly every regard.

      As for private browsing, firefox signs you out of and closes whatever you are doing and starts a new private browsing session (then when you are done returns to the state you left, although sometimes logs you out of everything). Chrome and IE8 open a new private browsing session, so you can keep one window logged into all your sites and use the private window for your private stuff.

    3. Re:Still the slowest browser. by mejogid · · Score: 3, Insightful

      I'm sorry, but without any benchmark or other reasonable test there's no way of ranking the browsers in terms of general speed. I personally find firefox 3.5 faster than IE8 - I don't know if that's because I'm using XP, because that's the result I want to see or any other reason; the point is it's a subjective evaluation. Furthermore, adblock with a reasonable filter list and flasblock improve page load times and responsiveness substantially. The private browsing issue is reasonable, although I've not personally been troubled by it having no real need to combine "private" and less private browsing. I also feel the clear recent history function mitigates that to some extent.

    4. Re:Still the slowest browser. by gbarules2999 · · Score: 1

      I've been using 3.5's beta for a while (and I'm running the RC now). It's only slightly faster than 3.0, but it's not substantially slower than IE8 by any stretch of the imagination.

      Maybe you need to steak your "about:config"?

    5. Re:Still the slowest browser. by Nightspirit · · Score: 0, Redundant

      Yah but none of those are real life benchmarks, they are javascript tests. To judge my own curiosity I did my own inaccurate benchmark using naked browsers (no extensions) warm booted with yahoo as the homepage, going to different sites in my bookmark bars (all aligned in the same order) and using a timer program.

      Firfox consistently loaded through my test at around 11 seconds, Chrome and IE8 each at 15. So that does backup what zdnet is saying. I think my perception of firefox as being slow has more to do with the browser locking up when a tab locks up, and this may occur more in firefox, which would lead me to believe that overall it is slower.

    6. Re:Still the slowest browser. by cbhacking · · Score: 1

      Does 3.5 actually *have* private browsing? The equivalent of IE8's InPrivate mode, or Chrome's Incognito? If so, good for them - Google and Microsoft released those features near-simultaneously, and it's about time they made it into the world's second-most-popular browser (ignoring version numbers).

      Firefox 3.0 takes bloody AGES to start up on the Linux boxes at my school (GNOME, Fedora 9). It's probably a misconfiguration thing - it's faster on my KDE4 system (although still slower than Konqueror) - but even on Windows it's still substantially slower to start than IE8. I suppose I should try 3.5 and see if they've improved there, though.

      --
      There's no place I could be, since I've found Serenity...
    7. Re:Still the slowest browser. by anaesthetica · · Score: 3, Informative

      Indeed, performance is the top priority for Firefox.next (presumably Fx3.6 although you never know). Codenamed 'Namoroka,' the developers have selected several common tasks which they want to perceptibly increase the speed of, including:

      • Startup
      • Opening a new tab
      • Loading a bookmarked page
      • Autocompleting a location in the Awesomebar
      • Play rich media content
      • Animation and other interaction techniques to reduce lag between action and feedback, and to improve perceived speed
    8. Re:Still the slowest browser. by RiotingPacifist · · Score: 1

      preload and readahead speedup firefox startup times significantly, 3.5 is pretty quick here but i have taken care with the extensions i use (no tmp,fasterfox,etc)

      --
      IranAir Flight 655 never forget!
    9. Re:Still the slowest browser. by Anonymous Coward · · Score: 0

      I didn't really notice the speed difference on my regular computer. However, I borrowed a friend's older laptop recently. It had Opera 9 and Firefox 3 install on it. The difference was so large that I was able to double-click the Firefox icon, open Opera, check my e-mail for new messages (in Opera) and close it by the time Firefox started up. Firefox was running without any plugins. On older hardware the difference is very apparent.

    10. Re:Still the slowest browser. by Anonymous Coward · · Score: 0

      Not enough. Most of those operations should be true interactive. There should be no perceptible delay between action and response. Computers are fast these day, and our software should damn well be fast too.

    11. Re:Still the slowest browser. by Quantumstate · · Score: 1

      If you want to test speed first create a new blank Firefox profile. Of course you wouldn't normally browse like that because you like the functionality of the plugins, but you don't get them with other browsers anyway so you go round in circles. But if you are comparing you must at least compare like with like, although I would say the test is worthless because you don't have what you want in the other browsers so however fast they are you won't want them.

    12. Re:Still the slowest browser. by Anonymous Coward · · Score: 0

      everytime the browser freezes because one tab decides it wants to do something I re-evaluate this decision

      Did you remember to change the equation?

  5. Extensions by mwolfe38 · · Score: 1, Insightful

    Anyone know if xmarks, adblock, and firebug extensions are available for it yet? If so I'll download it in a heartbeat.. Otherwise I think I'll wait.

    1. Re:Extensions by Tubal-Cain · · Score: 2, Informative

      Adblock Plus & NoScript work fine in Minefield, so they almost certainly will work in the RC. I don't know about other plugins, though.

    2. Re:Extensions by RiotingPacifist · · Score: 1

      dunno about xmarks, but I've been using http://www.andyhalford.com/syncplaces/index.html with minefield after fedora11betas had issues with firefox3.5.

      --
      IranAir Flight 655 never forget!
    3. Re:Extensions by therealmorris · · Score: 1

      add xmarks to that too, working fine here, as are all my add-ons, including !

    4. Re:Extensions by wolrahnaes · · Score: 1

      Currently using all three on FF 3.5b99, so they should work fine on the RC as well.

      --
      I used to get high on life, but I developed a tolerance. Now I need something stronger.
    5. Re:Extensions by maglor_83 · · Score: 1

      xmarks, adblock plus, ietab, flashblock, kallour and stylish are all working. Don't know about firebug.

    6. Re:Extensions by Marcika · · Score: 1

      Adblock Plus & NoScript work fine in Minefield, so they almost certainly will work in the RC. I don't know about other plugins, though.

      All of my plugins work now (though they still have to be enabled). Tab Mix Plus was screwy in the 3.1/3.5 nightlies and betas, but works fine now as well.

    7. Re:Extensions by boteeka · · Score: 1

      Yes, these extensions are all working in RC too.

    8. Re:Extensions by Quantumstate · · Score: 1

      I am running 3.5 (that is what it says but I presume it is RC1) and I have xmarks and adblock working normally. Firebug requires you to use the 1.4 beta release. I am not so sure about how stable this is because I don't run it in my default profile and i haven't been doing web development recently due to exams. Previously I had to use the 1.4 alpha releases which were buggy but I cannot comment on the 1.4 beta.

  6. available now... by zixel · · Score: 1

    If you want it now replace 3.5b4 to 3.5rc1 in the URL from http://www.mozilla.com/en-US/firefox/all-beta.html Might not be intended but it worked for me.

    1. Re:available now... by Anonymous Coward · · Score: 0

      This works ppl:

      http://www.mozilla.com/products/download.html?product=firefox-3.5rc1&os=win&lang=en-US

      replace as needed, for you ferners are linux nerds.

  7. v3.5 and still no MSI package for Windows by denis-The-menace · · Score: 5, Interesting

    I wish Mozilla would make up their minds: are they going to target the Corps or not?

    Even if you can get an MSI from Frontmotion (http://www.frontmotion.com/Firefox/download_firefox.htm), the corps will never go for it unless it comes off the Mozilla servers and is on the same web page as the current XPI installers. It's a "warm and fuzzy" thing that they need.

    If Mozilla could somehow sanction those MSIs from Frontmotion then the corps would be more comfortable with it. Even a link from here (http://www.mozilla.com/en-US/firefox/all.html) would give FrontMotion's MSI package credibility.

    --
    Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    1. Re:v3.5 and still no MSI package for Windows by Slashdot+Suxxors · · Score: 1

      Pardon my ignorance, but this is a serious question; what would be the difference in downloading an MSI package versus an .exe if they both achieve the same thing?

    2. Re:v3.5 and still no MSI package for Windows by Anonymous Coward · · Score: 0

      You are correct, and since windows is the only platform they really care about, it should be an MSI. The linux and mac ports are second class and they don't care about any other OS at all.

    3. Re:v3.5 and still no MSI package for Windows by Anonymous Coward · · Score: 1, Informative

      They don't achieve the same thing in all cases.
      Admins can slipstream the MSI as an update using their existing systems. The .exe requires human intervention.

    4. Re:v3.5 and still no MSI package for Windows by Elgonn · · Score: 2, Informative

      They don't achieve the same thing because the MSI while seemingly doing nothing more than an exe installer integrates correctly with Active Directory. You don't roll out 10k+ installs with an exe. http://en.wikipedia.org/wiki/Windows_Installer

    5. Re:v3.5 and still no MSI package for Windows by tepples · · Score: 4, Informative

      Pardon my ignorance, but this is a serious question; what would be the difference in downloading an MSI package versus an .exe if they both achieve the same thing?

      Because they don't in fact achieve the same thing. Deployment of software across hundreds of machines in an Active Directory environment relies on Group Policy objects that reference .msi packages.

    6. Re:v3.5 and still no MSI package for Windows by Anonymous Coward · · Score: 0

      Same reason you would probably prefer a .deb or an .rpm over some random executable binary in Linux.

      More specifically an MSI describes how the software should be installed which is something that the OS itself can handle or there are several tools which can be used with MSIs for deploying the application. For example, in Active Directory I can take any MSI and deploy it to thousands of machines with custom features selected based on a criteria, or I can publish that the application exists and allow the end user to decide to install the application, even if they don't have the rights to install other applications. I can take the MSI, customize the contents and repackage it.

      It's no longer the 90s. No OS should rely on installer programs that run native code that copy files.

    7. Re:v3.5 and still no MSI package for Windows by hattig · · Score: 2, Insightful

      I think that Google Chrome will get corporate friendly before Firefox.

      Firefox doesn't really have a plan for targeting business users - it's as if they don't understand corporate needs!

      * Redirect update server to internal corporate network so they can test new releases before updating the corporate desktops.

      * Fine-grained control at the policy level over installable extensions, themes, plugins. I.e., stop users installing their own, define a set of standard corporate extensions, and so on.

      * Can run those internal designed-for-IE6-by-inept-programmers websites, that the company has no budget to update.

      And I'm sure many many more can be thought of by people who actually work in corporate IT departments.

    8. Re:v3.5 and still no MSI package for Windows by RiotingPacifist · · Score: 1

      open a bug report?

      --
      IranAir Flight 655 never forget!
    9. Re:v3.5 and still no MSI package for Windows by denis-The-menace · · Score: 1

      There is one but I don't know if it's still open.
      It was promised for version 3.0 but it never happened.

      --
      Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    10. Re:v3.5 and still no MSI package for Windows by denis-The-menace · · Score: 1

      I think you're right.
      By that time though, it will be too late for Firefox to get corporate mindshare.

      --
      Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    11. Re:v3.5 and still no MSI package for Windows by Techman83 · · Score: 1

      MSI's are far easier to deploy than EXE's, because they work in a relatively consistent manner (there are some niggles here and there, but you learn those). Every EXE can be packaged differently, some self extracting, some install shield, etc and they all have different switches to get them going, if it can be done at all. Also MSI installs are far easier for deployment software to monitor the progress, so no time delay tricks when moving onto the next app to deploy.

      Mozilla may not make MSI's, but you can get them from Front Motion or you can package them yourself with something like AdminStudio, which Is damn trivial because FF isn't intricately tied to the windows backend.

      --
      # cat /dev/mem | strings | grep -i cat
      Damn, my RAM is full of cats. MEOW!!
    12. Re:v3.5 and still no MSI package for Windows by msclrhd · · Score: 1

      So why does FF have a cross-platform UI engine (XUL) and have native theme support for Mac and Linux as well as XP and Vista. Or are you talking about Chrome/Chromium that was written to the Windows API?

    13. Re:v3.5 and still no MSI package for Windows by handsomepete · · Score: 1

      While this may not help you, there are certainly options for deploying silently without the MSI if you're so inclined.

      If you really can't deploy anything but MSIs, then how do you handle the other thousands of installers that aren't MSI packaged? Firefox seems like a nit in comparison to the legions of corporate-important applications that use any other install method but MSI. Or legacy apps that were packaged before the popularity of MSI. Or in house desktop applications. Or any number of other obnoxious speed bumps you deal with when managing a large number of desktops + app deployment in a corporate environment.

  8. Re:Open Source FAIL *again*. by Synchis · · Score: 1

    First they ignore you...
    Then they ridicule you...
    Then they fight you...

    Then you win.

    Enjoy

    --
    Thomas A. Knight
    Author of The Time Weaver
  9. 93/100 by Tubal-Cain · · Score: 2, Insightful

    RC1 still scores a 93/100 on the Acid3 test.

    Minefield has scored 94/100 for quite some time now, so I doubt Shiretoko will score any better at release.

    1. Re:93/100 by Anonymous Coward · · Score: 0

      Minefield now scores 96/100.

  10. Have they improved the memory leaks? by superyanthrax · · Score: 4, Interesting

    I know it's a tired topic, but it's a legitimate one, and not one that can be explained away by saying "extension writers suck".

    1. Re:Have they improved the memory leaks? by RiotingPacifist · · Score: 3, Interesting

      yes, as with 3 the memory footprint is significantly reduced, its still a bit on the high side here 128mb (the most any one program uses) but i have plenty of ram (~1.5Gb) so much of that may be features instead of leaks.

      --
      IranAir Flight 655 never forget!
    2. Re:Have they improved the memory leaks? by Anonymous Coward · · Score: 0

      There are still leaks. Here's my experience: yours might vary.

      When I first launch it (using only adblock plus extension) it uses ~50 MB of memory. If I don't touch anything and let it sit for a day, it's up to 200 MB. I've seen it get as high as 450 MB, which seems like a LOT on a 1 GB machine.

      On a smaller 512 MB machine, it's unusable. It'll run OK for a little while after launching it, but soon it starts to make the whole machine swap so bad it's not usable. Then if I kill it, the machine is back to being fine. It's OK for about 10 or 15 minutes of use.

    3. Re:Have they improved the memory leaks? by Anonymous Coward · · Score: 0

      Ever since 3 it's been totally fine. A little on the heavy side of footprint for sure, but I keep browsers open for weeks at a time and it doesn't grow.

      At this point if you are having trouble, it probably IS sucky extensions you are using.

  11. What is decent? by tepples · · Score: 1

    I don't think anyone with a decent PC is going to be frustrated by the performance on 3.5

    I don't understand what you mean by "decent". Low-cost subnotebook PCs optimized for size and battery life over CPU speed have become popular over the past year; are those "indecent"?

    1. Re:What is decent? by mejogid · · Score: 1

      This is a strawman - nowhere did I claim that firefox would perform at the desired speed on any piece of hardware, and I'm sure there are some netbooks on which its performance leaves something to be desired. However, that remains only a minute proportion of total computer ownership. If it's specifically the implication that netbooks are indecent that offends you, then replace "decent PC" with "the majority of personal computers or notebook purchased within the last 3 years at a cost of $500 or greater".

    2. Re:What is decent? by Quantumstate · · Score: 1

      I don't know what he means but I am running on an old (~7.7 years but I did upgrade the ram to 768mb) PC with Jaunty and the performance is more than adequate, also the hard disk I am using is a slow 10GB one becuase that is what I installed Ubuntu on, so the hard disk must be near 10 years.

  12. Re:Open Source FAIL *again*. by Tubal-Cain · · Score: 1

    Opera and Safari have rather low adoption rates. Acid3 compliance is purely a marketing gimmick until people actually implementing those features in real webpages. Opera and Apple decided that such a gimmick was a relatively fast and cheap way to get publicity, but we don't know what damage was incurred in the codebase(s) to make it happen.

    Few websites will use the final 7 tests until Mozilla or MS get around to it. Mozilla can afford to take it slow and implement the features properly, rather than tacking it on. MS obviously isn't in any hurry.

  13. Re:Open Source FAIL *again*. by Anonymous Coward · · Score: 0

    Gee, that's original. As if we haven't seen that same tired Ghandi quote hundreds of times before. Your creativity stuns us all. The video however, fails to impress. I guess you have to be a Linux geek with a chubby for OS advocacy to really get worked up watching it. What they don't tell you, is that while you're celebrating your pseudo-victory, we go right back to ridiculing you. You will never learn.

  14. Will they fix by Anonymous Coward · · Score: 0

    Will the fix either the spellchecker (which is supposed to be enabled automatically) or the documentation (which says it's supposed to be enabled automatically).

    Probably not - they're too busy adding support for XZXZXZXZRSSML 5.3.1.2.c. Still, I prefer it as a browser to IE, especially on forum type sites where IE is sloooooow, but the help & documentation are total babber.

    1. Re:Will they fix by Darkness404 · · Score: 1

      Errr... Having installed Firefox many different times, on many different releases, on many different platforms, I would have to say that at least for versions 3 and above (been forever since I have installed anything in the 2.X branch, but I think it was enabled by default then too), spellcheck is enabled by default.

      --
      Taxation is legalized theft, no more, no less.
  15. Re:Open Source FAIL *again*. by Anonymous Coward · · Score: 0

    Actually, it's going in reverse with open source:

    First you have a cool sounding idea to share source code and collaborate and you call it open source.

    Then they fight you because open source sounds like a good idea.
    Then they ridicule you because it actually fails in the real world.
    Then they ignore you because the only people who still believe in it are the zealots.

    And then you lose.

  16. Not quite RC yet by spinkham · · Score: 3, Informative

    This is actually a pre-RC build, the actual RC should be coming in the next week.
    See this site for more details.
    http://blog.mozilla.com/blog/2009/06/17/firefox-35-beta-users-will-receive-update-to-early-release-candidate/

    --
    Blessed are the pessimists, for they have made backups.
  17. Re:Open Source FAIL *again*. by zoips · · Score: 1

    Technically you have one non-beta closed source; Safari gets its 100% from Webkit, which is open source.

    Fed troll is fed.

  18. to heck with firefaux by FudRucker · · Score: 1, Interesting

    when firefox first started out it was ok, a lightweight alternative to Mozilla/Netscape but feature creep bloated it up that even Seamonkey runs just as good and even better in most cases than firefox so whats the point of firefox anymore, i rather just get seamonkey since it already has a built in email client, but for just a stand alone lightweight browser i been using dillo for a GUI browser and lynx for a console/cli text mode browser, besides it is the text is what i am after anyway, i could care less for plugins and graphical animations which is just kludge anyway that offer no insight & information anyway

    --
    Politics is Treachery, Religion is Brainwashing
    1. Re:to heck with firefaux by selven · · Score: 1

      substituting "fox" with "faux" is a level of fail reserved for american news (olds?) services.

    2. Re:to heck with firefaux by jpmkm · · Score: 1

      Faux does not rhyme with fox. You are not clever.

    3. Re:to heck with firefaux by RiotingPacifist · · Score: 1

      if your so happy about dillo and lynx why did you give enough of a shit about an alternative post?

      --
      IranAir Flight 655 never forget!
    4. Re:to heck with firefaux by Anonymous Coward · · Score: 0

      Actually, it is clever. It doesn't have to rhyme. The comedy is in the combination of the two words. You are simply too narrow minded to see it.

    5. Re:to heck with firefaux by jpmkm · · Score: 1

      Please explain how calling it Firefaux is clever or funny.

    6. Re:to heck with firefaux by Draek · · Score: 1

      And your point is...? good that you use Dillo, hopefully you'll contribute, I've heard they're kinda short on devs. Ohh, and if you want a more modern browser that's still fast, you should try Midori.

      There are options for every performance/features ratio you may prefer, its just that Firefox ain't on your particular favorite. The sky isn't falling.

      --
      No problem is insoluble in all conceivable circumstances.
    7. Re:to heck with firefaux by Anonymous Coward · · Score: 0

      Just as using "fail" instead of "failure" makes you look like a drooling and uneducated forum kiddie.

    8. Re:to heck with firefaux by alexborges · · Score: 1

      Well...

      Opinions are like um... yeah, you know.

      Ive tried opera once, this year, the latest and best of them and it seemed like the slowest thing Ive seen since mozilla pre 1.0.

      --
      NO SIG
  19. Re:Open Source FAIL *again*. by Simetrical · · Score: 1

    Another failure for Open Source. There are now TWO non-beta 100% fully ACID compliant CLOSED SOURCE browsers available (Opera and Safari). Why can't the "Open Source" community come up with something competitive?

    WebKit and Opera had 100/100 on the same day (March 26, 2008). WebKit is, of course, open-source. It's used by more than one open-source browser, including Chromium. WebKit and Chromium aren't developed solely by the stereotypical basement-dwelling hackers who communicate only over the Internet, but corporate-funded open source is still open source.

    By the way, "Acid" is not capitalized. Perhaps you're confusing it with the database concept of ACID compliance (atomicity, consistency, isolation, durability).

    --
    MediaWiki developer, Total War Center sysadmin
  20. Hold me closer, Private Browsing dancer! by WillAffleckUW · · Score: 1

    I can feel the power of Privacy growing, leaving no traces in History, no stored passwords, and telling Big Brother to go back to Cuba with his comrades like Yoo et al.

    Free at last!

    Thank d0g, I'm free at Last!

    --
    -- Tigger warning: This post may contain tiggers! --
  21. Turn off Geolocation! by Ian+Alexander · · Score: 1
    One of the upcoming features is a way for Firefox to send websites your location information based on a best-guess provided by Google (or your location-guesser of choice) once you've expressly okayed it. From the sound of it they try to extrapolate based on nearby wi-fi hotspots and your IP address.

    This isn't really the kind of information I would like to share, and I imagine other people might not like it either, so to just disable it so you won't even be asked, do the following:
    • go to about:config
    • Change the "geo.enabled" preference to false

    All information summarized (read: stolen wholesale) from http://www.mozilla.com/en-US/firefox/geolocation/

  22. What's the all fuss about the test results about? by CosmicRabbit · · Score: 1

    I don't get the problem of the test showing you a distorted image. If you're seeing it on Acid, what would you expect?

  23. I wish javascript links by Anonymous Coward · · Score: 0

    would open in new tabs like they do in Opera.

  24. No one even notice? by NervousNerd · · Score: 1

    No one even notice the new Firefox icon?

    1. Re:No one even notice? by TheDreadedGMan · · Score: 1

      Yep I noticed it however windows doesn't always refresh the short cut icons immediately so some might have missed the new shiny icons.

      If you're on Windows XP or similar and it has not refreshed the icon just go to the shortcut properties and click change icon and click ok... it will update automatically.

  25. CORRECT LINK by Anonymous Coward · · Score: 0

    Here is the RC1 link:

    http://www.mozilla.com/en-US/products/download.html?product=firefox-3.5rc1&os=win&lang=en-US

    All I did was change "?product=firefox-3.5b4" to "?product=firefox-3.5rc1" and it worked. You'd be surprised what you can find by guessing URLs.

    Enjoy.

  26. Re:H.264 or Theora? by Anonymous Coward · · Score: 0

    I guess one moderator was afraid of the truth.

  27. Figures. by adolf · · Score: 1

    I just installed beta4 late last night/early this morning. Hadn't even had a chance to fire it up yet.

    I'll go update it to RC1 straightaway, so we can move on with RC2 tomorrow.

    (You're welcome.)

    1. Re:Figures. by mr_mischief · · Score: 1

      Just because you're weeks to months behind a beta cycle doesn't give you some reason to bitch. If you don't like testing or the speed of development, then stick to releases.

  28. Re:H.264 or Theora? by armanox · · Score: 3, Insightful

    Since when is H.264 industry standard?

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  29. Re:H.264 or Theora? by Ilgaz · · Score: 4, Interesting

    H264 is industry standard since the day it was proposed/accepted. Industry standards aren't defined by nerds, they are defined by industry, huge boards of professionals and several computing specialists. There are billions (if not trillion) worth of broadcasting equipment, workflows, applications trusting to MPEG standards. Near all HD broadcasts are h264 and you should be thankful that TV industry didn't buy Microsoft's "but VC1 is documented too!" tricks.

    They sit, argue, propose and after years, MPEG standards appear. H264, being part of MPEG 4 is more standard than anything you can imagine. It is result of 300 Experts discussions, several universities, companies and even governments.

    Of course, it would be wise to wonder around saying "evil patents and mpeg la" but reality is a bit different. Even the reasons of patents are different than you may think.

  30. Similar issues on OS X, no .PKG by Ilgaz · · Score: 1

    In fact, even home users using OS X lives problem with "Drag Drop" installs if they aren't admin (super user) and the poor Finder's architecture of "if not owned by user, prompt" functionality is being relied on.

    OS X is generally clever on that area but just moments ago, it stopped at half eventually giving up replacing the .app directory (which we see as Firefox.app) breaking the working executable.

    If it was a .pkg, OS X would launch its Installer.app, it would nicely ask for admin credentials, store the app in "user neutral" way (not in uid of the admin dragging it) and store its metadata at /Library/Receipts. It doesn't do "healing" etc. yet but large Mac networks admins end up creating "Firefox.pkg" themselves just like you for similar reasons.

    Really interesting is, they also give up the best feature of MSI. If you do it right, it can even "heal" the overwritten or missing files right? It really matters to home users.

  31. Re:Open Source FAIL *again*. by maglor_83 · · Score: 1

    You mean the Safari that uses the open source WebKit for rendering?

  32. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  33. 93/100 on the Acid3 test by r45d15 · · Score: 1

    For a web developer 93/100 is more than enough, such a (high) score is well suited to do everything you'd expect from a modern browser. The need to hit 100% is overrated, if you're a web developer you know what I mean. Firefox takes the approach of "what really matters" to web developers and users and that is not only passing the acid 3 test but also "next-generation" (HTML5) features like web workers (threads), native video, animated SVGs, Canvas and other stuff that other browser(s) that hit 100/100 aren't yet able to do for now, but which is much more welcome than the remaining 7% of the acid test.

  34. Re:A little Opera Music with a bad note by TaoPhoenix · · Score: 1

    Like my private links page.

    It's a simple little page with about two layers of tables, and one of the recent Opera builds pounds it. (I think the one before last week's release.)

    So now I don't know if it's because my page isn't Standard Compliant or if Opera is just throwing a snit.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  35. Re:H.264 or Theora? by Anonymous Coward · · Score: 1, Informative

    Near all HD broadcasts are h264 and you should be thankful that TV industry didn't buy Microsoft's "but VC1 is documented too!" tricks.

    No HD broadcasts in the US are H.264, unless you're defining that term completely differently from I do.

  36. Re:A little Opera Music with a bad note by Just+Some+Guy · · Score: 1

    W3's HTML validator is a good place to start researching.

    --
    Dewey, what part of this looks like authorities should be involved?
  37. Not everyone trusts Flash, thank god by Burz · · Score: 1

    Or thank NoScript, rather.

    Flash is now a significant malware vector.

  38. Re:Open Source FAIL *again*. by mr_mischief · · Score: 2, Informative

    Safari's renderer is WebKit, which is open source and based on KHTML.

  39. Re:H.264 or Theora? by SpookyFish · · Score: 1

    Yup. Broadcast (ATSC) uses Mpeg-2. However both DirecTV and Dish use h.264 for many of their HD channels. That's why old DirecTiVo HDs miss out on a lot of programming.

  40. Re:H.264 or Theora? by armanox · · Score: 1

    My point was - if it is an industry standard, then why don't I see it used anywhere I go? Not at home, work or school (and MP4 != H.264).

    --
    I'm starting to think GNU is the problem with "GNU/Linux" these days.
  41. Re:H.264 or Theora? by Ilgaz · · Score: 1

    It is used in HD Broadcasts, you don't see it get used, it is the satellite/set top box/device doing the h264. DVB-T and DVB-S (HD) are all in h264 and the container is always MPEG, in some form. VC6 (Theora) can't do the job H264 does. It is all about the bandwidth you can grab from satellite and H264 excels at giving very good quality in fraction of bandwidth MPEG4 SP would provide. It really matters to the 3G stuff too as you only rely on a single codec with several different bandwidths. It is more like ARM architecture and powerpc and even Motorola 68K, it is everywhere but you don't spot it.

    If h264 didn't exist, there was no other standard than Microsoft VC1 to rely on for such uses. It would be a real disaster, way more than "patented" issue. I agree to the concerns about the MPEG LA and patents but just think what would happen if Microsoft, as a single company had reach of H264 with their VC1.

    MP4 is the container, based on Quicktime standard and it is doing really well IMHO. Everyone, including pirates (which really matters) picked it except the ones using MKV container which really has full potential to be a standard but, because of its "image" and some political reasons at EBU/FCC, it would never be.

  42. Re:H.264 or Theora? by Ilgaz · · Score: 1

    They must have some great bandwidth to spare. MPEG2 is of course usable in HD broadcast but it requires massive bandwidth compared to MPEG 4 SP (think like Quicktime plain Mpeg 4) and H264.

    It is all about bandwidth actually, it is not "old tech" vs. "new" or anything. Also the way TV industry works matters. They will never change a thing unless some definately needed feature is required and can't be built on existing technology. That is why PAL/NTSC standards still lives today since 1950-60 period.

  43. Re:H.264 or Theora? by imroy · · Score: 1

    Just to nitpick, but the video codec is standardised by both MPEG and ITU. The "h.264" (lowercase 'h' followed by a period) name that everyone has latched onto is used by the ITU. In the MPEG world, it is known as MPEG-4 AVC (advanced video codec) or formally, MPEG-4 Part 10.

  44. Re:H.264 or Theora? by Ilgaz · · Score: 1

    Oh yes, but thanks to Apple factor (who is also responsible for mpeg4 take off), everyone sticks with h264 now.

    They can't even understand the difference between mpeg4 SP and mpeg 4 ASP and why it matters/mattered. Thanks to Apple (!) for not supporting the ASP in default quicktime mpeg4, people barely seen a full feature (like 3ivx) MPEG4 and when they saw H264, they thought it is a new thing and as SJobs introduced it as h264, name sticked.

    In fact, it could be the reason why some people think h264 is not a standard, because of not having "mpeg" in the name and being promoted by Apple first.

  45. Re: Validator by TaoPhoenix · · Score: 1

    Yea, I'd known about that but this morning I finally spent a few hours to switch my page over to microsteps of style type. Now I have a clean 4.01 Transitional rating. Yay!

    I'll check the page again at work to see if Opera is still giving me fits or not.

    I'll also have to put that page back on my resource links now I know how to get clean readings.

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine