6 ms·

>Chrome is ahead in some areas, but behind in others. Correct, but as a whole, it's significantly more ahead than Firefox, and it's way, way, way ahead than ev

>Chrome is ahead in some areas, but behind in others. Correct, but as a whole, it's significantly more ahead than Firefox, and it's way, way, way ahead than even the latest version of IE. What you said doesn't contradict that point.

azakai 14y ago
I don't agree that it is "significantly more ahead than Firefox" - can you back that up? There is a long list of features that each of those browsers has, that the other does not. As for IE, I don't run Windows, so I know less about it.
- Retric 14y ago
  Chrome 463, Firefox 393 that's a fairly large gap IMO. http://html5test.com/results/desktop.html http://html5test.com/results/desktop.html
  - azakai 14y ago
    The numbers there are highly arbitrary - some things have large subcategories and so a big final number, while huge features like WebGL have few subcategories and a small final number. The numbers there are just an arbitrary decision by, AFAICT, one person. Edit: Also, that does not include JS features at all. The modern web isn't just HTML ;)
- unconed 14y ago
  Firefox: * No CSS shaders * CSS 3D is still very buggy (http://acko.net/#force3d http://acko.net/#force3d) despite the support being over a year old now. Also renders without anti-aliasing, which makes it really ugly. * Both Firebug and the built-in inspector seriously lack compared to Chrome's dev tools which has a per-frame timeline, profiler, etc. Instead they added the rather pointless 3D tilt view of the DOM which doesn't show you the actual DOM layers (unlike this 5 minute CSS 3D hack: http://www.youtube.com/watch?v=2-oQj9Y9I6I http://www.youtube.com/watch?v=2-oQj9Y9I6I) and hence is just a misleading gimmick. * No in-browser code editing/saving * No Web Audio API * No desktop notifications * No MP3, no AAC, no H.264 support (on OSX anyway), the three most common audio and video codecs. * No date/time picker, no color picker, no number range field Yeah, I know there are reasons behind this, but still, the picture is heavily skewed in Chrome's favor As for IE... CSS 3D support is incomplete (no nesting), its dev tools are pretty crap, and they seem to be actively ignoring standards like WebGL and pushing their own spec for WebRTC.
  - azakai 14y ago
    Those are indeed features that are missing from Firefox, yes. Although several are already there in nightly builds (WebAudio, number range, for example). As I said earlier, it is easy to compile such a list from the other direction, stuff Chrome is missing. A few off the top of my head: * A wide range of ES6 features, see http://kangax.github.com/es5-compat-table/es6/ http://kangax.github.com/es5-compat-table/es6/ * Proper fullscreen mode (resized) * OPUS codec * Microdata * Scoped style * asm.js * etc. All those are in Firefox. Again, both Firefox and Chrome are ahead of each other in various ways. Deciding which is "overall" more ahead means which features you care about - do you care more about JS language features or HTML forms? WebAudio or Opus? etc. There is no clear winner.
    - greggman 14y ago
      * asm.js is not a standard and was only announced 2 weeks ago. Hardly a fair comparison. * ES6 features? All disabled on FF19. * OPUS codec? Who uses that? Which codecs to support is not part of any standard. Browsers are free to support what they want. But at the same time, not being able to play the most common audio and video formats seems like a far bigger issue. * What's "proper fullscreen mode?"
      - azakai 14y ago
        asm.js is not a standard, but neither are various things on html5test. I agree it and those other things are less important though. Not all ES6 features are disabled? For example WeakMap. OPUS would be used by more people if more browsers than Firefox supported it ;) Proper fullscreen mode is fullscreen where the element has the right css, that makes it fill the screen as per the spec. Chrome does not do that yet.

azakai 14y ago

I don't agree that it is "significantly more ahead than Firefox" - can you back that up? There is a long list of features that each of those browsers has, that the other does not. As for IE, I don't run Windows, so I know less about it.

Retric 14y ago
Chrome 463, Firefox 393 that's a fairly large gap IMO. http://html5test.com/results/desktop.html http://html5test.com/results/desktop.html
- azakai 14y ago
  The numbers there are highly arbitrary - some things have large subcategories and so a big final number, while huge features like WebGL have few subcategories and a small final number. The numbers there are just an arbitrary decision by, AFAICT, one person. Edit: Also, that does not include JS features at all. The modern web isn't just HTML ;)
unconed 14y ago
Firefox: * No CSS shaders * CSS 3D is still very buggy (http://acko.net/#force3d http://acko.net/#force3d) despite the support being over a year old now. Also renders without anti-aliasing, which makes it really ugly. * Both Firebug and the built-in inspector seriously lack compared to Chrome's dev tools which has a per-frame timeline, profiler, etc. Instead they added the rather pointless 3D tilt view of the DOM which doesn't show you the actual DOM layers (unlike this 5 minute CSS 3D hack: http://www.youtube.com/watch?v=2-oQj9Y9I6I http://www.youtube.com/watch?v=2-oQj9Y9I6I) and hence is just a misleading gimmick. * No in-browser code editing/saving * No Web Audio API * No desktop notifications * No MP3, no AAC, no H.264 support (on OSX anyway), the three most common audio and video codecs. * No date/time picker, no color picker, no number range field Yeah, I know there are reasons behind this, but still, the picture is heavily skewed in Chrome's favor As for IE... CSS 3D support is incomplete (no nesting), its dev tools are pretty crap, and they seem to be actively ignoring standards like WebGL and pushing their own spec for WebRTC.
- azakai 14y ago
  Those are indeed features that are missing from Firefox, yes. Although several are already there in nightly builds (WebAudio, number range, for example). As I said earlier, it is easy to compile such a list from the other direction, stuff Chrome is missing. A few off the top of my head: * A wide range of ES6 features, see http://kangax.github.com/es5-compat-table/es6/ http://kangax.github.com/es5-compat-table/es6/ * Proper fullscreen mode (resized) * OPUS codec * Microdata * Scoped style * asm.js * etc. All those are in Firefox. Again, both Firefox and Chrome are ahead of each other in various ways. Deciding which is "overall" more ahead means which features you care about - do you care more about JS language features or HTML forms? WebAudio or Opus? etc. There is no clear winner.
  - greggman 14y ago
    * asm.js is not a standard and was only announced 2 weeks ago. Hardly a fair comparison. * ES6 features? All disabled on FF19. * OPUS codec? Who uses that? Which codecs to support is not part of any standard. Browsers are free to support what they want. But at the same time, not being able to play the most common audio and video formats seems like a far bigger issue. * What's "proper fullscreen mode?"
    - azakai 14y ago
      asm.js is not a standard, but neither are various things on html5test. I agree it and those other things are less important though. Not all ES6 features are disabled? For example WeakMap. OPUS would be used by more people if more browsers than Firefox supported it ;) Proper fullscreen mode is fullscreen where the element has the right css, that makes it fill the screen as per the spec. Chrome does not do that yet.