Slashdot Mirror


Firefox 4 Beta 1 Shines On HTML5

snydeq writes "InfoWorld's Peter Wayner takes a first look at Firefox 4 Beta 1 and sees several noteworthy HTML5 integrations that bring Firefox 4 'that much closer to taking over everything on the desktop.' Beyond the Chrome-like UI, Firefox 4 adds several new features that 'open up new opportunities for AJAX and JavaScript programmers to add more razzle-dazzle and catch up with Adobe Flash, Adobe AIR, Microsoft Silverlight, and other plug-ins,' Wayner writes. 'Firefox 4 also adds an implementation of the Websockets API, a tool for enabling the browser and the server to pass data back and forth as needed, making it unnecessary for the browser to keep asking the server if there's anything new to report.'"

256 comments

  1. Peter Wayner by tyrione · · Score: 3, Funny

    He's living in a cloud if he thinks it's going to ``take over everything on the desktop.''

    1. Re:Peter Wayner by Anonymous Coward · · Score: 3, Funny

      I left a cloud on your mom's desktop last night.

    2. Re:Peter Wayner by Anonymous Coward · · Score: 0

      Did the Peter really write "razzle-dazzle"?

      And good thing about that web sockets API. I don't know why web browser makers didn't think bfore about the need to pass data back and forth between them and the server.

    3. Re:Peter Wayner by jemtallon · · Score: 3, Funny
    4. Re:Peter Wayner by Monkeedude1212 · · Score: 2, Interesting

      Famous last words.

      Well no... okay okay okay... I see what you're saying, there's no way Firefox could possibly take over EVERYTHING on the desktop, there are many things that operate outside of applications.

      However, for what most people use a computer for, a web browser does most of it. Email? Who here has an email address and check it using their favourite browser. I know I've got a hotmail and a gmail. Surfing the web? Thats a given. Aside from games, what do most people do on computers? Word processing, spreadsheets, there is some work-y kind of stuff. But more and more stuff is being moved to the cloud (for better or worse, its happening). Eventually, it might reach a point where its standard to have your documents backed up online in a service like Google Docs, and then before you know it your word processor is an Addon or plugin bundled into Firefox.

      Firefox has that flexibility in it that allows for more customization, which is one of the areas Internet Explorer lacks most (I'll compare it to IE since IE has a lot of market share). It also has that community behind it, in a way that
      1)That there are a lot of people who use it, just for the sake of not being stuck to IE
      2)There are a lot of people who develop for it, just because its the most popular alternative out there
      3) There are a lot of people who use it, and provide useful feedback to those who develop for it.

      All in all, even if you don't always like the course Firefox takes (some people complain its getty bogged down), its at least in the most healthy environment imaginable to change. IE, being in that tough spot of "All these businesses use Internet Explorer, we better not screw up" doesn't have the ability to try things out as much as Firefox does.

      So - all in all, don't be surprised if the browser thats best suited for new standards (if Firefox beats IE at HTML5) ends up gaining a lot of momentum in this technological shift we're seeing lately.

    5. Re:Peter Wayner by Hatta · · Score: 4, Insightful

      Because the hypertext transfer protocol was designed to transfer hypertext documents. It was not designed to be a remote application protocol.

      --
      Give me Classic Slashdot or give me death!
    6. Re:Peter Wayner by Anaerin · · Score: 1

      Isn't it called XMLHTTPRequest (ca. 2000)? Or, if you want to go even older-school, frames (ca. 1998), or HTTP Server Push (ca. 1996, http://en.wikipedia.org/wiki/Push_technology#HTTP_server_push)

    7. Re:Peter Wayner by Anonymous Coward · · Score: 0

      No. Web Sockets was added specifically to address the shortcomings of XMLHTTPRequest.

      (That wouldn't have taken you long to find out if you tried, but I guess you were too busy telling Slashdot how much smarter than everyone else you are.)

    8. Re:Peter Wayner by RobertM1968 · · Score: 0

      No. Web Sockets was added specifically to address the shortcomings of XMLHTTPRequest.

      (That wouldn't have taken you long to find out if you tried, but I guess you were too busy telling Slashdot how much smarter than everyone else you are.)

      And hopefully wont create a lot more when a certain web browser improperly (if at all) supports it, or uses it as a tool to push people to .NET instead (Embrace, Extend... yeah, you know the rest).

      Every time some new advance comes out for the web, I get scared something like that will happen, that, at the least, will make any web developer's life a nightmare. So far, Microsoft has not let me down.

    9. Re:Peter Wayner by Peach+Rings · · Score: 1

      Yep, and web browsers are supposed to render web pages, not MathML and XPath and SVG, but try telling that to the Gecko devs.

    10. Re:Peter Wayner by RobertM1968 · · Score: 1

      And fortunately, Microsoft is onboard with this:

      For the client side, WebSocket is implemented in Firefox 4, Google Chrome 4, and Safari 5.

      Internet Explorer 9 is supposed to feature Web Sockets at some point according to Microsoft (before the stable release).

      Waiting with baited breath.

    11. Re:Peter Wayner by Requiem18th · · Score: 2, Insightful

      I'd argue that MathML and SVG have a very proper place as components of a Hypertext Document, I don't know why are you talking about XPath.

      --
      But... the future refused to change.
    12. Re:Peter Wayner by holloway · · Score: 3, Insightful

      Because the hypertext transfer protocol was designed to transfer hypertext documents. It was not designed to be a remote application protocol.

      Irrelevant. If it can be evolved to work well enough for people then it is suitable. The Type-III Secretory Gland evolved into the Bacterium Flagellum without any design, but it happened to work well enough to survive and so it did.

      Design helps cause effects but it doesn't prevent useful side-effects.

    13. Re:Peter Wayner by tenco · · Score: 1

      MathML can be part of an XHTML document. Dunno what XPath is, but chances are it's part of HTML5 like the rest.

    14. Re:Peter Wayner by AkaXakA · · Score: 1

      Yeah, and these images, blech! When can we get rid of them?

    15. Re:Peter Wayner by Requiem18th · · Score: 2, Interesting

      But what's the point of installing a word editor as a pluging? Just install OpenOffice.org already, it will do more and run faster than anything firefox can offer(, yes it's Java but firefox is *Javascript* which is slower still).

      The beauty of web apps is noth that they can be installed as plugins but that they are accessible from any platform with a browser. From your PC to your phone to your gaming console, to your plane sit, to your toilet, if you live in Japan.

      Any web-enabled machine becomes your desktop with just a login.

      If an application requires you to install it as a firefox pluging, how are you going to use it in your car's gps?

      --
      But... the future refused to change.
    16. Re:Peter Wayner by Derleth · · Score: 1

      It also was not designed to display images, or replace Gopher, or become one of the major foundations of the modern economy.

      Funny how things work out, isn’t it?

      --
      How can you use my intestines as a gift? -Actual Hong Kong subtitle.
    17. Re:Peter Wayner by DragonWriter · · Score: 1, Interesting

      Because the hypertext transfer protocol was designed to transfer hypertext documents. It was not designed to be a remote application protocol.

      That's true, if at all, only of the original, GET-only version of the HTTP protocol as supported by the first WWW prototype implementation ("HTTP 0.9".)

      Its certainly not true of HTTP/1.1 which is a generic distributed object-manipulation-and-access protocol following REST principles.

       

    18. Re:Peter Wayner by icebraining · · Score: 2, Insightful

      or uses it as a tool to push people to .NET instead

      .NET in the browser only with Silverlight, and that already had normal sockets.

    19. Re:Peter Wayner by icebraining · · Score: 2, Informative

      yes it's Java

      Where does this myth come from? Most of OOo is written in C++, and even many parts written in Java are compiled to machine-code using GCJ. The only parts of OOo that require a JRE (Java interpreter/JIT compiler) are:
              * the media player on Unix-like systems
              * all document wizards in Writer
              * accessibility tools
              * Report Autopilot
              * JDBC driver support
              * HSQL database engine (used in OpenOffice.org Base)
              * XSLT filters
              * BeanShell, the NetBeans scripting language and the Java UNO bridge
              * export filters to the Aportis.doc (.pdb) format for the Palm OS or Pocket Word (.psw) format for the Pocket PC
              * export filter to LaTeX
              * export filter to MediaWiki's wikitext

    20. Re:Peter Wayner by Nutria · · Score: 1

      baited breath

      You're using you breath to lure animals?

      --
      "I don't know, therefore Aliens" Wafflebox1
    21. Re:Peter Wayner by GaryOlson · · Score: 1

      Bait may be used to lure more than animals...
      Looks to me like he is trapping for Microsofties. I am really curious what type of bait he uses.

      --
      Every mans' island needs an ocean; choose your ocean carefully.
    22. Re:Peter Wayner by Hatta · · Score: 1

      It is relevant, as it explains why we've had to wait until now for a mechanism to push events from the server, which is what the parent asked about. It also explains why the browser has so far sucked as an application platform. Hopefully web sockets will do something to alleviate that.

      --
      Give me Classic Slashdot or give me death!
    23. Re:Peter Wayner by Nadir · · Score: 1

      > * the media player on Unix-like systems

      This is being replaced with GStreamer: http://www.linuxjournal.com/content/openofficeorg-use-gstreamer-multimedia

      --
      --
      The world is divided in two categories:
      those with a loaded gun and those who dig. You dig.
    24. Re:Peter Wayner by oztiks · · Score: 1

      Yeah but like everything HTML its going to be a part of a mass conglomerate of attempted standards practices quietly manipulated by the each browser vendor.

      To this day we still have to hack websites to work for individually for IE8, Safari/Chrome, Firefox. HTML5 isn't going to impose a solution to this, if anything we are years away from seeing any of these shortcomings you speak of disappear. As for Web Sockets, its yet another object of objects to add to the list .... "do we support this? no then do we support this? no, how about this? yep okay use ActiveXObject"

      HTML5 is a good concept and too see it flourish is going to be pinnacle to my work, but alas I'm a cynic and lost faith with standards and compliance years ago (not that I'll ever make a website that _isn't_ strict complaint) but my iPad is a perfect example of how everything still wont render friendly. It mulls up font-types and screws up javascript code and every now and then. Now with each browser competing to be "more compliant" than its competitor, it gives the excuse to developers to worry about less and implementing less backward compatibility.

      Not something I'm afraid of, I get to make up for it in all the billable hours on fixing broken websites. But it's falls in the same computing issues the world has seen time and time again, security and legacy working to destroy whats new (or vice-versa). What needs to happen is we need a more abstract approach to this legacy trump and put some sort of middleware on the web servers that can solve these issues for developers and track this standards garble the browsers play at.

    25. Re:Peter Wayner by the_womble · · Score: 1

      The most important thing is that docx import depends on Java - I used to have Java turned off until that became an issue.

      Of course, the fact that OO contains an option to turn off Java ought to be a clue that it is not written in Java.

    26. Re:Peter Wayner by Anonymous Coward · · Score: 1, Informative

      And what exactly is a Type III Secretory gland? Gland? SInce when did bacteria get glands? Bacterial type III secretion systems are a protein complex typically used to inject proteins into a host cell. A gland is a hormone secreting organ found in animals. More different they could not be...

    27. Re:Peter Wayner by RobertM1968 · · Score: 1

      Bait may be used to lure more than animals... Looks to me like he is trapping for Microsofties. I am really curious what type of bait he uses.

      Silly question!!!! Hype, FUD and Vaporware of course!!! ;-)

    28. Re:Peter Wayner by RobertM1968 · · Score: 1

      or uses it as a tool to push people to .NET instead

      .NET in the browser only with Silverlight, and that already had normal sockets.

      Not even commenting on the fragmentation issue that .NET functionality will have for other platforms if MS has their way (and follows their standard planbook), why would .NET, with it's plethora of security issues since day one till now, be a viable solution? And what about .NET makes it truly cross platform like HTML5 is planned on being? Can one use all of the .NET capabilities and functions on MacOSX and Linux and eComStation? And of those capabilities that can be used, for how much longer before Microsoft changes something and loses interest in other platforms? Their consent decree (forcing them to release info on how to interoperate with these communications protocols) has expired. Or did anyone think it was some sort of altruism on their part, or some sort of real effort to support the open source community?

    29. Re:Peter Wayner by not+already+in+use · · Score: 1

      The Type-III Secretory Gland evolved into the Bacterium Flagellum without any design

      Unfortunately, standardized web protocols don't evolve in the same manner as organic matter. The GP's point remains completely valid. Doing these kind of things over HTTP remains one of the most widely used hacks.

      --
      Similes are like metaphors
  2. Have I missed any? by Pojut · · Score: 2, Funny

    ::grumble grumble:: Memory leak
    ::grumble grumble:: Bloated
    ::grumble grumble:: Not nearly as good as it once was
    ::grumble grumble:: Most development money comes from Google
    ::grumble grumble:: Not as good as Gecko/Opera/Safari/Chrome/etc

    1. Re:Have I missed any? by silverkniveshotmail. · · Score: 3, Interesting

      ::grumble grumble:: Memory leak
      ::grumble grumble:: Bloated
      ::grumble grumble:: Not nearly as good as it once was
      ::grumble grumble:: Most development money comes from Google
      ::grumble grumble:: Not as good as Gecko/Opera/Safari/Chrome/etc

      Plugins?

    2. Re:Have I missed any? by Anonymous Coward · · Score: 1, Interesting

      Have you tried this beta? For me, memory usage has gone down tremendously over previous versions.

    3. Re:Have I missed any? by KiloByte · · Score: 2, Funny

      Plugins?

      Why do you refer to Flash in plural?

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
    4. Re:Have I missed any? by Anonymous Coward · · Score: 2, Informative

      ::grumble grumble:: Not as good as Gecko/Opera/Safari/Chrome/etc

      Gecko is the rendering engine of Firefox.

    5. Re:Have I missed any? by Anonymous Coward · · Score: 0

      ::grumble grumble:: Most development money comes from Google

      what the fuck has that got to do with anything?

    6. Re:Have I missed any? by Pojut · · Score: 3, Funny

      That's a weird way to spell "woosh"...

    7. Re:Have I missed any? by Pojut · · Score: 0, Troll

      I have no idea, ask the people that cite it as a reason Firefox sucks.

      In case you missed it (which you apparently did), I was poking fun at people who find Firefox so abhorrent that a piece of software borders on offending them.

    8. Re:Have I missed any? by Anonymous Coward · · Score: 0

      Ask the folks that grumble about it. The parent is innocently preempting their grumbling.

    9. Re:Have I missed any? by Anonymous Coward · · Score: 0

      I have no idea, ask the people that cite it as a reason Firefox sucks.

      In case you missed it (which you apparently did), I was poking fun at people who find Firefox so abhorrent that a piece of software borders on offending them.

      Well I've yet to see money from Google being used as a reason to avoid Firefox ... if anything that sort of money backed support (yet still open source) is reason to flock to Firefox.

    10. Re:Have I missed any? by Anonymous Coward · · Score: 0

      ::grumble grumble:: Memory leak
      ::grumble grumble:: Bloated
      ::grumble grumble:: Not nearly as good as it once was
      ::grumble grumble:: Most development money comes from Google
      ::grumble grumble:: Not as good as Gecko/Opera/Safari/Chrome/etc

      ::grumble grumble:: still not available as a suppository

    11. Re:Have I missed any? by mrsteveman1 · · Score: 1

      rabble rabble rabble.

      rabble!

    12. Re:Have I missed any? by JamesTRexx · · Score: 1

      For me it would be;
      New tabs opening right next to the current tab
      Tabs on top now!? *grumble grumble hissyfit grumble rant on /.*

      --
      home
    13. Re:Have I missed any? by Anonymous Coward · · Score: 1, Informative

      You can also view memory usage in detail by putting this into the location bar:

      about:memory

    14. Re:Have I missed any? by Khyber · · Score: 1, Interesting

      ::grumble grumble:: fixing a fucking FACEBOOK flaw instead of focusing on security.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    15. Re:Have I missed any? by Dishevel · · Score: 1

      I have seen it. Here on /. too.

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    16. Re:Have I missed any? by Monkeedude1212 · · Score: 1

      I believe you left out ::grumble grumble:: bugzilla is no help, everyone still ignores me

    17. Re:Have I missed any? by blair1q · · Score: 1

      Because Flash it also comes in Adblock configuration, which is handy for when you want to disable the default configuration.

    18. Re:Have I missed any? by blair1q · · Score: 3, Informative

      Both of which can be disabled using about:config settings.

    19. Re:Have I missed any? by andrewd18 · · Score: 1

      I believe you left out ::grumble grumble:: bugzilla is no help, everyone still ignores me

      WORKSFORME

    20. Re:Have I missed any? by kobaz · · Score: 1

      You missed: ::grumble grumble:: Crashy

      Beta 4 crashes any time I right click on a link
      It crashes any time I load a new plugin
      It crashes any time I open a new tab

      --

      The goal of computer science is to build something that will last at least until we've finished building it.
    21. Re:Have I missed any? by JamesTRexx · · Score: 0, Redundant

      Get off my lawn!

      :-P

      --
      home
    22. Re:Have I missed any? by blazerw · · Score: 1

      It crashes...

      Wow! For me, Firefox never crashes. Even on Windows.

    23. Re:Have I missed any? by Goaway · · Score: 1

      Yes, there is ONE PERSON working on Firefox, and when he has to take the time out of the day to fix Facebook, nothing else gets done!

    24. Re:Have I missed any? by X0563511 · · Score: 1

      IE offends me. Would you poke fun at me for it?

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    25. Re:Have I missed any? by lennier · · Score: 3, Funny

      And you should see what happens when he has to harvest his Farmville.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    26. Re:Have I missed any? by X0563511 · · Score: 1

      WONTFIX|INVALID

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    27. Re:Have I missed any? by Anonymous Coward · · Score: 0

      Dear Kobaz,

      You must be holding it wrong.

      ~Steve

    28. Re:Have I missed any? by icebraining · · Score: 3, Informative

      You don't need about:config for the Tabs on top config:

      "To disable the tabs from the top position, click on the Firefox button on the top left corner. From the menu, click Customize-> Tabs on top. Uncheck the box against "Tabs on top"."

    29. Re:Have I missed any? by icebraining · · Score: 1

      A Beta version of an app is unstable! Stop the presses!

    30. Re:Have I missed any? by bunratty · · Score: 1

      You left out
      ::grumble grumble:: Slow
      ::grumble grumble:: Crashes
      ::grumble grumble:: Freezes
      ::grumble grumble:: Security vulnerabilities
      ::grumble grumble:: Too many updates
      ::grumble grumble:: Too few updates
      ::grumble grumble:: Smells funny

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    31. Re:Have I missed any? by Runaway1956 · · Score: 1

      From the book of Nlite, Chapter 1, verse 0, "If thine IE offend thee, pluck it out!"

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    32. Re:Have I missed any? by perryizgr8 · · Score: 1

      you might want to return your pc and ask for a new one. if it were that crashy, moz wouldn't have released it as beta. hell, even the nightlies are not THAT crashy.

      --
      Wealth is the gift that keeps on giving.
    33. Re:Have I missed any? by perryizgr8 · · Score: 1

      It crashes...

      Wow! For me, Firefox never crashes. Only on Windows.

      ftfy.
      i say this because firefox has grown to be utterly slow and unresponsive on linux (any distro) these days. on windows it is fast enough that i don't care about any more speed. but it becomes 'not responding' on linux mint for 10-15 seconds every time i open a slashdot discussion.

      --
      Wealth is the gift that keeps on giving.
    34. Re:Have I missed any? by Khyber · · Score: 1

      Since you can't understand, I'll explain.

      That timing thing they 'fixed' to make farmville work, stopped everything that *WAS* working properly with our test rollout of firefox across our corporate network.

      That very move just got Mozilla blacklisted and banned from our corporate networks, and I had to spend five hours rolling back every bench to IE.

      FUCK MOZILLA.

      Posting using Chrome, now. I removed Firefox from my system because that change makes me unable to work from home.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    35. Re:Have I missed any? by Randle_Revar · · Score: 0

      what

    36. Re:Have I missed any? by kobaz · · Score: 1

      Nothing else crashes... just firefox

      --

      The goal of computer science is to build something that will last at least until we've finished building it.
    37. Re:Have I missed any? by Randle_Revar · · Score: 1

      Modding me down? why? I feel that was a very relevant response to a sentence like this:

      "Because Flash it also comes in Adblock configuration, which is handy for when you want to disable the default configuration."

      The dang thing just doesn't parse.

    38. Re:Have I missed any? by Kitsune+Inari · · Score: 1

      Uh... excuse me, but would you be so kind as to rephrase your statement? This time, if possible, in a language we can understand, please.

    39. Re:Have I missed any? by Ash+Vince · · Score: 1

      That timing thing they 'fixed' to make farmville work, stopped everything that *WAS* working properly with our test rollout of firefox across our corporate network.

      Since this is technical discussion site would you care to flesh your post out with any details of why this happened and why this fix broke your test rollout across your corporate network? You post doesn't really provide any information to back up your point.

      Oh, and try taking a valium or something, swearing at an application strikes me as being a little high strung :)

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
    40. Re:Have I missed any? by thePowerOfGrayskull · · Score: 1

      That's a weird way to spell "woosh"...

      So whas that...

    41. Re:Have I missed any? by Khyber · · Score: 1

      "Since this is technical discussion site would you care to flesh your post out with any details of why this happened"

      Our security for timeouts was linked to that timing in Firefox. Firefox changed it to fix Facebook, broke our timing-based security.

      That's about as in-depth as I can go without beginning to reveal details about our infrastructure, which is against NDA.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    42. Re:Have I missed any? by Ash+Vince · · Score: 1

      Our security for timeouts was linked to that timing in Firefox. Firefox changed it to fix Facebook, broke our timing-based security.

      So you were relying on firefox timing out non-responsive flash apps after 10 seconds and them changing it to time them out after 45 seconds broke your timing based security? Thats sounds a bit far fetched.

      If it really is the case then I would suggest you take a good look at what you are doing and try and figure out a better way of achieving it without being reliant on a plugin being closed or reloaded after 10 seconds. To be honest though this whole things sounds completely bogus as the version of firefox before they implemented this never timed out a non-responsive plugin, it just left it up to the user to close the browser.

      http://mashable.com/2010/06/28/firefox-3-6-6-farmville/

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
  3. Firefox needs better support for security tokens. by elucido · · Score: 2, Insightful

    Firefox needs to have better built in support for Ironkey, smartcards and security tokens. So we can once and for all switch away from passwords.

    If Firefox actually supports security tokens, it's not very intuitive.

  4. Re:Does what to HTML 5? by Pojut · · Score: 5, Funny

    At any rate, lets all change the standards again, so all those old computers that can't run anything later than Firefox 2 have to be shipped off to some foreign dump where they leak poisonous chemicals in to the drinking water.

    It's the American way.

  5. Re:Does what to HTML 5? by beelsebob · · Score: 3, Insightful

    Yes, lets all live in 1999, so that you can continue to use your shitfest of a computer.

  6. Its too bad the UI got messed up by Burz · · Score: 5, Insightful

    Mozilla and Google have got this one WRONG:

    Merging the address and search fields is a big drawback. It further confuses people about what a URL is, and it encourages them and others (esp. advertisers) to give directions to web sites as if the keywords == addresses. (Hey, like AOL!)

    If this trend continues, we'll have shenanigans and lawsuits claiming that "squatters" are using keywords on their pages that "belong to us". It will open another "IP" can of worms.

    Encouraging people to rely on keywords also opens them up to phishing big time. It's like having them clean their teeth with their enema: Very semantically dirty!

    1. Re:Its too bad the UI got messed up by Haffner · · Score: 1
      You can't deny its convenience - plus, Firefox is not a default browser on any OS run by people who can't make that distinction.

      Then again, to play devil's advocate it is nice being able to see the terms you searched for in the same page. Plus, it also doubles as a way to save a string of text without opening up anything else.

      --
      "Going to war without the French is like going deer hunting without your accordion." ~General Norman Schwarzkopf
    2. Re:Its too bad the UI got messed up by blair1q · · Score: 4, Insightful

      well, no, actually, that's a good thing.

      URIs have become cumbersome. Making the net content-addressable is a big efficiency measure.

      You can still give out a key that will only map to you, and return a URI that is clearly you. Or at least as clearly as happens now when someone does a Google search.

      But now you're not constrained to identifying yourself with some bogus fqdn with a limiting TLD stuck on it.

      As for Phishing, banks have moved to authentication systems that use graphics on the page to tell you that the password-entry box you're looking at is legit. If you don't see your predetermined secret glyph, you don't enter your password. And the glyph isn't sent until your browser and the server are connected by SSL, so it can't be sniffed and hacked into a phishing site. And it isn't sent unless your browser already has a cookie identifying it as having been validated previously, using a secret-question protocol. If you deleted the cookie, you go through the secret-question routine again.

      Short of adding more layers of such things, or using in-person pre-validated biometrics over secure links, you're not getting much more security than that on the internet. Using simple, recognizable URIs won't help you, and really, just invites social engineering based on URIs that look almost legit.

    3. Re:Its too bad the UI got messed up by sweatyboatman · · Score: 4, Insightful

      Your posts defines two distinct categories: URLs and Search Terms. Most people don't think about those things as separate ideas. They're just means of telling the internet to show a website.

      The key distinction between a URL and a search term is that URLs are hard to remember and prone to typos. Search terms are far easier (and tend to be helpful even if you spell them wrong). why would I want to type in "http://krugman.blogs.nytimes.com/" when I can just type in "krugman" (or "krugrman") and get my daily Keynesian economic analysis that way.

      For the browser, the URL and the search term are completely distinct. For an engineer or a software programmer, it's clear why they would have separate fields for entry of one or the other.

      But for a user (even a technically savvy user) semantic cleanliness doesn't make any sense and causes more problems than benefits.

      --
      It breaks my pluginses, my precious!
    4. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 3, Insightful

      All is good as long as I can disable search from the toolbar.

    5. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      While I agree with you in principle, the sad truth is, most people cannot navigate the Web without Google. Nobody remembers URLs anymore. Nobody even uses their browser's bookmarks feature anymore. People just use Google for everything and anything.

    6. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 2, Insightful

      Uh, the method you described does almost nothing to stop phishing. Doing a man-in-the-middle on it is trivial, so really all it does it is require the phisher to handle each bank separately... which they probably have to do anyway in order to make their sites look the same. The only trip-off to the user would be an extra security question being asked, which no one will notice because banks randomly ask those security questions anyway.

    7. Re:Its too bad the UI got messed up by SatanicPuppy · · Score: 2, Insightful

      Yea, and it'll also reduce the incentive for people to squat and typo-squat domain names.

      I'm frankly tired of all that crap: if ICANN wants to deal with the rampant squatting, I'll start supporting "address bar for addresses only" thinking. Until then, I'd rather google hijack me to a meaningful result than accidentally direct myself to some damn squatter site.

      --
      ad logicam Claiming a proposition is false because it was presented as the conclusion of a fallacious argument.
    8. Re:Its too bad the UI got messed up by PhxBlue · · Score: 2, Insightful

      Grandma doesn't care what a URL is, only that she can get to the sites she needs. If Firefox 4 is intuitive to her, then it doesn't owe me any apology.

      --
      !#@%*)anks for hanging up the phone, dear.
    9. Re:Its too bad the UI got messed up by starfishsystems · · Score: 1

      Couldn't agree more. There is no need to engineer in favor of computer illiteracy.

      --
      Parity: What to do when the weekend comes.
    10. Re:Its too bad the UI got messed up by camcorder · · Score: 1

      Your grandma should use a device designed for her age then. Stop thinking PC usage based on grandmas anymore. That's not 90s. Current generation is growing with computers, and they should be intelligent enough to know and grasp the basics of computing.

    11. Re:Its too bad the UI got messed up by Kaboom13 · · Score: 4, Interesting

      Firefox started as the browser that wasn't for your grandma. It had rough edges, pages didn't always display properly, but it was fast and tabbed an light weight with an installer in the single digits. This is how it grew it's user base, Trying to shoehorn it into the browser for grandma is retarded (Chrome already is better for that, by a good margin). Fuck your grandma, I don't want to use the best browser for your grandma. Our requirements are completely different. I want Firefox to be the best browser for me. I want separate url and search fields because I know exactly what I am trying to accomplish. If I want to stick some search terms through google I will, if I want to go to slashdot.com instead of slashdot.org I had a specific reason. I want the url bar to make a best effort at turning what I entered into a working url with as little guessing as possible and run with it.

      Let chrome be the browser for grandma, they have the resources and the marketing power behind them. Leave Firefox pure to the roots it came from, and focus on technical aspects. If people want to change the ui, the wonderful extension system lets them do just that.

    12. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 1, Informative

      Firefox 4 still has separate address and search fields.

    13. Re:Its too bad the UI got messed up by Nethead · · Score: 1

      Mod this AC up.

      --
      -- I have a private email server in my basement.
    14. Re:Its too bad the UI got messed up by theswimmingbird · · Score: 2, Insightful

      Definitely. I love having them separate. Besides, even my netbook has a resolution of 1366x768. Who needs an address bar that's over a thousand pixels wide? I mean, really. So much of their efforts go into optimizing screen space usage, but I feel that a unified bar that's mostly blank really defeats this purpose.

    15. Re:Its too bad the UI got messed up by kiddygrinder · · Score: 1

      heh, i think you miss the point, firefox 4 *is designed for her age*

      --
      This is a joke. I am joking. Joke joke joke.
    16. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      But for a user (even a technically savvy user) semantic cleanliness doesn't make any sense and causes more problems than benefits.

      Garbage.

      If I type "dennis" in the address bar, it's because I want to connect to the webserver on the local machine called "dennis". If I screw up and type into the wrong browser, I want to know that there's no dennis on the local network - I don't want a list of famous people called Dennis.

    17. Re:Its too bad the UI got messed up by camcorder · · Score: 1

      I don't support design direction of Firefox 4 and Chrome.

    18. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      I think you're confusing URIs and URLs. Remember that URIs are too general to be only what you describe.

    19. Re:Its too bad the UI got messed up by lennier · · Score: 1

      But now you're not constrained to identifying yourself with some bogus fqdn with a limiting TLD stuck on it.

      I think you've hit on the exact opposite of the definition of 'bogus' there.

      A keyword can be spoofed by anyone. A URL, not so much.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    20. Re:Its too bad the UI got messed up by tenco · · Score: 1

      If I type "dennis" in the address bar, it's because I want to connect to the webserver on the local machine called "dennis".

      Easily fixed: just use a correct URI.

    21. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      Encouraging people to rely on keywords also opens them up to phishing big time.

      I'd think it's the opposite. URLs are easy to mess up and one single incorrect character can land you on a look-alike phishing site. Keywords are sent to a magical Google search that either finds the correct site for you or asks you if you meant something different.

      I know my parents have been doing this for years. I say "location bar" or "URL bar" and they have no idea what I'm talking about...I don't think they even realize it's there. When they want to go to a site, they hit the "home" button (which takes them to Google) and they type what they want in the search box. Quite often, that involves typing www.whateversite.com. And they're not alone...If you've ever visited someone who works for Google, you might have seen the screens they have up in some of the waiting areas that show live search terms and a lot of them are fully-qualified domain names.

    22. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      I believe you get the experience you're looking for by including the http:// prefix.

      Accepting keywords in the URL bar is the next logical step beyond accepting hostnames rather than full URLs, which is something you obviously don't object to since the behavior you're advocating requires it. It seems rather hypocritical of you to expect to the browser to only help in certain ways when you type a URL incorrectly. If you don't want the browser to help you, you're always free to enter full URLs.

    23. Re:Its too bad the UI got messed up by BZ · · Score: 3, Informative

      > Merging the address and search fields is a big drawback

      Of course Mozilla hasn't merged them. So I'm not sure what you think they got wrong.

    24. Re:Its too bad the UI got messed up by boxwood · · Score: 2, Insightful

      I think the opposite. DNS has gone to shit because of the squatters. To the point that its pretty much useless now.

      And with all the phishing sites.... well we should be discouraging people from typing in $COMPANY_NAME.com to get information they need. They make one typo or if the site they want is under a TLD other than .com then at best they're going to be inconvenienced by loading up the wrong page, and at worst they've entered their banking logon into a phishing site.

      Its far better for people to simply enter a reasonable approximation into a search bar and have a search engine give the site thats most likely what they wanted. Google is much more forgiving of typos than DNS.

      And if you actually know the exact URL, then the functionality is still there for you to bypass the search engine and go directly there. I don't really see a downside.

    25. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      As for Phishing, banks have moved to authentication systems that use graphics on the page to tell you that the password-entry box you're looking at is legit. If you don't see your predetermined secret glyph, you don't enter your password. And the glyph isn't sent until your browser and the server are connected by SSL, so it can't be sniffed and hacked into a phishing site. And it isn't sent unless your browser already has a cookie identifying it as having been validated previously, using a secret-question protocol. If you deleted the cookie, you go through the secret-question routine again.

      Yo dawg, we heard you like logins so we put a login in your login so you can log in while you log in...

      Seriously, doesn't that just means you have two log-in layers? You'll typically stay logged in to the first layer (which displays the "secret glyph"), and keep on logging in to the second layer whenever you want the actual site.

    26. Re:Its too bad the UI got messed up by blair1q · · Score: 1

      Why? Man-in-the-middle is not trivial on SSL links.

      You don't know what secret question to ask unless you've intercepted the question setup, and you can't do that unless you intercept the account setup and act as the SSL endpoint yourself, and act like you're setting up the account. But if you do that, then there's no actual account at the real bank for you to be hacking into.

    27. Re:Its too bad the UI got messed up by blair1q · · Score: 1

      I think you're forgetting that "URL" is deprecated and those things in the box are now called "URIs".

    28. Re:Its too bad the UI got messed up by blair1q · · Score: 1

      I'm speaking in the original Spicoli. You can read the translations in the boxes above and below the panel.

      'Nuff sed.

    29. Re:Its too bad the UI got messed up by blair1q · · Score: 1

      Astute.

      That is in fact what is going on. Sort of.

      Your computer is engaging in a persistent session with the login page, using the cookie as an on-request validation token. If you don't use that computer, or you delete the cookie, you don't get the login page until you log the computer back in.

      Once your computer is logged in to the login page, it's time to log yourself in to your account page. Your account session expires much more easily than the computer's login session does. The computer could conceivably remain logged-in forever (but in practice things get reset during maintenance and upgrades at the bank). You lose your personal session access whenever you close the last account window, or do not send data for several minutes.

    30. Re:Its too bad the UI got messed up by Pentium100 · · Score: 1

      Why? Man-in-the-middle is not trivial on SSL links.

      So, you do not intercept the connection from the user to thebank.com, but ask the user to connect to thebank.phishing.com which has a valid SSL certificate or does not use SSL at all. That server then connects to thebank.com. This requires cooperation from the user, but that's why it's called phishing and not hacking.

    31. Re:Its too bad the UI got messed up by perryizgr8 · · Score: 1

      just one question: what is uri and is it any different from url?

      --
      Wealth is the gift that keeps on giving.
    32. Re:Its too bad the UI got messed up by perryizgr8 · · Score: 1

      this.
      i always search for my bank on google and click on the topmost result. because once while typing the site url, i made a mistake and pressed return and i got a realistic looking login page. that was obviously a phishing operation waiting for people to make a spelling mistake.

      --
      Wealth is the gift that keeps on giving.
    33. Re:Its too bad the UI got messed up by Burz · · Score: 1

      Maybe people are getting tired of remembering different glyphs for each secure site they visit, and you just rather remember the URL?

      Using simple, recognizable URIs won't help you...

      Sorry, NO! The 'complexity' of remembering and using a site's address is irreducible. People have to learn it and if they don't want to that's TOUGH. Social engineering becomes much worse when you start relying on search terms in place of addresses.

      Much of what you say about accessibility is inane: People can still easily access search without having the search and address bars melded together.

    34. Re:Its too bad the UI got messed up by Burz · · Score: 1

      All is good as long as I can disable search from the toolbar.

      I would say the opposite: People who are most likely to realize the difference and have the knowhow to change the toolbar back are also the ones who can't become confused by the combined toolbar in the first place.

      The combined address/search bar should be an option someone can turn on, not a default.

    35. Re:Its too bad the UI got messed up by Burz · · Score: 1

      Grandma doesn't care what a URL is, only that she can get to the sites she needs. If Firefox 4 is intuitive to her, then it doesn't owe me any apology.

      The same reasoning for expediency applies to people who always send email from MS Word, or who use Outlook Express and expect all (active) content to just run.

      The argument for convenience and sleek appearances can (and often does) go too far.

    36. Re:Its too bad the UI got messed up by Phroggy · · Score: 2, Interesting

      You can't deny its convenience

      Watch me.

      I am posting this from Safari 4.1, which has two boxes at the top: an address bar, and a search bar. If I want to search Google, I use the search bar. If I want to revisit a page I've been to before, I use the address bar (Apple recently improved this feature in versions 4.1/5.0). Obviously if I want to enter a new URL, I also use the address bar.

      Since I know what I'm trying to do (search my bookmarks and browser history, or search Google) I have no trouble choosing which field to use (and, for an additional hint, the former currently contains a URL while the latter says "Google" on it). When I type into the address bar, it auto-populates with a list of matches from my bookmarks and history, and is not cluttered by anything from Google. When I type into the search bar, it auto-populates with popular search terms from Google, which is a great feature that I really appreciate; these suggestions are not cluttered with search results from my bookmarks and history.

      Safari's implementation is, therefore, more convenient than Firefox's.

      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    37. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      Don't you remember that article about Facebook that actually ended up above Facebook.com in the Google rankings and how many people complained in the comments about being unable to log in? These people were giving their username and password to an obviously incorrect site. Now imagine what you could do if you Google-bomb a phishing site, and most users access the site simply by searching without even realising that they're searching. Search results are far too inconsistent compared to domain names.

      I also hate merging the bars because I love having all the different search engines available in Firefox. It's much more convenient for them to be separate.

    38. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      There's only one reason that Chrome shifted to using a combined URL/search bar: to drive more hits to Google.

      I agree with the parent to your reply, and other browsers should certainly not follow in Chrome's footsteps.

    39. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 1, Informative

      When working in a call centre, customers would routinely enter URLs in the search bar rather than the address bar (despite asking them to click the bar with the "http" in it, and whatever else I could think of). From that, they would click on the sponsored links. This was a pretty common occurrence.

    40. Re:Its too bad the UI got messed up by kiddygrinder · · Score: 1

      you should use a device designed for your age then!

      --
      This is a joke. I am joking. Joke joke joke.
    41. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      Semantic cleanliness is a benefit if you don't want to feel like you're being belittled. Yes, I know what a search engine is, and yes, I know what an URL is. Don't go around presuming I want the one when I want the other. Don't tell me "FTFY: you really wanted to search for 'other term', not 'this term'", just tell me I might have a typo and provide a link to the other search. In short, programs and search engines shouldn't second-guess.

    42. Re:Its too bad the UI got messed up by alantus · · Score: 1

      Someone should make a plugin / theme / skin in Firefox to make it easy for Grandma.
      Simple menu entries, not too colorful, etc. Maybe its already out there and I haven't found it yet.

      In fact, this should be part of ALL software: OpenOffice, Firefox, Thunderbird, etc.

      Some developers just don't get it. You shouldn't need a degree in order to use a computer.

      KDE takes it to the next level, showing dialog boxes with names like Nepomuk, Akonadi, etc. WTF?

    43. Re:Its too bad the UI got messed up by drinkypoo · · Score: 1

      Sorry, NO! The 'complexity' of remembering and using a site's address is irreducible. People have to learn it and if they don't want to that's TOUGH.

      Sorry, but you are completely and totally incorrect. There are sites which I visit occasionally whose FQDN I cannot recall, but I can remember enough search terms on the site to find them in the top ten google results most of the time. Further, many people know how to visit sites by remembering some site with a link to them. Further, there is a "bookmark" functionality available. You could use del.icio.us (or any alternative) so that you'd tag your bookmarks and be able to find the site again later without knowing the FQDN, yet from anywhere with web access.

      Much of what you say about accessibility is inane: People can still easily access search without having the search and address bars melded together.

      And yet, there is no actual reason to have them separate. It's not like it's hard to tell the difference between URIs and search terms.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    44. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      Not to mention that some ISPs have started mangling their DNS servers up to serve addresses for advertising servers instead of NXDOMAIN responses in a way that breaks address bar searching if the browser does a DNS lookup on the keywords before trying them as a search query.

      Of course, this is entirely the fault of the ISPs, but I don't imagine a great many users will understand or believe that their ISP has taken away their search functionality and not Mozilla.

      But I was under the impression that Firefox 4 would still have a search box anyway, as others have noted.

    45. Re:Its too bad the UI got messed up by ArsenneLupin · · Score: 1

      As for Phishing, banks have moved to authentication systems that use graphics on the page to tell you that the password-entry box you're looking at is legit. If you don't see your predetermined secret glyph, you don't enter your password. And the glyph isn't sent until your browser and the server are connected by SSL, so it can't be sniffed and hacked into a phishing site.

      ... and what if the phishing site connects to the real bank (via SSL...) in order to get the relevant glyphs?

      And it isn't sent unless your browser already has a cookie identifying it as having been validated previously, using a secret-question protocol.

      Ok, so this one's secure, as the browser wouldn't send the bank's cookies to the phisher's site (which has a plausible looking, but different URL).

      If you deleted the cookie, you go through the secret-question routine again.

      ... which will alert you that is something amiss if you didn't actually delete your cookies, which is good. But, if for security reasons (... to protect against other kinds of threats, such as tracking by advertisers...) you've set your browser to consider all cookies as session cookies, then you will get this dialog every single time, making it useless as a warning against phishing. O, and the phishers will have the correct "secret question", because he just connects to the real bank site.

      Ok, in real life, the bank's system would probably grow suspicious if it got lots of connection attempts for different users from a single IP, but in this day and age of botnets, this can easily be worked around by the attacker.

    46. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      You could use your browser's search function to look that up.

    47. Re:Its too bad the UI got messed up by ArsenneLupin · · Score: 1
      Why don't you just bookmark your bank's site?

      And even if you don't, firefox (old version...) would autocomplete to what you've entered previous times.

    48. Re:Its too bad the UI got messed up by Omestes · · Score: 1

      Merging the address and search fields is a big drawback. It further confuses people about what a URL is, and it encourages them and others (esp. advertisers) to give directions to web sites as if the keywords == addresses. (Hey, like AOL!)

      Personally I find it very convenient, so convenient it hampers my use of browsers that don't combine address and search bars. There is nothing quote as annoying as searching for something and ending up at "http://howtocookwalrus.com" instead of a search page. So yes, if there is a mixed standard (some browsers having it, some not), domain squatting will be a problem, but if everyone switches, it won't. Though it is annoying when I type "blizzard" into the address bar and just a Google page, and not nifty auto-parsing action. So I suppose it makes life a bit simpler, and a bit more complicated. Though in this mixed market, I suppose it is safer to default to search, than auto-parsing.

      That said, I don't know if browser devs should be making their products for ONLY the lowest common denominator, its a good way to drive off your core market (if your Mozilla or the Chrome faction of Google). While Firefox has grown in popularity, this growth was because of geeks (who probably have no problem with confusing URLs with search terms), and I'm guessing a very large percentage of their base is still geeks, and if they start removing "confusing" features, and dumbing things down they will start hemorrhaging this segment. Microsoft and Apple (who develop for the masses, and not mostly just nerds) can afford to dumb things down, all of the other browser companies really can't.

      At worst, keeping the merge of address and search would keep things as they are in much of the computer illiterate population. Both of my parents use Google as a place to type in URLs. After 7 years neither of them have ever quite grasped the address bar, no matter how many times I tell them.

       

      --
      A patriot must always be ready to defend his country against his government. -edward abbey
    49. Re:Its too bad the UI got messed up by Anonymous Coward · · Score: 0

      The key distinction between a URL and a search term is that URLs are hard to remember and prone to typos.

      I thought the key distinction was that URLs were globally unique.

    50. Re:Its too bad the UI got messed up by benhattman · · Score: 1

      FYI, unified search/URL bars do exactly what your asking. The user types something in, the browser tries the following

      if isURL?
          Open URL
      else
          Open Search.

      You're complaint is basically that you prefer having to click between two separate text boxes based on what type of text you are entering. That's just a crazy thing to be so upset over. Would you prefer a car with a different ignition slot for reverse than drive? After all, you know which direction you want to be going!

    51. Re:Its too bad the UI got messed up by BitZtream · · Score: 1

      As for Phishing, banks have moved to authentication systems that use graphics on the page to tell you that the password-entry box you're looking at is legit.

      You clearly have no idea how utterly silly those images. They provide 0 additional security. I simply setup my phishing site to suck in your image from the banks website when you try to login, there are multiple ways to do this without the browser alerting you or the bank to anything fishy. This all works because ... people get the wrong URL.

      You can still give out a key that will only map to you, and return a URI that is clearly you

      Really? You're going to create a unique key, that has some sort of meaning to it so it can be remembered thats going to map to any address I want? How do you propose to avoid collisions with no structure? Are you planning on using keys that people can't remember, therefor making them only useful when being transmitted or stored, in which case you can just as easily use URLS. This is a stupid idea.

      If you want deep linking, you don't get pretty URLS that are still human usable.

      If you want shitty linking like the telephone system than sure, we can hand out some 15-20 digit keys instead of domains cause those will certainly be far far easier than using urls.

      Reality check: The unique key is already there, its an IP/Port combination, and it fucking sucks for normal people. Thats why we have URLs, so normal people have something they can use and remember reasonably easy.

      People will screw up some random silly key you make up for them just as often as the screw up a URL, if not more. The same scamming will happen it just won't be targeted as well.

      Everytime someone says URIs are bad, they come and spit out some analog to an existing system that are significantly less useful than a URI and then pretend they had a thought. You didn't. URIs are fine. You don't have any suggestion at all on making them better, you're just repeating what someone else said. You won't fix stupid no matter what you come up with to 'replace the inferior URI', the same problems will still apply. Someone eventually will come up with its replacement, but it won't be anytime soon because there isn't a real problem with URIs and there most certainly hasn't been an alternative that qualifies as 'better' come around yet.

      Do we stop trying to find better ways? No. But seriously, anyone who says URIs suck and are 'a problem' is an idiot. They can be made dead simple and convey almost no information of extremely complex and contain a lifes history. The person creating the URI is the problem, not the URI.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  7. Re:Firefox needs better support for security token by fuzzyfuzzyfungus · · Score: 5, Informative

    "Tools" -> "Options" -> "Advanced" -> "Encryption" -> "Security Devices".

  8. Re:Does what to HTML 5? by Anonymous Coward · · Score: 1, Funny

    oh noes a fast moving industry is moving fast once again. whatever shall we do.

  9. new opportunities for AJAX by nurb432 · · Score: 1

    Great, more client side slow down.

    No, not trolling, i just long for the old days where the processing was done on the server side, and all you needed was a tiny client.

    --
    ---- Booth was a patriot ----
    1. Re:new opportunities for AJAX by blair1q · · Score: 2, Insightful

      Hmm. Have ten million users doing the same ten million calculations each on different data on the sever, or have the ten million users download their data and do the calculations on their own machine...which one will complete faster?

      Server-side scripting is a massive bottleneck if the page has any complexity at all.

      What you should be complaining about is the disastrous state of the code sent to the client side. Most of it is painfully bad.

    2. Re:new opportunities for AJAX by guruevi · · Score: 1

      These days however, clients are about as fast as their servers (if not faster) and servers have thousands of requests to handle. Most recent clients should be able to handle it. However, I wish that more developers also developed a site that would still work without JS however for simpler clients. There are simple ways to do that, to submit information, just use standard forms and AJAX those up. Same goes for menu's - they should be workable without a mouse (no 'hover' functionality) and use CSS instead of JS (where JS can add effects). At least more developers shy away from Flash to develop those extra's.

      Actually, if a developer would develop their site to be usable for blind people, then we would be a great deal further (as those blind people can't see what JS does).

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    3. Re:new opportunities for AJAX by jsebrech · · Score: 1

      JavaScript is not the problem for blind users, there is WAI-ARIA for that. The newest crop of screen readers can deal just fine with Ajax sites, provided they're wired correctly.

      Also, I think the leap from the lightest mobile device to the heaviest desktop user is too big. You have to split your UI into a few key segments and optimize each. If you try to make a single UI fit all purposes, you end up fitting no purpose exactly right, and spend a lot more effort than when building a few dedicated UI's.

    4. Re:new opportunities for AJAX by Anonymous Coward · · Score: 0

      Do you actually know what the J stands for in AJAX?

  10. Sure... by Anonymous Coward · · Score: 0

    If nothing proves that the Internet is primarily used by furries, it's that most of the Web called for the blood of Gates for getting his icky human cooties all over their desktop and it wasn't 'just' a browser, as it should be.

    But that mythical 'fire' fox? Feel free to yiff all over my entire desktop. What a great idea!

    1. Re:Sure... by Khyber · · Score: 4, Funny

      FireFox, IceWeasel, ThunderBird, Breezy Badger, Snow Leopard.

      Just accept the entire technology industry is run by furries.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    2. Re:Sure... by Ash-Fox · · Score: 1

      It's too late to take the blue pill now. You have to see how deep the rabbit hole goes.

      --
      Change is certain; progress is not obligatory.
    3. Re:Sure... by Anonymous Coward · · Score: 0

      I don't wanna enter that hole.....

    4. Re:Sure... by Anonymous Coward · · Score: 0

      Don't forget things like Stoned Beaver and Beaver in Detox (Linux kernel codenames), either...

      In fact, did you know that before Tux became the official unofficial mascot of the Linux kernel, there was another one that was an anthro fox created by Alan Mackey (a furry artist)? Google it sometime (I personally like Tux better, though).

      That said - you may be joking when you say that the entire tech industry is run by furries, but if you've ever been to Silicon Valley, you'll know that this is actually quite a bit closer to the truth than one might think. ;) A lot of the tech folks there are furry, although not all of them shout about it on the Internet.

  11. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 0

    Firefox needs to have better built in support for Ironkey, smartcards and security tokens. So we can once and for all switch away from passwords.

    If Firefox actually supports security tokens, it's not very intuitive.

    Well, it does.

  12. Re:Does what to HTML 5? by Pojut · · Score: 4, Insightful

    I love this country as much as the next patriotic guy...and love means being able to view things honestly. Face it: as a country, we throw out a MASSIVE amount of stuff.

    Come on, mods: if you can't be honest about yourself, what can you be honest about? Shut off Olbermann and Beck, accept what our country is, and just deal with it. Seriously.

  13. Horray Websockets! by DontLickJesus · · Score: 4, Informative

    As a javascript developer I'd simply like to applaud this addition from the HTML5 spec. Simulating the effect with Web Workers wasn't cutting it.

    --
    Where genius and insanity become confused true wisdom is found
    1. Re:Horray Websockets! by h4rr4r · · Score: 2, Interesting

      As a developer, sysadmin and end user I would like to tell you that HTTP is not for this there are other ports than 80 and the web browser is not a virtual machine.

    2. Re:Horray Websockets! by Anonymous Coward · · Score: 2, Insightful

      As a developer, sysadmin and end user I would like to tell you that HTTP is not for this there are other ports than 80 and the web browser is not a virtual machine.

      With the addition of canvas and now websockets... it is now.

    3. Re:Horray Websockets! by Anonymous Coward · · Score: 0

      Go back to 1992?

    4. Re:Horray Websockets! by exomondo · · Score: 1

      I would like to tell you that HTTP is not for this

      It wasn't intially designed with this in mind, but welcome to the technology industry, it may shock you but the internet wasn't designed for with streaming video in mind either.

    5. Re:Horray Websockets! by Ant+P. · · Score: 1

      Wait, you could do that with web workers? I thought they were limited to the message passing interface for I/O.

    6. Re:Horray Websockets! by DontLickJesus · · Score: 1

      As I said, "simulating", using them in a comet fashion never quite cut it.

      --
      Where genius and insanity become confused true wisdom is found
    7. Re:Horray Websockets! by Simetrical · · Score: 1

      As a developer, sysadmin and end user I would like to tell you that HTTP is not for this there are other ports than 80 and the web browser is not a virtual machine.

      Then it's a good thing that that WebSockets aren't HTTP. It's a completely new protocol that's designed for efficient two-way communication over a connection that's held open on both sides. See section 1.7 of that draft RFC, "Relationship to TCP and HTTP":

      The WebSocket protocol is an independent TCP-based protocol. Its only relationship to HTTP is that its handshake is interpreted by HTTP servers as an Upgrade request.

      --
      MediaWiki developer, Total War Center sysadmin
  14. Re:Does what to HTML 5? by Anonymous Coward · · Score: 0

    My 1939 Studebaker can't keep up with the speed of traffic on interstate highways so everyone else should have to slow down.

  15. Re:Firefox needs better support for security token by mrsteveman1 · · Score: 1

    It does, you just need a library for working with your token, and of course that token has to work at the driver level with your OS, but yea in general it works pretty well, certificates can be stored on the device and they can be retrieved from it when a specific website requests authentication.

  16. Obligatory King Of The Hill paraphrased quote by RevWaldo · · Score: 1

    Prepare your PC for razzle-dazzle!!

    .

    1. Re:Obligatory King Of The Hill paraphrased quote by swanzilla · · Score: 1

      Prepare your PC for razzle-dazzle!! .

      I don't think you know what obligatory means.

    2. Re:Obligatory King Of The Hill paraphrased quote by rudy_wayne · · Score: 1

      Prepare your PC for razzle-dazzle!!

      Instead of crap done in Flash, we can now have crap done in HTML 5.

  17. Re:Firefox needs better support for security token by blair1q · · Score: 4, Informative

    You mean "Edit" -> "Preferences" -> "Advanced" -> "Encryption" -> "Security Devices".

  18. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 5, Insightful

    No, he doesn't. He means what he said, regardless of the fact that *nix firefox has a different menu layout.

  19. Re:Does what to HTML 5? by eldavojohn · · Score: 1

    I love this country as much as the next patriotic guy...and love means being able to view things honestly.

    Er, I don't think this is an issue of whether or not you're "patriotic enough." I think you're overlooking that a lot of other countries also through stuff out, like Great Britain. And in China, they throw it out, it just gets thrown out in their country next to their cities. When you snidely comment "It's the American way" you kind of omit that it's also the way of many other countries.

    So one of the big problems is that we try to treat garbage and pollution from a capitalistic perspective. We may give countries or pay to have countries take our garbage under the understanding that it's being recycled. But more often than not it is just dumped or the precious metals are harvested in very environmentally damaging ways. And this is a problem with a world wide capitalism similar to how the mafia ruined parts of New Jersey with illegal dumping of NYC's garbage. It's corruption. China shows that a corrupt socialist system exhibits the same environmental problems on their local level. And when we feed that corruption and turn a blind eye then, yes, it is also our problem.

    Face it: as a country, we throw out a MASSIVE amount of stuff.

    This is true. It's also true that stuff we buy (from both inside our country and from the outside) are designed to be disposable. Your toaster breaks. Do you A) bring it to the repairman down the street and pay $50 to get it repaired by a skilled technician or B) go to Wal-Mart and buy your next $12 toaster? If we do A we're stupid and cannot manage our money. If we do B then you're criticizing us and calling it the American way. So what's an average citizen to do?

    Come on, mods: if you can't be honest about yourself, what can you be honest about? Shut off Olbermann and Beck, accept what our country is, and just deal with it. Seriously.

    Do you think it's the moderators that desire this situation? That want this situation? Do you think it's Olbermann and Beck that promote this situation? The entire world is part of the problem. The fact that everyone on Earth consumes products and produces waste that will be around longer than their flesh is a potential problem as our population increases. This happens in every country, not just the United States. Your criticisms are strangely specific. Jon Stewart supports this just as much as Glenn Beck. It is a universal problem of pollution and disposal yet you turn it into an American responsibility. Why is that?

    Do you really think that if Americans stopped doing it, the problem would magically disappear because the disposal of the electronics in Japan goes through some magical Fern Gully process?

    Sorry to go to such an offtopic response but I cannot understand why this blame is placed on Americans. As to the topic of HTML 5 affecting this pollution, attacking some standard far down the chain does not make nearly as much sense as instituting government regulations to make computers more recyclable without hindering them too much. If you perceive what you say to be "the American way" to be a problem than it's obvious our current system has not adapted to regulate itself.

    --
    My work here is dung.
  20. Why Google matters by westlake · · Score: 1
    what the fuck has that got to do with anything?

    Something like 83% of Moz's funding comes from Google. There's nothing much to suggest that Moz is ready for the day when Google pulls the plug.

    1. Re:Why Google matters by hedwards · · Score: 1

      With Google offering up Chrome, it's virtually assured that they won't pull the plug shy of going out of business. It's just not worth the cost of the antitrust defense. As long as Firefox and IE are major players Google doesn't have to worry a whole lot about being seen as controlling the browser market. Plus since Mozilla already has a meaningful interest in HTML5 and much of what Google wants, it's strategically helpful to them anyways.

    2. Re:Why Google matters by boxwood · · Score: 1

      anti-trust wouldn't be an issue since Google doesn't have an illegal monopoly. Yeah almost everyone uses their search, but thats browser agnostic, and people use their search because they choose to. There is no barrier to people using another search engine.

      But you don't need to worry about mozilla. Google will keep giving them money to keep google as the default search engine in firefox. If google stopped giving them money, Bing would gladly pay them to make them the default search.

    3. Re:Why Google matters by icebraining · · Score: 1

      Chrome has so little market share that they could do whatever they want, nowhere would they be considered as "controlling the browser market".

      The question is: why would they do it? They're not in the browser market, they're in the web advertisement market. More and better browsers == more people viewing their ads.

    4. Re:Why Google matters by bunratty · · Score: 1

      Why wouldn't some other search engine pay to be the default search engine in Firefox?

      --
      What a fool believes, he sees, no wise man has the power to reason away.
  21. Firefox 4 didn't catch up in canvas speed by dionyziz · · Score: 5, Interesting

    Interestingly, Firefox compares poorly to other browsers when it comes to heavy rendering in "canvas". Here's a demo I made that allows measuring the speed of rendering in FPS (frames per second).

    http://dionyziz.kamibu.com/3d/heli/

    Chrome 6: 31 FPS
    Opera 10.60: 46 FPS
    Safari 5.0: 25 FPS; visually poor results
    Internet Explorer 9: 19 FPS
    Firefox 4.0 Beta 1: 19 FPS

    1. Re:Firefox 4 didn't catch up in canvas speed by Cthefuture · · Score: 1

      I get about 25-30 FPS in the Firefox beta 1 (32-bit version) under Linux.

      I get about the same as you in Chrome and Opera (64-bit versions, also Linux).

      --
      The ratio of people to cake is too big
    2. Re:Firefox 4 didn't catch up in canvas speed by Cthefuture · · Score: 1

      I forgot to mention that I get about 10-18 FPS in Firefox 3.6 (32-bit) on Linux and it's visibly choppy and blah. Firefox 4 may not be at the top but it seems better than Firefox 3.

      --
      The ratio of people to cake is too big
    3. Re:Firefox 4 didn't catch up in canvas speed by dionyziz · · Score: 1

      I'm using Windows 7. As far as I know, Firefox uses different rendering techniques on different operating systems, so that may be a cause.

    4. Re:Firefox 4 didn't catch up in canvas speed by Anonymous Coward · · Score: 0

      Hmm... I have one of the old, first-gen MacBooks. I get 19-20 FPS but not ugly results in Safari 5. Firefox 3.6 gives me around 8-9 FPS and looks as piggish as those numbers sound.

    5. Re:Firefox 4 didn't catch up in canvas speed by tyrione · · Score: 1

      Interestingly, Firefox compares poorly to other browsers when it comes to heavy rendering in "canvas". Here's a demo I made that allows measuring the speed of rendering in FPS (frames per second). http://dionyziz.kamibu.com/3d/heli/ Chrome 6: 31 FPS Opera 10.60: 46 FPS Safari 5.0: 25 FPS; visually poor results Internet Explorer 9: 19 FPS Firefox 4.0 Beta 1: 19 FPS

      Hardware specs, please.

      I'm on a Pentium D 945 with 4GB Ram and an Nvidia 8600GTS with 256MB Ram. I'm getting 17FPS on Chrome Debian 64bit Linux, latest beta. Epiphany 2.30.2-3 locks up.

    6. Re:Firefox 4 didn't catch up in canvas speed by BZ · · Score: 1

      In Firefox, about 25% of the time on that page is spent in anything canvas-related. Another 20% is spent painting.

      Also, 10% is spent allocating arrays, 20% is spent sorting arrays. Another 15% is spent running other JavaScript of various sorts.

      So the issue here is not exactly canvas performance...

    7. Re:Firefox 4 didn't catch up in canvas speed by dionyziz · · Score: 1

      I'm using an Intel Core 2 CPU at 2.40GHz, 2GB RAM and an NVidia GeForce 7300GT. I use the latest betas of Chrome, Opera, Safari, Internet Explorer, and Firefox available precompiled for download (not directly from their repositories). My OS is the latest Windows 7 with all recent updates.

    8. Re:Firefox 4 didn't catch up in canvas speed by dionyziz · · Score: 1

      That still counts as performing poorly when measured against other browsers. It could be Firefox's Javascript engine that is too slow: As a developer, I want to have applications that run fast and look good; I don't care how the browser achieves that much. At the moment, Firefox just doesn't do that for me.

    9. Re:Firefox 4 didn't catch up in canvas speed by BZ · · Score: 1

      > That still counts as performing poorly

      Sure. Did I say anything about that? My point was that canvas performance is not the issue here.

  22. Re:Does what to HTML 5? by Pojut · · Score: 0, Troll

    My original post ("The American Way") was intended as a joke...a true joke, but still just a joke. That being said, given the -1 mod it reached, I figured I offended someone...so I figured I would be a dick, because you should never be offended when someone states the truth. "The American Way" doesn't mean no one else does it, it simply means that we do it. In no way did I mean or imply otherwise.

    For the record, I wouldn't have bought a $12 toaster in the first place...that's one of the reasons why it broke ;-)

  23. desktop as a document? by roman_mir · · Score: 1

    Browsers are designed and implemented to display documents, not to be as interactive as normal desktop apps, sure we try to cross that bridge with all the tricks and yet the browsers are just too slow for using as good desktop apps. They render and re-render to get the layout right the way the designers wanted it, but while recalculating all of those layouts and all of the elements that come in later, scripts that execute after the html is parsed and dom is created and css are applied and then re-rendering it to fit things right yet again.... browsers are just not good for replacing desktop apps. So that's where java applets come in (I guess for some it's flash/silverlight...)

    1. Re:desktop as a document? by jsebrech · · Score: 4, Insightful

      You do realize that flash internally manages a display object hierarchy not unlike the DOM? There isn't much difference between writing apps in flex/flash and writing apps in javascript with something like ExtJS toolkit. All rich app frameworks I know, on any platform, use the HTML-like approach of having an element hierarchy and a set of layout rules that are constantly re-calculated.

      HTML may be ill-suited to rich app development, but so is everything else. Win32 and X11 are both truly horrible API's, arguably much worse than HTML+JS+CSS, but combined they hold the majority share of native apps.

      And by the way, the browsers of today are designed for rich applications. They have been for a few years now. Cars were originally designed to make it up to a brisk walking pace at best. Things change.

    2. Re:desktop as a document? by carrier+lost · · Score: 2, Funny

      Things change.

      Heresy!

    3. Re:desktop as a document? by roman_mir · · Score: 1

      whatever the browsers of today are designed for, I still find that when I try to display a table with 20,000 rows in it in 8 columns, it takes almost a minute to create/render this table in a browser, vs less than 1 second in a Java applet running in the same browser, so I can scroll to the very bottom of the JTable in the applet 1 second after the data starts loading, in the same time the browser renders maybe 300-400 rows.

      This is not helped by any of the technologies that exist, GWT compiler/code cutter doesn't help, AJAX doesn't help, css only table doesn't help, inline HTML (also used by GWT table bulk renderer) doesn't help. You'll say: big deal, don't put that many rows there? I say: that's why a desktop app is better, I can put that many rows in there and I have a business case for it.

    4. Re:desktop as a document? by Randle_Revar · · Score: 1

      >Win32 and X11 are both truly horrible API's

      Luckily we have GTK/QT and uh, .NET to cover that up

    5. Re:desktop as a document? by Anonymous Coward · · Score: 0

      There is no business case for showing that much data to a user right away. Provide search and paging features and while you're at it go pick up an HCI book.

      Also HTML is a document language so the browser is rendering every row. Even ones that aren't visible. JTable is a widget that does lots of creative tricks to be fast. Try loading a giant PDF 4000x4000 pixels or so and watch every desktop app crawl. It's the same thing you're seeing in the browser. Desktop apps arent imune to this problem.

    6. Re:desktop as a document? by roman_mir · · Score: 0, Troll

      Who are you to tell my users what their business case is?

      Also I am giving you the actual reasons why browser sucks at being forced to try and behave like a desktop application, you are dismissing it on your perverted reasoning that you know better what people need for their work!

  24. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 0

    Firefox fully supports PKCS#11 as it always has. Pretty much any PKCS#11 module can be used and there are tons of them for just about every security device in existence.

  25. Not quite by Anonymous Coward · · Score: 0

    I read the wiki. It sounds like a kludge to accomplish what is really being done in HTML 5.
    The first method sounds like the reason some pages I visit always show that the page is never done downloading. The server keeps the socket open as if it was going to still transmit data. At some point, this connection must timeout. The other 2 methods aren't adopted by all browsers, which is why we need HTML 5.
    HTML 5 - To finally be able to to write something as simple as a chat program in HTML & JavaScript only without Polling.

    1. Re:Not quite by icebraining · · Score: 1

      Not only connections timeout, as they close each time the server sends some data, so if there are multiple data packets (Google Wave's show-as-you-type, for example) incurs in a lot of overhead closing and opening HTTP connections.

    2. Re:Not quite by dave420 · · Score: 1

      It's rather easy to use keepalive to keep connections open after they're used.

    3. Re:Not quite by icebraining · · Score: 1

      keepalive maintains TCP connections alive, but you still have to do an HTTP request for every data packet you want to transfer. keepalive is just a way to pipeline multiple HTTP requests.

  26. Re:Does what to HTML 5? by h4rr4r · · Score: 1

    So why not update the OS to something that will run the later firefox?

    OS upgradees don't cost me anything.

  27. Re:Firefox Speed by Phrogman · · Score: 0

    seems to be ever decreasing in a constant spiral with each new version. Its already getting slow enough that I don't use it for certain websites (which are admittedly badly written). I play a web-based game a friend of mine has written. After issuing a few orders in it, Firefox just stops working. His HTML is likely crappy and his PHP doubly so, but there is no excuse for it, when I can open the same website up in Safari and it works fine. I want to use FF but I am being driven away from it by the decrepit speed it operates at much of the time.

    --
    "The first time I got drunk, I got married. The second time I bought a chimpanzee, after that I stayed sober" Arian Seid
  28. On Windows 7 by Sycraft-fu · · Score: 1

    It is supposed to use Direct2D, just like IE9. I don't know if it does yet or if it is enabled by default, but that is one of the big features. If that is available (which means any Windows Vista or 7 system with WDDM 1.1 hardware) it be able to make sure of it. That should accelerate the heavy hitting rendering, as well as make for smoother scaling and text (at least if it also uses DirectWrite).

    I haven't looked in to if it will use similar acceleration on other platforms, where available.

    1. Re:On Windows 7 by dionyziz · · Score: 1

      Actually, Internet Explorer 9 has a similarly poor performance, as you can see from my measurements. Opera seems to be winning so far, and by a wide margin.

    2. Re:On Windows 7 by surveyork · · Score: 1

      On my poor old PC with XP 3 Chrome wins, second is Firefox and 3rd is Opera. Remember that Firefox is still in beta 1. Mozilla is working on making it faster.

      --
      2019 is going to be the year of Linux on the desktop.
    3. Re:On Windows 7 by shutdown+-p+now · · Score: 3, Informative

      It is supposed to use Direct2D, just like IE9. I don't know if it does yet or if it is enabled by default

      FF 4 beta 1 does that, but it is not enabled by default. Here are the instructions on how to enable it.

  29. Catch up with silverlight? by xmorg · · Score: 1

    How the heck do you "catch up"? Its like saying adds Apple IIe support. Better written as Adds support for legacy plugins like Silverlight

  30. Acid test still not 100/100? by erroneus · · Score: 1

    The article doesn't say so but another one (http://digitizor.com/2010/06/30/review-of-firefox-4-0-beta-1-for-linux/) when googling the question reveals that Firefox 4.0 beta scores 97/100. This is less than perfect which is currently achieved by other browsers. I have to wonder what the issue is. While 97/100 is better than the 94/100 of the current version 3.6.6, I have to wonder why it hasn't targeted 100/100 for this release.

    Perhaps someone in the know will have something interesting to reveal on the subject. Could it be that Mozilla's efforts are more honest while those who score 100/100 have merely been "studying for the test?" (In the past we have seen where graphics card drivers were optimized to score high on certain benchmark tests instead of scoring high in general. This is what I would call "studying for the test" instead of mastering the material.) In the case of MSIE, we understand Microsoft's motivation to remain "broken by design" but this doesn't apply to Firefox so their less than 100/100 defies explanation in my mind at the moment.

    1. Re:Acid test still not 100/100? by t0y · · Score: 3, Informative

      The remaining tests target SVG font functionalities which are not being actively developed.
      You can find a semi-official rationale for not implementing them here: http://weblogs.mozillazine.org/roc/archives/2010/06/not_implementin.html

    2. Re:Acid test still not 100/100? by surveyork · · Score: 2, Informative

      I think you're right: Mozilla is mastering the material, not studying for the test. The only thing that really keeps them from getting 100/100 is the lack of implementation of some SVG stuff. See: https://bugzilla.mozilla.org/show_bug.cgi?id=119490 , specially the last 10 or so comments. However, Mozilla publicly stated that they wanted to fully implement SVG 1.1. http://www.mozilla.org/projects/svg/

      --
      2019 is going to be the year of Linux on the desktop.
    3. Re:Acid test still not 100/100? by BZ · · Score: 4, Interesting

      Those remaining 3 points are SVG Fonts.

      Opera and Webkit implemented (very brokenly, in at least Opera's case) a small subset of SVG 1.1 Fonts; basicallu just enough to pass Acid 3. We don't particular want to do that small subset in Gecko, since it gives no benefits to authors or users over the existing downloadable font support (beyond the brownie points on Acid3). On the other hand, support for the full specification in a UA that also supports HTML is ... very difficult. SVG fonts are just not designed with integration with HTML in mind. Once you put an in a glyph, all sorts of issues arise (both in terms of the spec being underdefined and in terms of the behavior being very difficult to implement no matter what the spec said).

      One of the previous commenters here linked to Robert O'Callahan's post about this, which covers the issues pretty well.

      At this point, the SVG working group has decided that SVG Fonts will no longer be a core part of SVG but will be a separate specification, and that it might need some serious work if anyone is ever to implement it in full.

    4. Re:Acid test still not 100/100? by Anonymous Coward · · Score: 0

      http://weblogs.mozillazine.org/roc/archives/2010/06/not_implementin.html

      Well, yeah. Read the comments on that post. People don't understand why Firefox does not support SVG fonts when even they acknowledge it wouldn't be difficult to do.

      It really is hard to understand.

    5. Re:Acid test still not 100/100? by BZ · · Score: 1

      Please read again.

      It wouldn't be hard to support the small subset Opera and Webkit implemented to pass Acid3. Especially if one settles for an implementation as broken as Opera's (font fallback? What's that?)

      Properly implementing SVG Fonts in a UA that also supports HTML is really really hard.

    6. Re:Acid test still not 100/100? by BitZtream · · Score: 1

      Until its in a spec someone can access, what they talk about really is irrelevant. The SVG working group is a pain in the ass for SVG adoption. You have the Inkscape devs saying 'well the SVG WG is talking about doing this, so we're not going to do anything else because thats the way the spec is HEADING'. Then you have the batik devs who are saying 'we implemented most of the last published draft for the 1.2 spec, we're not doing anything else on the extended features unless it solidifies because it looks like its going to change'.

      Batik has implemented the vast majority of the 1.1 spec and most of the last 1.2 drafts, inkscape is somewhere trailing behind, and getting either group to do anything relating to new features is next to impossible since no one wants to be obsoleted by the SVG WG.

      I say, fuck the SVG WG at this point. Lets take the last published 1.2 full draft and continue on without them. I'm talking to you Inkscape and Batik devs! Stop using the spec as an excuse, code to the working draft and the SVG WG can either get their ass in gear or not be a group that anyone cares about and they'll be replaced by someone else.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    7. Re:Acid test still not 100/100? by BZ · · Score: 1

      If Inkscape/Batik follow your proposal, why should anyone else (e.g. browser developers) care about what they cook up?

  31. Re:Does what to HTML 5? by Nethead · · Score: 1

    As much as I think eldavojohn is often the jerk, he's really right on this comment.

    I just hope that we can nano-harvest the dumping grounds someday.

    --
    -- I have a private email server in my basement.
  32. Re:Firefox Speed by kiddygrinder · · Score: 1

    so use something else, that's why web standards exist :)

    --
    This is a joke. I am joking. Joke joke joke.
  33. Firefox started to got it right already by unity100 · · Score: 1

    this last change in the last version that has the flash and other plugins run in a separate plugin container which prevents firefox from crashing when any of these plugins (Especially flash) crashes, has set a lot of things right already. all you need to do now is to refresh the page to get the plugins rolling again.

  34. Re:Does what to HTML 5? by Nethead · · Score: 3, Insightful

    Ya know, 1999 wasn't all that bad for me. Dot com boom. making big bucks at an internet porn company, got married, had a nice car, nice house... yeah, I'll go back there.

    --
    -- I have a private email server in my basement.
  35. what's that? Firewhat? by bwave · · Score: 1

    Firewhat? Didn't that go the way of Netscape and the dodo bird?

  36. Re:Does what to HTML 5? by ZosX · · Score: 1

    He's talking about the hardware. Of course you can't effective browse the web on a 486. If you can't run firefox 2, then an upgrade was looooong overdue!

  37. Legacy browsers = forget HTML5 for, say, 10 years by onlyjoking · · Score: 0

    If the lessons of IE6 are anything to go by HTML5 won't really be relevant for about another 10 years, ie. when IE8 has faded into obscurity. I just started upgrading my CSS skills and the landscape is only now ready for phasing out IE6 support. With IE7 as the baseline most of CSS3 is irrelevant, never mind HTML5. Microsoft has a lot to answer for. Despite the insidious tentacles of their insipid monopoly they don't seem to have the ability to use it for good and impose browser upgrades, largely due to the way they encouraged companies to build IE(6)-only apps for so long.

  38. Title bar reduced by half? by quickgold192 · · Score: 1

    Why would the developers only reduce the title bar size by half? It's like a landing strip: if you're going to go through the trouble of shaving some off, you might as well shave it all off.

    1. Re:Title bar reduced by half? by Ankle · · Score: 1

      Leaving some of the title bar makes for a much easier target to grab and drag a window around than a pixel or two for a border.

  39. Re:Still WAY behind Opera by Jake+Griffin · · Score: 1

    Title: Still WAY behind Opera

    Firefox4 is still a million miles beyond Opera...

    Vocabulary fail.

    --
    SIG FAULT: Post index out of bounds.
  40. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 0

    You have just publicly humiliated yourself.

  41. Re:Does what to HTML 5? by CoonAss56 · · Score: 1

    Mine does 'cause it has a 540 blown Chevy on alcohol.

    --
    Won't Bow.....Don't Know How
  42. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 0

    No, he doesn't. He means what he said, regardless of the fact that *nix firefox has a different menu layout.

    Several different layouts, actually. My UNIX firefox has the prefs on the "Firefox" menu. (Mac OS X)

  43. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 0

    No, blair1g did.

  44. Re:Firefox needs better support for security token by AaxelB · · Score: 1

    I've never understood why "Preferences" would be in the Edit menu. I think the thought process is "You edit your preferences!", but that just makes no sense at all, given the rest of the entries in the Edit menu. This seems to be a common theme among most Linux (at least) applications, so I have to assume (quite optimistically, I admit) that there's some sort of explanation... Does anyone know?

  45. Plugins by Jazzbunny · · Score: 1

    If you want to test whether your favorite plugin will work at Firefox 4.0 b or not, do following: add new boolean entry at about:config named "extensions.checkCompatibility.4.0b" and set it to false. After that install your plugins and mostly they work just fine, if not nag to the plugin developer :)

  46. Re:Firefox needs better support for security token by transwarp · · Score: 1

    I always thought it was either a GTK or GNOME guideline. KDE apps have 'configure' in the settings menu.

  47. Re:Firefox needs better support for security token by blair1q · · Score: 1

    I've never understood why all the application controls are under the "File" menu.

  48. Re:Firefox needs better support for security token by AaxelB · · Score: 1

    Ah, true, I've been using almost exclusively GNOME for a while and forgot how KDE's menus work.

  49. jaggies by perryizgr8 · · Score: 1

    for some reason, firefox does not anti-alias text in custom fonts. for example, go to html5test.com. the score is very jaggy. the same font on chrome looks ultra smooth.
    is this a firefox problem or is it just me and my horrible vista?

    --
    Wealth is the gift that keeps on giving.
  50. Re:Firefox needs better support for security token by perryizgr8 · · Score: 1

    i thought they removed the menu bar? and there is a single orange button now? is that incorrect?

    --
    Wealth is the gift that keeps on giving.
  51. Shines on HTML5; shits on MPEG-4 by gig · · Score: 0

    When IE9 is released, every PC, smartphone, and tablet will support HTML5/MPEG-4 out-of-the-box. Every set-top box and console game already supports MPEG-4, and they are all in the process of getting HTML5. The HTML5/MPEG-4 Web is the consumer Web and it is already here. The fact that Firefox can't support it means they are on borrowed time, getting by in the shadow of IE6-IE8.

    Right now the Web is split in 2 layers: a modern HTML5/MPEG-4 layer that runs on non-PC and a legacy IE6/Flash layer that runs on PC. That is why PC users are incredulous that iPad can be used to surf the Web. They see Flash all over the place and don't understand that the same IE6/Flash page they are viewing appears as HTML5/MPEG-4 on iPad. IE9 will finish what Safari/Chrome for Windows started and bring the PC onto the modern Web. Essentially IE9 will mobilize the PC. Publishers are already chafing to drop the IE6/Flash legacy right now because it costs so much to maintain and they want to run just one modern website. People who only use a PC to access the Web (no smartphone, iPod, tablet, set-top, etc.) are rare right now and getting rarer every day.

    If you think Firefox is going to survive the "mobilization" of the Web with didactic open source philosophy screeds and WebM/Ogg support, you are insane. WebM has only 2 practical purposes: drive Firefox users to Chrome and video publishers to YouTube. Standards are new to the Web ... HTML5 may be the first successful markup standard. But in audio video, standards are historically very successful. MPEG-4 is the 3rd successful audio video standard ... 4th if you count MP3, and 5th if you count CD-DA. There were unsuccessful ones years ago that spanked everyone in audio video so hard they learned their lesson. We got a taste of that recently when even the entire weight of Microsloth could not break the consumer audio video standards: VC-1 in Windows went nowhere, VC-1 in "HD-DVD" sold only 150,000 players. But they did pretty much kill the optical disc, which was at the end of its life anyway. MPEG-4 is an online CD/DVD. To audio video publishers, MPEG-4 is as important as CD/DVD. MPEG-4 is as important to audio video publishers as UTF-8 is to text publishers. And it's not something that's happening in the future, it happened already at the turn of the century. The incredibly slow, mind-numbing, reason-defying slowness of Microsoft has just hidden this from PC people. Consumer electronics is all MPEG-4 for many years now. MPEG-4 is what is on Blu-Ray, it's your Hulu stream, it's your Netflix stream, it's your iTunes+iPod, it's in your smartphone and your GPU.

    So all the HTML5 standard markup support in the world doesn't matter if Mozilla can't play MPEG-4 standard audio video. The Web is not about PC's and I-T people anymore, it's about consumer electronics devices and consumers. It's not just text and graphics and whatever exotic nonstandard thing you want to embed or plug-in or download to show your techiness, it's the whole range of human expression in rigorously standardized formats that require zero I-T work to decode. The Web is now native HTML5 code, UTF-8 text, JPEG photos, PNG/SVG graphics, and MPEG-4 audio video. All W3C/ISO standard.

    Perhaps the most foolish part is Mozilla says they don't want to pay MPEG-4 license fees, but those license fees could never amount to more than what they get from Google for just 10% of their user's searches. If they lose only 10% of the Firefox user base because those users can't see standard audio video, then their gambit has lost. They could be gaining users right now by pressing the MPEG-4 advantage over IE8, but they are missing that chance and handing those users to Safari and Chrome. When you consider that the vast majority of video that plays today in Firefox via Flash (the ultimate closed system) is MPEG-4 H.264, Mozilla is cutting off their nose to spite their face. They're making a mistake of historic proportions. We'll mark this as the beginning of the end for Firefox one day in the near future when writing its obituary.

  52. Re:Does what to HTML 5? by Runaway1956 · · Score: 1

    Maybe you should do routine maintenance on your Studebaker?

    "A new 164.3-cid six-cylinder engine was designed expressly for the lightweight Champion and made for sprightly performance and sparkling economy. It wasn't long before owners were bragging of 25-mpg economy and 80-mph top speed. In various forms, this durable L-head would be a staple at Studebaker through model year 1960.

    Sparked by early reports of its miserly ways, the Champion topped 30,000 sales in its introductory year. Thousands of over-the-road salespeople took a real liking to this economical traveler, and Studebaker enjoyed its best year since 1928. "
    http://www.howstuffworks.com/1939-studebaker-champion.htm

    Granted, you don't want to run any vehicle at it's top speed all the time - but the Studebaker can be expected to run 65 to 70 mph, which means you can keep up with the flow of traffic almost everywhere.

    --
    "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
  53. Great, another malware attack vector by dhammabum · · Score: 1

    Firefox 4 also adds an implementation of the Websockets API, a tool for enabling the browser and the server to pass data back and forth as needed

    And there is talk of support for cross-domain comms and binary data - see hacks.mozilla.org. Who needs Microsoft (for poor security) when there are designs like this?

    --
    I am not a robot. I am a unicorn.
    1. Re:Great, another malware attack vector by Ant+P. · · Score: 1

      OH NOSE! Web servers will be able to SEND DATA TO YUOR BORWROSAR!!1 HAX!!!!!1

      Seriously, are you smoking crack?

    2. Re:Great, another malware attack vector by coerciblegerm · · Score: 1

      OH NOSE! Web servers will be able to SEND DATA TO YUOR BORWROSAR!!1 HAX!!!!!1

      Seriously, are you smoking crack?

      Not just data, but binary data. If you don't understand the attack vectors this opens up refrain from mocking those who do.

    3. Re:Great, another malware attack vector by Ant+P. · · Score: 1

      What, like AJAX requests to "file.bin" on the server? Holy crap you're right this has never been thought of before!!

  54. I don't believe that by Snaller · · Score: 1

    "Firefox 4 also adds an implementation of the Websockets API, a tool for enabling the browser and the server to pass data back and forth as needed, making it unnecessary for the browser to keep asking the server if there's anything new to report.'""

    And how would the browser know? Magic? Telepathy? Of course the browser has to keep asking the server if there is something new!

    --
    If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
    1. Re:I don't believe that by psYchotic87 · · Score: 2, Informative

      At the risk of getting a few "whoosh" comments, let me explain this to you (and anyone else that doesn't know about websockets): your browser requests a websocket from the server, which responds with an address it can connect to. Once connected to this address, your browser and the remote server can exchange anything over a regular full-duplex TCP channel, effectively bypassing all the HTTP limitations. Look here for more information.

    2. Re:I don't believe that by LarryRiedel · · Score: 1

      From draft-ietf-hybi-thewebsocketprotocol-00:

      The opening handshake is intended to be compatible with HTTP-based server-side software, so that a single port can be used by both HTTP clients talking to that server and WebSocket clients talking to that server. To this end, the WebSocket client's handshake appears to HTTP servers to be a regular GET request with an Upgrade offer

  55. Perfect by Anonymous Coward · · Score: 0

    What's not to love about corections with typos in them!

  56. What's in a name by Anonymous Coward · · Score: 0

    Ok. So where do they go? They're not a "tool". Nor are they "help". You can view or edit them, but they're not document-specific. Let's face it, menu structures are fucked up all over in every OS, because they conform to entrenched user habits.

    Top menu names should really be something like:

    App modes
    App actions
    App info
    Doc modes
    Doc actions
    Doc info
    [Superduper app-specific menus]

    If you look at the structure right now, it's roughly:

    File -> Application modes & Application actions & Document info
    Edit -> Document actions
    View -> Document modes
    History -> App-specific menu
    Bookmarks -> App-specific menu
    Tools -> Application actions & Document actions
    Help -> Application info

    They're all there, if messed up quite a bit. Rearrange them to make sense and people start complaining. Don't rearrange them and have people like you (and me) use above mapping. Which means preferences ought to be under File.

  57. html5 FTW by Anonymous Coward · · Score: 0

    works good like a zylophoned frog on acid!

  58. Re:Firefox needs better support for security token by Phroggy · · Score: 1

    I believe this was originally a Mac OS standard, which made its way to the UNIX world when UNIX had no standard of its own. As for why, though, I have no idea.

    On the Mac, the keyboard shortcut command-semicolon became a de-facto standard, adopted by a huge percentage of Mac applications, but never accepted by Apple. With the transition to Mac OS X, Apple took the opportunity to create a new application menu, move Preferences to there, and define a new official keyboard shortcut, command-comma. I have no idea why they changed the keyboard shortcut that everyone except them had standardized on.

    But I digress. :-)

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

    Basel Convention

    The United States are the only developed country that has not ratified the Basel Convention.

  60. Re:Still WAY behind Opera by m1ss1ontomars2k4 · · Score: 1

    Ironically enough for you, perhaps, they're actually quite close now, because they look darn near identical (or they do on Windows anyway), what with their ridiculous menu button in the upper left and nearly identical tab widgets.

  61. Plugin Container BLOWS CHUNKS by Anonymous Coward · · Score: 0

    slows the browser down to a crawl sites like techdirt are almost unnavigatable and i end up using chrome for loads a sites but retin FF for some sites....

    fix it or FF is dumped and im a guy who helped get netscape communicator out to the masses on a mirror when it went public

  62. Re:what's that? Firewhat? by Jackie_Chan_Fan · · Score: 1

    As long as chrome has terrible bookmark management... Firefox will be first choice for me

  63. Events are possible right now by olau · · Score: 1

    That's not really true. You can push events right now.

    The problem with the model on the web is that most clients are behind some kind of firewall/router/.... So the client always has to initiate the communication, keeping a connection open for the server to respond. What you do with long-polling is simply asking for events, not responding at the server until any events actually show up. Voila, event pushing. For this to work through standard HTTP, the clients sends a standard GET or POST and get back a properly formatted HTTP response.

    From a cursory glance on websockets.org, it appears that the only thing web sockets is changing is making it simpler to send plain strings rather than complete HTTP messages. This solves the potential problem that when you get a response at the client, the (logical) connection is closed, so there's a gap until the client's next GET request arrives at the server before it can get a new event. So there's a limit to how fast you can receive the events, at least without some kind of trickery.

    Possibly, the web sockets API might also make some connection issue problems simpler, but otherwise it's really not a big deal for most people.

    I think most web servers won't ever serve sub-second events anyway, they're simple going to die from the load with many clients. Of course, in internal apps, the situation can be different. At lot of the new stuff in HTML5 is about extending the capabilities so web tech can supplant more of the traditional desktop apps.

    1. Re:Events are possible right now by Simetrical · · Score: 1

      From a cursory glance on websockets.org, it appears that the only thing web sockets is changing is making it simpler to send plain strings rather than complete HTTP messages. This solves the potential problem that when you get a response at the client, the (logical) connection is closed, so there's a gap until the client's next GET request arrives at the server before it can get a new event. So there's a limit to how fast you can receive the events, at least without some kind of trickery.

      If you're using WebSockets, you're not using HTTP at all; there's no such thing as GET. The web browser opens the connection, and keeps it open. Both client and server can push arbitrary strings to each other with network overhead about the same as pushing them directly over TCP (at least by comparison to HTTP). It means you don't have to poll the server at all, you can set up event handlers. This is drastically more efficient; it will enable things like webmail to be both more efficient and faster (get new e-mail instantly, not after you poll for it), and will also enable things like multiplayer games in HTML and JavaScript.

      WebSockets is a pretty big deal. Maybe not the most important part of HTML5, but still a big deal.

      I think most web servers won't ever serve sub-second events anyway, they're simple going to die from the load with many clients. Of course, in internal apps, the situation can be different. At lot of the new stuff in HTML5 is about extending the capabilities so web tech can supplant more of the traditional desktop apps.

      WebSocket servers are not HTTP servers. WebSocket is its own protocol, and servers will be written from scratch in practice. One of the design goals was to make this really easy, a couple hundred lines, so as not to inhibit adoption.

      --
      MediaWiki developer, Total War Center sysadmin
  64. Re:Firefox needs better support for security token by drinkypoo · · Score: 1

    I have no idea why they changed the keyboard shortcut that everyone except them had standardized on.

    Because it wasn't their way, and it's Steve's way or the highway. Seriously, I fucking guarantee you that it's a Steveism or similar. I'll bet a dollar and pay out the first citation that proves me wrong.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  65. What if the search engine doesn't know the URL by Anonymous Coward · · Score: 0

    I came across a browser for the iPhone, that offers only a search entry, with no way of entering a URL without searching. Even links in a page went through the search engine! As a result, pages too obscure for the search engine, were inaccessible to this browser.

  66. Re:Firefox needs better support for security token by Anonymous Coward · · Score: 0

    Where else would you put edit preferences?

    I just checked Microsoft Word 2010, finally finding it in the File menu, even though it's not related to files at all.

  67. The morning is a great time for bad analogies by Steauengeglase · · Score: 1

    We can pass out guns that fire bullets and guns that pop out little flags out that say, "bang". Why not mix them up? It is more convenient for people who want to buy products with triggers.

  68. Re:Does what to HTML 5? by Dausha · · Score: 1

    "Come on, mods: if you can't be honest about yourself, what can you be honest about? Shut off Olbermann and Beck, accept what our country is, and just deal with it. Seriously."

    I don't accept where our country is going, any more than I would accept my girlfriend is sleeping with my best friend. Some things require a reaction, especially "where things are going" is a retrenchment in what our ancestors sought to leave behind.

    --
    What those who want activist courts fear is rule by the people.
  69. Re:Does what to HTML 5? by Pojut · · Score: 1

    I was referring to recognizing the truth, rather than maintaining that America is the "best/most powerful/everyone should be like us" line of thinking.

    Poorly worded, on my part...sorry about that.

  70. Re:Firefox needs better support for security token by Phroggy · · Score: 1

    By the time Steve returned to the company in 1998, the command-semicolon shortcut was already a de-facto standard, which Apple was already ignoring. (Some Apple apps had no shortcut for Preferences, some had a random shortcut that wasn't consistent with anything.) However, it was under Steve's leadership that they came up with their own standard (that nobody else had ever used before).

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

    I think it is pretty terrible that the betas for Firefox 4 have all this brand-new CSS support for CSS3 but still FAILS at the Acid 3 test. Firefox is lagging in standards support, so we see the two most popular browsers, IE and Firefox, not supporting web standards, is it any surprise that the internet doesn't necessarily use them as well?

  72. Re:Firefox needs better support for security token by drinkypoo · · Score: 1

    By the time Steve returned to the company in 1998, the command-semicolon shortcut was already a de-facto standard, which Apple was already ignoring. (Some Apple apps had no shortcut for Preferences, some had a random shortcut that wasn't consistent with anything.) However, it was under Steve's leadership that they came up with their own standard (that nobody else had ever used before).

    New slogan... Apple, the NeXT ivory tower in the walled garden.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  73. Re:Does what to HTML 5? by improfane · · Score: 1

    I will talk in regard to my own country, the UK to represent my point without any bias towards America.

    If my country moves towards recycling and attempting to produce more serviceable electronics rather than consumer electronics, the localized impact will be less. Less waste will need to be disposed of in the UK. We'll adapt our processes and technologies to handle the unmaintainable produce from other countries that we inevitably import. It would reduce the number of landfill or incinerators needed to handle waste.

    Just because it won't solve the world problem if UK (far from it) starts being more responsible for the waste it produces, doesn't mean we should not try. The local benefits will be worth it.

    Pojut was not trolling. He's right.

    --
    Slashdot needs Geekcode | Can anyone recommend any good SCIFI? My tastes: Foundation, Startide Rising, CITY, Ringworld,
  74. Hah. by Anonymous Coward · · Score: 0

    If Firefox 4b1's HTML5 support is shining, then Chrome's is blinding.