Archive for the ‘Browsers’ Category

IE 10 Specific Styles

Browsers, Internet Explorer | Posted by Keefr June 12th, 2013

I missed this, but Internet Explorer 10 removes the ability to parse out the conditional style sheets, the browser in the past has often required to get it inline with what every other browser was doing. Obviously, this hasn’t caused too much alarm because IE 10 has played catchup to the rest of the modern browsers.

I haven’t come up with a need to specifically target IE10, but the link below gives a way to do it. It would in a pinch, also allow you to target any given browser, as long as you knew and targetted its user agent string.

IE 10 Specific Styles

CSS Idea: /*autoprefix*/

Browsers, CSS | Posted by Keefr May 22nd, 2013

Love this idea from David Walsh. Prefixes are the bane of CSS, and I love the idea of the web browser becoming the processor for CSS properties that it knows need prefixing.

The one complexity comes in with prefixes that change the syntax within the properties. This may be a case that only applies to older versions of IE (examples I’m thinking of are all old IE browsers). But auto prefixing would old help with new browsers going forward, unless I’m misunderstanding.

Autoprefix for older browsers would have to have a JS framework to work for older versions of browsers. Beyond that, I’m not seeing any reason why browsers going forward couldn’t and shouldn’t auto prefix.

CSS Idea: /*autoprefix*/

Paul Irish on Chrome Moving to Blink

Browsers, Chrome, CSS, WebKit | Posted by Keefr May 17th, 2013

Yay, no prefixes in the CSS! They seem pretty adamant about it. I really hope it works out well and becomes the standard to you know… use the standards.

Paul Irish on Chrome Moving to Blink

Usage Share of Web Browsers

Browsers | Posted by Keefr May 5th, 2013

A co-worker shared this with the Interactive team a couple weeks back. Wikipedia has a nice page on what web browsers are being used where worldwide:

Usage Share of Web Browsers

WebKit Releases New SunSpider 1.0 Benchmark to Chart the Future of JavaScript Performance

JavaScript, WebKit | Posted by Keefr May 2nd, 2013

Benchmarks are all over the place, but the interesting bit about this one is that this one is really spurred by Google forking the Webkit project, making its own spinoff called “Blink,” which allows it to separate itself from Apple’s Nitro JS processor, which Chrome doesn’t utilize.

Samsung (and others) end up as the odd men out though, as it uses the Apple WebKit Engine, but Chrome’s V8 JS engine. Things could get interesting going forward if these forks… well fork more.

WebKit Releases New SunSpider 1.0 Benchmark to Chart the Future of JavaScript Performance