In yet another interesting turn of events, two of the biggest issues when it comes to web design and development make way for the newer, better versions of themselves.
Goodbye, IE6!
Asa Dotzler of Mozilla reports that IE6 usage has now been overtaken by IE8, based on the browser tracking data from Net Applications. This happened as recently as June 2009.
Of course, specific demographics on your respective websites will vary, but this trend is a sign of things to come. And we’re not talking about years anymore, but months.
I’d have to commend Internet Explorer team on their great marketing efforts to improve the IE8 adoption rate. Even if Microsoft’s latest browser is up to snuff compared to the likes of Firefox, WebKit (Safari/Chrome), and Opera—see these comparison charts for HTML5—it’s a big step.
This is it, guys. Freedom.
Goodbye, XHTML2!
Slashdot reports that the XHTML2 Working Group charter is expiring by the end of 2009, and it will not be renewed. The W3C has also decided to pour more resources into the HTML5 working group.
Those who weren’t paying attention to this seeming sibling rivalry between XHTML2 and HTML5 can now rest easy. Though I’m not sure if XHTML2 ever stood a chance given how all the web gurus were backing HTML5 as early as last year. Google is on board, too. And everybody else is starting cash in on its growing popularity.
The good thing about XTHML was that it enforced well-formed markup, with strict provisions for lowercase code, quoted attributes, and trailing slashes for empty elements. Thankfully HTML5 this coding convention too, and can be served as a serialized XML document dubbed XHTML5.
At least we wouldn’t be forced to choose between the two anymore. Competition is good, but not here. We need standards.
Unwanted competition eliminated
How convenient is it that we have two less things to worry about now? Very, but now that they’re gone, it’s time to make up for lost time:
- Microformats. (This is the easiest to jump into.)
- Fluid layouts.
@font-face and custom web fonts: this time it’s not just the browser makers that web designers and developers are up against, but the type foundries. TypeKit and Kernest are attempting to bridge that gap.- CSS nested declarations, variables, and operations: LESS
- CSS if statements: Modernizr
- Animated PNGs.
Exciting times, people!
All the new browser updates seem to be coming out at the same time, which definitely keeps the competition interesting. But while you continue to scoff at IE, gush over Firefox, and smile nervously at Opera, Chrome, and Safari, have you heard that ordinary computer users don’t actually know what a web browser is? Let’s get to that in a bit…
Internet Explorer is the “best”
IE8 Comparison (comic by Brad Colbow)
I think people around the world made a collective ROFLMAO when the infamous IE8 browser comparison chart came out. I reserved any biased judgment when I first saw it, but oh my, Microsoft sure knows how to put its best features forward.
That’s not all it’s doing to promote the latest version of Internet Exploder, though. There’s a treasure hunt for $10,000 buried “online” (you have to use IE8 to find it, of course), and a donation of meals to charity (per IE8 download, of course).
Firefox has a new icon
New Firefox logo
Firefox is definitely the darling of the browser lot, so even a branding update—the fire, the fox, and the glossy globe are still intact and recognizable—is under magnified scrutiny.
Of course that’s not all there is to the next major release of Firefox, but I’m just glad they also care about their image. Lots of open source products pay little attention to the designery stuff. Firefox knows how to stay fresh and accessible to its audience without trying too hard (cough, see previous browser, cough).
Opera unites
Opera continues to innovate with its upcoming release, including an interface refresh from the same person who brought the Firefox logo to life. But it doesn’t stop there. Opera Unite cuts off the middleman for sharing photos, music, and all other kinds of files by turning the browser into a web server.
It’s not for everybody, but it’s a fascinating idea. An interesting twist to the “web as platform” concept. First there was web-based equivalents of desktop apps, as well as full-blown desktop interfaces on the web, then it was cloud computing, then it was the real-time web, then we have this. The jury’s still out on whether this will actually take off—considering Opera’s level of influence compared to the fox and the blue “e”—but any venture into Web 3.0 is a welcome effort. Here’s hoping we jump into it very soon.
But what is a web browser?
But apparently we can’t jump just yet. According to this discovery by The Next Web, the average internet user can’t tell the difference between a search engine and a browser, about 92% of those interviewed. Ironically, it was Google conducting the survey, and the final question was whether people knew that it had its own web browser.
Although Internet Explorer and Firefox were mentioned, people still didn’t know where the Web ended and the software began. It’s all just a blur of computer terms, which, at the end of the day, help them “find stuff”.
Knowing this, shouldn’t web browsers be scrambling to teach its users how the Internet works, including typing URLs into the address bar, and not just relying solely on search engines? Or should they just give up on the nth incarnation of the Browser Wars?
Andy Clarke of For A Beautiful Web has presented a stylesheet for the web browser we haven’t been able to push off the provebial cliff: Internet Explorer 6.
When I asked myself why people visit my sites, and the ones that I make for other people, the answer was always “for the content”. Content that is almost always written words and that means type.
That is why I’m now advocating to my clients (and to you), that where feasible, not to waste hours in time and a client’s money on lengthy workarounds in an unnecessary attempt at cross-browser perfection. Instead, you and I should provide simple but effectively designed HTML elements. This means just great typography for headings, paragraphs, quotations, lists, tables and forms and no styling of layout.
But this idea is not new; this Universal IE6 CSS file contains just enough rules for a practically unstyled but easy to navigate website. You’re basically giving websites loaded in a low-fi browser a low-fi experience. Examples here, here, and here.
Despite its waning popularity, we seem to have amassed a whole buffet of solutions to the shortcomings of IE6, ranging from the hostile upgrade messages and campaigns to the subtle conditional stylesheets and scripts.
I can just imagine someone creating one of those personality quizzes out of this whole debacle: which IE6 compatibility fix are you? There’s an idea.
But really, dealing with IE6 and somesuch boils down to principle and circumstance. Can your clients and your conscience accept barely recognizable version of their sites in twentysomething percent of their audience? Is your sanity more precious than squishing mysterious bugs? Or do you feel like throwing some humor in?
Let me know if someone’s actually made a personality quiz about this; I’d love to take it.
Everything old seems to be new (and hip?) again. And I’m not too sure I’m happy about it.
Short URLs
Shorter URLs are all the rage these days because of Twitter and its 140-character limit. If you’re one of the top sites on the web is practically mandatory for you to roll out your own URL shortening system. Ars Technica, for example, whose official URL is arstechnica.com, also has arst.ch. If you’re on a CMS like WordPress, you’re advised to give out the post ID permalink instead of the keyword-rich permalink of your blog post for the same reason.
Not too long ago, SEO and usability experts were on the same side and recommended readable URLs. Now that Twitter is the new internet marketing (I think they call it social media now) battlefield, the rules changed. When the next killer Web 3.0 app comes out, will we compromise and adjust once again?
But then again, has the Web ever stood still? Maybe I just thought it was beginning to.
WebKit’s CSS animations and scrollbars
You can now style scrollbars and perform animations using CSS in WebKit browsers.
I remember when Internet Explorer started to support scrollbar styling and almost every personal site took advantage of it. But then they grew out of it and were told by the gurus not to mess with the browser chrome.
I also remember <blink> and <marquee>.
But then again, “styling scrollbars isn’t messing with the chrome anymore than styling a button is.” Would the world be a saner place if browsers behaved the same way and all looked alike?
DiggBars
Digg has come out with its own version of the external page framing mechanism which they call the DiggBar.
Said mechanism is nothing new, and never really died out even to be considered a comeback, but Digg has a powerful following by all that which is noisy in the blogosphere to build a considerable amount of buzz. And no matter how you look at it, framing external pages is still framing, reminiscent of the era when HTML framesets were considered cool.
But then again, perhaps in this new era listening to the clamor of the crowd is no longer a fluke, but a very real way to improve one’s business.
Chrome Experiments is a cool new website rolled out by Google to promote its browser Chrome (which is out with version 2.0 beta, by the way) and to demonstrate the power and fun that can be had with the awesomeness of JavaScript and the browser chrome.
Emphasis on the small letter c. See how the site is named Chrome and not Google Chrome (although they effectively became synonymous because it’s Google)? This means most of the neat tricks can be accomplished on other modern browsers too. That is, after all, the idea of “moving to the cloud”—your web product must work in every browser and any other device possible. Of course, the idea is to promote Chrome and not really every other browser and device out there, but Google gets that that’s not the only goal. The experiments are best experienced while using Chrome and not the other browsers.
A short update on other browsers
Speaking of other browsers, let’s take a look at what they’ve been up to lately:
Now let’s go back to Chrome. Seems to me that this Chrome Experiments campaign is the most engaging one of its kind to come out in a long while. From real-time information visualization to graphics and sound rendering to games (both the classics and ones with a browser-based twist), these demos are just a delight to try out. See the compilation video below:
A short rant on other browser campaigns (yes, IE6)
Now, a note on “browser campaigns”. it’s like every other day I see a new site, piece of code, or banner that screams death to IE6! exclamation point! That’s it. Hardly any effort to get Microsoft and other companies to listen, it’s just screaming. I feel like IE6 is now an ace up one’s marketing sleeve, and no longer a real headache that web designers have to deal with everyday. Chrome Experiments makes more sense right now.
What Chrome’s made of
All the browsers claim they’ve got the fastest JavaScript engine of all, and maybe Chrome wants to put its money where its mouth is. It needs to; Google probably expected a better adoption rate for its browser because it’s Google, but it hasn’t happened (yet?). And while it’s nothing close to Spread Firefox or Mozilla Labs, it’s still a solid effort.
We do practically everything on a web browser these days. That’s how Google built itself from the ground. That’s why they rethought how browsers were made and came out with Chrome. Time to show what it’s really made of.
The World Wide Web created by Sir Tim Berners-Lee is 20 years old today. Even though I’m not the most qualified person to say this, its seems like several eternities have passed when you take a look at all that’s been accomplished.
And yet at the same time, it also feels like things have only started falling in place—ubiquitous and high-speed connections, uncompromised content delivery on mobile devices, live streaming and other real-time services, data portability and APIs, and so on. Some feel that the Web can be better, but it has to be rebuilt from the ground up:
Instead of merely jury-rigging fixes into the existing Internet, Peterson and Rexford believe much can be learned about possible improvements by designing a new network from the ground up — one that parallels the existing Internet, on which researchers can run their most innovative experiments.
If we have to revamp the Web it’s better to do so now, or sooner rather than later.
Maybe the infrastructure itself doesn’t need the overhaul, but only certain features. Thomas Baekdal considers a new domain system. Internet Explorer is reportedly getting a brand new browser rendering engine, taking a cue from Google Chrome. And dare I include the Web 2.0 phenomenon, which to its credit wasn’t a complete fad: we got YouTube, Facebook, and Twitter from it, after all. All address different aspects of the Web, but each one’s a game-changer in its own right.
The key here is people are rethinking rather than building on top of things. But will it come full circle, only for people to realize too late that starting from scratch was a much better way? The endeavor feels so large and drastic that it’s too daunting to even consider.
Some chunks of good browser-related news at the turn of the new year: Firefox browser usage is more than 20% now, while Internet Explorer, especially IE6, is declining—forcibly and otherwise!
Firefox market shares are rise, IE shares decline
Browser market share from October to December 2008
For the first time ever, Net Applications is reporting that Mozilla Firefox market shares passed 20% while Microsoft Internet Explorer dropped below 70%. Four major factors are said to explain Firefox growth, from the US elections to longer weekends/holidays, and higher unemployment—all US-centric factors.
Browser version market share December 2008
Here’s a chart by browser version. IE7 remains the dominant browser in the market, while IE6 is still at number 2, having almost the same percentage as all Firefox versions combined. But it has declined from the 21-22% range in the last quarter of 2008.
Google Chrome barely leaves a dent at 1%, but surpasses Opera at 0.7%.
Google urges IE6 users to upgrade
Get faster Gmail notice in IE6 (image courtesy of Ars Technica)
According to TG Daily, Google’s Gmail is now sporting a message specifically for IE6 users to upgrade and “get faster Gmail”.
The link leads to a page that promotes Chrome and Firefox 3. “Browsers are getting faster and better at running web applications like Google Mail that use browser technology to its limits,” the page reads. “In order to get the best experience possible and make Google Mail run an average of twice as fast, we suggest that you upgrade your browser to one of the fastest Google Mail supported browsers that work on Windows.” The page offers direct download links for Firefox 3 and Chrome. IE7 and Apple’s Safari are listed as supported Gmail browsers.
Several modern browsers are listed in the linked page, and unfortunately Opera is no longer qualified on that list. At least Google is trying to be fair by mentioning competitors to its own browser, Chrome. More importantly, at least it realizes that the browser share for such an old and run-down browser are alarmingly high. Looks like it’s getting costly to maintain backwards compatibility for JavaScript-intensive web applications like Gmail.
This is not the first time that a large company is forcing its hand. Apple’s MobileMe recommends only 2 browsers: Safari, which it owns, and Firefox.
There is hope!
With the combination of natural factors and some nudging from the big, influential companies like Google and Apple, the obsolete browser that is IE6 might just retire sooner than we expect, sooner than never.
Between Apple computers gaining popularity and Google remaining just as powerful, their influence on which becomes the default browser in controlled environments will be needed to level the playing field, ultimately pushing the capabilities of web browsers forward.
Contrary to popular belief, Microsoft is committed to building a better web with with a redesigned MIX Online and its horde of interesting resources, from articles to web development tools to delightful goodies.
We’ve all been guilty of bashing Microsoft for several different reasons, but now is a great time to give it a second (or a hundredth) chance. After all, it’s Christmas!
Articles and Opinions
Let’s start with readable sources on MIX Online, the Articles and Opinions sections. Skim through them and you’ll get a good sense that MIX Online shaping up to be a reputable web design source that’s passionate about web standards, user experience, and best practices. Read Nishant Kothary’s walkthrough of the site redesign, transforming moleskine sketches to a cool community running on their new CMS platform (more on that later).
more
In a recent developer conference in Sydney, someone asked Microsoft CEO Steve Ballmer why they’re spending so many resources on their beloved browser, Internet Explorer:
Why is IE still relevant and why is it worth spending money on rendering engines when there are open source ones available that can respond to changes in Web standards faster?
According to Techworld, this was his reply:
Ballmer began his answer philosophically, saying Microsoft will need to look at what the browser is like in the future and, if there is no innovation around them, which he thinks is “likely”, Microsoft may still need its own browser because of proprietary extensions that broaden its functionality.
“Open source is interesting,” he said. “Apple has embraced Webkit and we may look at that, but we will continue to build extensions for IE 8.”
So now if we can imagine Microsoft actually swallowing its pride to rework IE to use the same code Apple is using with Safari, and Google with Chrome, we’d have 3 competing browsers by 3 technological giants using the same foundations for building a browser. It would seem like good news for those who’ve spent sleepless nights keeping websites from breaking due to IE’s numerous bugs, although I’m not quite sure why have to have 3 different derivatives of WebKit in the first place—which is an issue for another day.
I want to go back to the question of relevance. Ballmer didn’t exactly defend IE’s relevance, even saying that there is likely to be “no innovation around them”. Are you sure? Mozilla definitely thinks otherwise. So does Google.
Add to that Microsoft’s foray into the “cloud” with Windows Azure. Google, which wanted to make sure its web apps provided the best experience, created its own web browser. IE has been around for years now, but what could be crucial to next-generation platform computing seems to be an afterthought, or is just playing catch-up.
If we were to actually take Ballmer’s words to heart, we can expect that either way, web browsing should improve for the better: either through a Webkit-based IE, or the death of IE.
It may very well be the latter, if we’re to believe this comment on the article at the AppleInsider forums:
The IE team was dismantled except for a core team called IE SE – which translates to “IE Sustained Engineering”. What this means… is a product is dead and the SE team simply puts out hot-fixes for any pertinent issues. This all happened during that great legal battle that Microsoft had with the States.
I know we can accomplish a lot more by not waiting around for IE (and Microsoft) to get its act together, but here’s yet another reason web designers and developers are in a rut.
If the company behind Internet Explorer does not believe in it, why should we?
All the hoopla over Everything You Know About CSS Is Wrong!, a book by Rachel Andrew and Kevin Yank (see also the Digital Web article) is making me feel uneasy.
We’re not wrong; the title is wrong
I detest the title of the book. No, I don’t think “everything” I know about CSS is wrong. I “know” about the display:table technique for months now (thanks to Sitepoint, again).
Neither do I think it’s a good idea to go around belittling people by telling them they are wrong, whether in printed book or online article format. It’s harsh and misleading.
We’ve got issues
As for the CSS Tables technique presented in the book, these are some of the issues plaguing it:
- tag soup
- lack of source order control
- the question of semantics and presentation vs. content: is making
<div>s behave like tables/table cells any different from using tables as layouts?
- IE6 and IE7 incompatibility (no surprise there!)
And not too long after the uproar, the authors have addressed the above problems:
Andrew Tetlaw responds to #1 and #3:
No one is negatively affected by the overuse of structural div tags. The same can’t be said for the use of HTML tables for layout.
And here’s an interesting quip which points out the very valid woe of web developers, who have had to adjust to all these changes in coding conventions because of our “flakiness”:
Congratulations on years of punishing web devs for using common sense. Finally the circle turns, but somehow you think that you were ‘right all along.
Matthew Pennell of Digital Web has this to say about those who question semantics and standards:
I must say that I’m surprised that an audience of (presumably) conscientious, standards-aware developers are almost all declaring that they will not use new features of CSS when they are available and supported. Are you all so short-sighted that you cannot see any application for the techniques discussed here beyond wholesale replacement of site layouts?
And Rachel has written this regarding #4:
Some commentators have suggested that we shouldn’t have put a book out about a technique that can’t be used immediately, that will require workarounds to still provide support for older versions of Internet Explorer. I disagree. Something I point back to in the book is how the web community began to use CSS for layout even though support in Netscape 4 was limited and buggy. If those of us who were building CSS layouts right in those early days had said, “nah, it doesn’t work in Netscape, can’t do it”, then our recent history would look very different.
Are we hesitant about change and innovation?
In a sense, browser usage does “cripple” our ability to look towards a future of web design innovation (and bliss) when IE6 is finally disappears. But are things right now are exactly the same as when Netscape Navigator 4 was the stumbling block?
More importantly, will the CSS Tables technique actually push our level of innovation by a significant degree? The past few months of new websites tell me innovation is not too hard to come by still.
And what about next-generation HTML5, which will have new structural tags like <header>, <section>, <article>, <footer>? Can one not feel guilty using all those <div>s in the midst of these elegant new tags? Perhaps that’s another debate for another day—in 2022.
*/
