from a Yahoo! and XML geek

Quick Links: Consulting | Book info | Brain Attic | Home

Push Button Paradise

Micah Dubinko

Mon, 17 Apr 2006

Night of the living dead browsers

Imagine yourself as a web developer. You wake up one day in an alternate universe, one with no Firefox Web Developer extension. No DOM inspector, no JavaScript debugger. In fact, no Firefox at all.

No Safari, not even IE. Opera is still around and kicking, but every other browser on the planet has been replaced with a randomly mutated copy of Navigator 3.0, with "View Source" disabled. Over a dialup-speed pipe.

As you get desperate to debug some content that appears horribly mangled on your particular mangled browser, you start making a catalog of what works and what doesn't--and there's no discernible pattern. CSS works on some browsers, and crashes others. Meaningless differences make the difference between working, not working, and crashing. Ditto for XML declarations. And DOCTYPE declarations. And tables (Well, maybe there are a few advantages in this universe).

In a place like this, what role does separating content and presentation play? How important is semantically-meaningful markup that results in unusably-bad displays on a significant fraction of the browser population? How much of what you've learned over the years about usable and accessible web design goes out the window? How do you make the pain stop?

Welcome to the mobile web, 2006. The questions above aren't rhetorical. Answer in comments below.

(Not to sound too negative, but this situation is actually a vast improvement over the way things were even five years ago.) -m

posted at: 23:05 | under: 2006-04 | 2 comment(s)



Somehow lure some key geeks and suits from different browsers, both the large marketshare and especially the small ambitious browsers together, then open up a wormhole and bring them all back to the world that is learning to appreciate the use of standards, choice and developer tools and put them in key learning environments.

Then you take a bunch of the worst spammers from earth and take them to this parallel universe where they´ll pay the browser aliens for browsers that will get their stupid-old messages to all creatures, e-mail and web, as they´re used to. After the alien browser builders have literally eaten all the spammers´ money, and other aliens keep contacting the spammers but never buying any of the spammers products (who needs viagra with such low gravity) the spammers gone bankrupt and browser builders have learned something about making a profit with using standards.

Then you take a bunch of standards-loving webdevelopers (take a few rather smart ones, they always no better, just to get some variation and competition in browsers :-) ) from earth and send them to this alternate universe where companies are now very eager to hire them.

Opera would do rather well in that universe


OR: make a (ironic) FireFox Flick video about MiniMo :-)
Posted by stelt at Tue Apr 18 00:26:24 2006

I am somewhat more optimistic. Some of the browsers frankly deserve to die (possibly to reincarnate as a immensely improved product), and some already have. I think the changes are likely to happen faster in the phone world than the in PDA world. Partly because the phone world is vastly larger and the PDA world is dying off, and partly because now that the phone world is leaving the WAP delusion behind they are requiring basic standards support for the browser to be installed on the phone to begin with.

But as most phones use proprietary operating systems (excepting the "smartphones"), with limited opportunities for upgrades, ghosts of the browsers past will haunt us for some time to come.

In principle the phone world should be, and in time will be, a poster child for semantic markup. I know that our capability to adapt the content to the device is greatly improved when we know what the content actually is. In the WAP world you had no such opportunity, if you wanted to add an 'h3' you would have to do something like "<b><big><big>" to achieve a similar effect, Netscape 3 indeed. Another consequence is that a well-crafted HTML document is always smaller than the equivalent WML document. In the phoney zone that matters.
Posted by Jonny Axelsson at Tue Apr 18 03:23:09 2006


Syndicate: RSS feed

What am I reading?
Don Quixote
Self-Editing for Fiction Writers
The Complete Joy of Homebrewing
Analog magazine
Compilers
TAOCP


What am I browsing?
BlogFour
Blake Ross
Brianstorms
Caveat Lector
Claus Wahlers
Copia
Cringely
David Temkin
Dave Hyatt
Groklaw
Mark Birbeck
M.David
Miguel de Icaza
Mitch Kapor
Norm Walsh
Omar Tazi
Sean McGrath
Sjoerd Visscher
Ted Leung
Tom Bradford
Wil Wheaton


Archives:
Link

Powered by PyBlosxom