Chris Wilson : If you (the page developer) really want the best standards support IE8 can give, you can get it by inserting a simple element. Aaron gives more details on this in his article . Aaron Gustafson : ...
Compatibility and IE8
blogs.msdn.comFound 165 days, 3 hours, 56 minutes, and 39 seconds agoto enable different "modes" of behavior to protect compatibility. When we released IE 6 in 2001, very few pages on the web were in "standards mode" (my team ran a report on the top 200 web sites at the time that reported less than 1%) - few people knew what a DOCTYPE was, and few tools generated them.
Well, I'm Back:
weblogs.mozillazine.orgFound 164 days, 22 hours, 49 minutes, and 42 seconds agoSpotted by: WebKit: Versioning, Compatibility and Standards W3C QA: IE8 versioning snowstorm Simon Willison: /a>
Microsoft's Version Targeting Proposal
webstandards.orgFound 164 days, 18 hours, 48 minutes agoOver at A List Apart today is Aaron Gustafson's article Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 , introducing a controversial proposal from Microsoft that developers should start locking their pages into set browser versions. ...
Has Internet Explorer Just Shot Itself in the Foot?
andybudd.comFound 164 days, 14 hours, 38 minutes, and 20 seconds agoIf you haven't read the latest posts on A List Apart , you should pop over now. Don't worry. I'll be here when you get back. Beyond DOCTYPE : Web Standards, Forward Compatibility, and IE8 From Switches to Targets: ...
Microsoft to add a 'super standards' mode to IE 8
blogs.zdnet.comFound 164 days, 18 hours, 46 minutes, and 41 seconds agoMicrosoft is planning to add a new, opt-in "super standards" mode to Internet Explorer (IE) 8 -- a move of which some developers are critical. IE Platform Architect Chris Wilson shared the details of how Microsoft plans to provide the greater standards compatibility, which it has promised for its next ...
Opera, Mozilla and Safari react to IE's solution for browser compatibility issues
operawatch.comFound 163 days, 17 hours, 20 minutes, and 22 seconds agoThere has been lots commentary and discussions regarding Microsoft's solution to fix compatibility issues between various versions of Internet Explorer (IE). For a good background on this, read Aaron Gustafson's post on the A List Apart blog . ...
HTML5 Shiv
ejohn.orgFound 163 days, 2 hours, 34 minutes, and 35 seconds agoAssuming that it'll be a while before most browsers attempt to implement most of HTML 5 (a perfectly reasonable assumption) we need to start thinking of ways to tackle the creation and rendering of HTML 5 components in the meantime. ...
digital-web.com
Mike Davies says it's the end of the line for IE
Found 164 days, 16 hours, 36 minutes, and 38 seconds ago
ln.hixie.ch
Spotted by: Mark Pilgrim: Microsoft koan Sam Ruby: Sunsetting Quirks Mode Simon Willison: A quote from Ian Hickson
Found 164 days, 23 minutes, and 4 seconds ago
ajaxian.com
This is an example from John Resig as he discusses a HTML 5 shiv . You can see how a JavaScript shim can "implement" some of HTML 5 for us.
We have also gone down this route for some of the HTML 5 spec, and you can indeed do a lot with JavaScript. There are a couple of places where you kinda have to be in the browser to do the right thing.... but these are few and far between.
Sjoerd Visscher just blogged about this and told us how he found it out (back in 2002-ish!):
As far as I can remember we found out about this when we converted the first rendering of the XSL output from a lot of createElement calls to one innerHTML change for performance.
Found 162 days, 20 hours, 32 minutes, and 19 seconds ago
ajaxian.com
Then, Eric Meyer came out to talk about switches versus targets :
The second major difference between browser sniffing and version targeting is that browser sniffing looks forward while version targeting looks back. Looking forward is one big reason browser sniffing is fragile: it's hard to predict the future. To pick one example, Safari's inclusion of "like Gecko" in its user-agent identifier broke a fair number of sniffer scripts-even those that were comparatively well done. The authors of those scripts had simply failed to predict that a non-Gecko browser from Apple would include the word "Gecko" in its user-agent identifier.
Found 164 days, 13 hours, 27 minutes, and 46 seconds ago
osnews.com
"In Dean's recent Internet Explorer 8 and Acid2: a Milestone post , he highlighted our responsibility to deliver both interoperability (web pages working well across different browsers) and backwards compatibility (web pages working well across different versions of IE). We need to do both, so that IE8 continues to work with the billions of pages on the web today that already work in IE6 and IE7 but also makes the development of the next billion pages (in an interoperable way) much easier. Continuing Dean's theme, I'd like to talk about some steps we are taking in IE8 to achieve these goals .
Found 164 days, 11 hours, 43 minutes, and 35 seconds ago
bink.nu
(in the WaSP-Microsoft Task Force )
on this problem. I can't give them enough credit for this work; it's
tough to step into the shoes of a browser vendor that ships to half a
billion users to figure out what the best thing to do is, when you
really just want to sit down and write code to the standards.
Found 165 days, 3 hours, 56 minutes, and 41 seconds ago
alex.dojotoolkit.org
So IE is the first browser out of the gate to do something sane about rendering engine locking to content …and good on them for it.
Now we need to know a couple more details to see if it's going to have real legs:
Found 163 days, 23 hours, 33 minutes, and 47 seconds ago
shauninman.com
Flame-retardant "If you feel the need to impugn the integrity or intelligence of another person to oppose an idea, you're undercutting yourself, not your target nor the thing you oppose." I want this on a t-shirt. Seriously. Can we make that happen?
Hit me on my iPhone "You might catch me talking to a tender lovely lady but I'm yapping through the earbuds so you probably thought I'm crazy." (via URN )
Layer Tennis People's Choice Vote for your ideal head-to-head from this past season's participants.
Found 163 days, 16 hours, 8 minutes, and 18 seconds ago
tinfinger.blogspot.com
An article this week on the Web design bible A List Apart lets us know the latest plans by Microsoft to embrace and extend the way HTML is rendered in Web browsers. Apparently in consultation with ALA boffins, Microsoft has agreed to implement a new meta declaration in the head section of HTML documents in their forthcoming Internet Explorer 8 release.
Found 163 days, 11 hours, 25 minutes, and 5 seconds ago
itwriting.com
Microsoft's Chris Wilson has a post on Compatibility and IE8 which introduces yet another compatibility switch. IE8 will apparently have three modes: Quirks, Standards, and Even More Standard.
Here's the key paragraph: ...
Found 164 days, 11 hours, 1 minute, and 18 seconds ago
simonwillison.net
No matter what great leaps forward the Internet Explorer team make from now on, the majority of developers won't use them and the majority of users won't see them. By doing this the Internet Explorer team may have created their own backwater, shot themselves in the foot and left themselves for dead. - Andy Budd
Found 164 days, 21 hours, 33 minutes, and 17 seconds ago
winbeta.org
CNET has published an article called Acid2, Acid3 and the power of default . The article predicts that IE8 will not pass the Acid2 test after all: '[Another] scenario could be that Microsoft requires Web pages to change the default settings by flagging that they really, really want to be rendered correctly. Web pages already have a way to say this (called doctype switching, which is supported by all browsers), but Microsoft has all but announced that IE8 will support yet another scheme . If the company decides to implement the new scheme, the Acid2 test - and all the other pages that use doctype switching - will not be rendered correctly.
Found 163 days, 14 hours, 58 minutes, and 21 seconds ago
1060.org
This is pretty painful to watch: The IE team announcing that IE
will
default to being bug-compatible with IE7, unless the page/web
server says otherwise.
Why would they do that? Some possibilities:
Found 163 days, 12 hours, 27 minutes, and 22 seconds ago
pods.lv
Pirmā doma, kas iešāvās prātā bija - idiņi. Ir taču vienots standarts, kas ir nodefinēts W3C dokumentācijās un kuru lieto visa civilizētā pasaule, bet nē, viņi atkal izdomā kaut ko savu - Microsoftisku. Un tad jūs man pārmetat, ka es ironizēju par Microsoft centieniem kļūt baltākiem.
Iespējams, ka izlasot skaidrojumu par jauno IE8 īpašo standartu režīmu IE blogā un A List Apart manas domas mainīsies.
Popularitāte: 22%
Found 164 days, 23 hours, 26 minutes, and 17 seconds ago
cssdrive.com
Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8
Found 164 days, 19 hours, 23 minutes, and 58 seconds ago
saila.com
IE8 and future compatibility
Found 164 days, 11 hours, 43 minutes, and 23 seconds ago
novemberborn.net
So . The good news is that IE8 will be much, much better than anything before it. The bad news, Microsoft doesn't dare release it and make it render existing websites, because there's no way they're going to render properly. Why? Because of the browser specific hacks put in to make the site render properly in IE6/7.
A "kill switch" is proposed, which will cause websites to render in the new or updated engine, whilst not breaking existing websites relying on IEs quirks.
Fair enough.
link
Found 164 days, 3 hours, 37 minutes, and 47 seconds ago
jystewart.net
and Sam Ruby and his commenting crowd considering the technical implications.
Reading all the debate it can be hard to separate feelings about this specific idea from a basic resentment against Microsoft that is harboured by most web developers I know. The failure of Internet Explorer to keep up with web standards has cost many of us, in aggregate, months of work, and our clients lots of money. The time we've spent supporting broken browsers could have been time spent improving the user experience or developing exciting new uses for the web.
Found 162 days, 22 hours, 39 minutes, and 30 seconds ago
cybernetnews.com
The Internet Explorer team is at it again pointing out that Internet Explorer 8 is looking to closely follow the web standards we've all become accustomed to in other major browsers. Earlier they demonstrated that IE 8 currently passes the Acid 2 test , and the IE blog actually admitted their lacking of compliance with the standards in the past:
Iâve been on the IE team for over a decade, and Iâve seen us apply the âDonât Break the Webâ rule in six different major versions of IE in different ways.
Found 164 days, 10 hours, 23 minutes, and 4 seconds ago
opuszine.com
Has Internet Explorer Just Shot Itself in the Foot? : No matter what great leaps forward the Internet Explorer team make from now on, the majority of developers won't use them and the majority of users won't see them. By doing this the Internet Explorer team may have created their own backwater, shot themselves in the foot and left themselves for dead. If this comes to pass, it couldn't have happened to a more deserving browser.
Found 164 days, 9 hours, 10 minutes, and 21 seconds ago
bannister.us
There is once again talk about versioned web pages. Unfortunately there is also the same continuing confusion between theory and reality.
A List Apart: Articles: Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8
Found 164 days, 2 hours, 24 minutes, and 10 seconds ago
andrewdupont.net
Aaron Gustafson's Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 is something I've been anticipating for a while.
Read that article. Then come back here.
It's the answer to a question that has been on many of our minds ever since the Acid2 announcement , one in which Dean Hachamovitch makes passing reference to "IE8 Standards Mode." Yes, this is an actual thing. Yes, it goes beyond ordinary Standards Mode, which requires only a DOCTYPE declaration.
In other words: Acid2 was the good news.
Found 163 days, 11 hours, 59 minutes, and 52 seconds ago
mtaa.net
Crazily enough, Zeldman and the WASP seem to be on board with a blog post and 2 (count 'em 2) articles on A List Apart ( 1 , 2 ).
Found 164 days, 19 hours, 23 minutes, and 37 seconds ago
weblog.juima.org
Mozilla Messaging
Found 164 days, 12 hours, 15 minutes, and 33 seconds ago
ejohn.org
January 22nd, 2008
Wanna know how I can tell that no other browser vendor participated in the creation of the new meta X-UA-Compatible tag? Because it's completely worthless - and in fact harmful - for any browser to implement!
I love this example from the overview article , including Firefox 3 as an example:
Found 164 days, 10 hours, 54 minutes, and 53 seconds ago
blogs.smugmug.com
Over on IEBlog and A List Apart , they detail a new flag for the upcoming IE8 that would enable you to "lock" the browser down to older versions should you be expecting older broken behavior from IE6 or IE7.
This is a bad idea. The Safari team has a great write-up about why they think it's a bad idea, which I agree with, but I also have an additional take:
Pages and sites that are likely to care about this are poorly written and poorly maintained. Microsoft created this problem themselves when they let IE6 sit idle for more than half a decade, and now they have to deal with it.
Found 163 days, 17 hours, 23 minutes, and 44 seconds ago
prototypen.com
no - Microsoft "invents" another totally new metatag and expects everyone to go over their pages and include it. Really what the freak are they smoking? Break the fucking backwards compatibility and finally make everyone just abandon IE6 - its a freaking dead horse that was born in the internet dark ages - and don´t pull along the stupid non working code - I am totally utterly sick of it. I hope this will further alienate developers from IE to the point where IE has MUCH less market share then the other browsers that are actually standard compliant from the get go and don´t need no freaking quirks mode to operate properly.
Found 163 days, 11 hours, 23 minutes, and 27 seconds ago
silverspider.com
Having spent some time digging into the various arguments around IE 8's plan to address compatibility concerns since my first post on the subject , I've shifted away from my initial embrace of the plan. While I'm not as deeply entrenched as many on the Net, I see this as a major problem. Microsoft will implement this change no matter what, and many developers will make use of it. It may start with bits and pieces - a quick fix to address one incompatibility, but in time we'll see it crop up in corporate-wide, multi-site environments - like your bank.
Found 161 days, 18 hours, 21 minutes, and 47 seconds ago
quirksmode.org
IE8 and the future of the web
Found 177 days, 34 minutes, and 29 seconds ago
chunkysoup.net
Opting-in to standards support and Microsoft's Version Targeting Proposal at the WaSP
Found 164 days, 17 hours, 39 minutes, and 3 seconds ago
pronetworks.org
complete article
Tags: Internet , Microsoft Corp. , Microsoft Internet Explorer , Mode , Standards , Web browsers
Found 164 days, 17 hours, 25 minutes, and 33 seconds ago
technudge.net
Microsoft is planning to add a new, opt-in "super standards" mode to Internet Explorer (IE) 8 - a move of which some developers are critical.
IE Platform Architect Chris Wilson shared the details of how Microsoft plans to provide the greater standards compatibility, which it has promised for its next browser release via a January 21 posting to the IE Team Blog.
More
Found 164 days, 17 hours, 25 minutes, and 35 seconds ago
blog.hansmelis.be
I thought this was a really early April's fool when I first read it, but this is all over the place it just has to be true. I picked it up from Robert O'Callahan's blog . I don't know who keeps inventing these things, but sometimes you just can't come up with such funny jokes no matter how hard you try.
Found 164 days, 14 hours, 28 minutes, and 37 seconds ago
adju.st
I had to get this off my chest.
Over at alistapart there is a post about a new proposal for getting around the complete failure of the IE dev team to produce anything other than dogfood. In summary it pushes the burden of future IE compatibility onto us web developers, rather than onto the IE dev team, who are the people who can actually fix it.
I work at a software development shop. We build a varied lot of software, but pretty much all of it has a web interface somewhere.
When those web interfaces go beyond helloworld we end up paying the IE Tax , just like all the other web developers out there.
Found 164 days, 13 hours, 52 minutes, and 47 seconds ago
it.slashdot.org
Dak RIT writes "In a blog post this week, Microsoft's IE Platform Architect, Chris Wilson, confirmed that IE8 will use three distinct modes to render web pages. The first two modes will render pages the same as IE7, depending on whether or not a DOCTYPE is provided ('Quirks Mode' and 'Standards Mode'). However, in order to take advantage of the improved standards compliance in IE8, Web developers will have to opt-in by adding an additional meta tag to their web pages. This improved standards mode is the same that was recently reported to pass the Acid 2 test, as was discussed here .
Found 164 days, 13 hours, 17 minutes, and 43 seconds ago
feeds.feedburner.com
I feel like I should have titled this, "Painful Web Standards Decision from IE (surprise!)", but that would be snarky, right?
The Internet Explorer team has detailed their implementation of the switch between different rendering standards over on the IEBlog . ...
Found 164 days, 12 hours, 38 minutes, and 3 seconds ago
newmobilecomputing.com
"In Dean's recent Internet Explorer 8 and Acid2: a Milestone post , he highlighted our responsibility to deliver both interoperability (web pages working well across different browsers) and backwards compatibility (web pages working well across different versions of IE). We need to do both, so that IE8 continues to work with the billions of pages on the web today that already work in IE6 and IE7 but also makes the development of the next billion pages (in an interoperable way) much easier. Continuing Dean's theme, I'd like to talk about some steps we are taking in IE8 to achieve these goals .
Found 164 days, 11 hours, 41 minutes, and 35 seconds ago
techzonez.com
Full story: ZDNet
Found 164 days, 11 hours, 4 minutes, and 17 seconds ago
dynamicflash.com
I started to write a long post about why Microsoft's proposal to fix web standards with a proprietary meta tag / header is both utterly futile and offensive to developers that care about web standards. Mike Davies , a fellow Yahoo! and one of the best guys you could hope to meet, has said everything I wanted to say - much more eloquently than I tend to be when ranting, I might add - in his End of line Internet Explorer article.
The biggest barrier to Microsoft adopting web standards is Microsoft's own clients, or rather Microsoft's promise to them of backwards compatibility.
Found 164 days, 10 hours, 23 minutes, and 54 seconds ago
newsgoat.com
Billy shared 0xDECAFBAD » Queue everything and delight everyone from decafbad.com
Found 164 days, 9 hours, 47 minutes, and 45 seconds ago
dvhardware.net
A number of commenters on the site took issue with the way Microsoft is planning to make IE 8 more standards-compliant. Many said they believed Microsoft should turn the super standards mode on by default (not make it an opt-in choice), as standards compatibility is more important than backward compatibility. Several posters said they believed Microsoft should abolish quirks mode with the IE 8 release. Source: ZDNet
Found 164 days, 9 hours, 18 minutes, and 27 seconds ago
cmsreport.com
"In Dean's recent Internet Explorer 8 and Acid2: A Milestone
post, he highlighted our responsibility to deliver both
interoperability (web pages working well across different browsers) and
backwards compatibility (web pages working well across different
versions of IE). We need to do both, so that IE8 continues to work with
the billions of pages on the web today that already work in IE6 and IE7
but also makes the development of the next billion pages (in an
interoperable way) much easier. Continuing Dean's theme, I'd like to
talk about some steps we are taking in IE8 to achieve these goals.
Found 164 days, 8 hours, 7 minutes, and 18 seconds ago
drupal.org
What is one of the best tips to get out of the creative slump? Need to find that extra juice for your Drupal theme?
It may be simple, but I love to use Flickr for my inspiration !
Flickr has millions of photos, and thousands of groups to showcase amazing work.
Vandelay Design has compiled a list of 99 Flickr groups to help get you unstuck, such as:
http://flickr.com/groups/webdesign-inspiration/
Found 164 days, 1 hour, 4 minutes, and 45 seconds ago
weblog.200ok.com.au
It is important to note that only some members of WaSP were involved in the decision, others were emphatically not: Microsoftâs Version Targeting Proposal - The Web Standards Project
Found 163 days, 20 hours, 45 minutes, and 56 seconds ago
tagneto.blogspot.com
A List Apart: Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8
Found 163 days, 19 hours, 44 minutes, and 59 seconds ago
blog.codedread.com
The IEBlog let the world know how you're going to have to opt in for their third (and counting) rendering mode that IE8 will support. You know, the one that should support CSS2 the way other browsers already do without such a mode. Put the following into your section of your page and you'll get IE8's "super standards" mode.
Found 163 days, 19 hours, 9 minutes, and 48 seconds ago
thinkdrastic.net
Of course, while I was writing that, the story developed a bit further.
It turns out that using the new
Found 163 days, 16 hours, 43 minutes, and 46 seconds ago
cubiclemuses.com
A List Apart has published an article in support of a versioning meta-tag to be used in IE8 that would allow web designers to target specific browser versions. Eric Meyers and Jeffrey Zeldman agree. I'm almost at a loss for words. Almost.
Robert O'Callahan points out the obvious future issues with this idea from the browser developer perspective. Didn't take long for WebKit to figure that out too. At least some people have a sense of perspective.
Much of the argument is based on IE7 transition issues holding to the "don't break the web principle.
Found 163 days, 16 hours, 41 minutes, and 13 seconds ago
nextwebgen.com
This is an example from John Resig as he discusses a HTML 5 shiv . You can see how a JavaScript shim can "implement" some of HTML 5 for us.
We have also gone down this route for some of the HTML 5 spec, and you can indeed do a lot with JavaScript. There are a couple of places where you kinda have to be in the browser to do the right thing…. but these are few and far between.
Sjoerd Visscher just blogged about this and told us how he found it out (back in 2002-ish!):
As far as I can remember we found out about this when we converted the first rendering of the XSL output from a lot of createElement calls to one innerHTML change for performance.
Found 162 days, 12 hours, 13 minutes, and 19 seconds ago
nextwebgen.com
Then, Eric Meyer came out to talk about switches versus targets :
The second major difference between browser sniffing and version targeting is that browser sniffing looks forward while version targeting looks back. Looking forward is one big reason browser sniffing is fragile: it's hard to predict the future. To pick one example, Safari's inclusion of "like Gecko" in its user-agent identifier broke a fair number of sniffer scripts-even those that were comparatively well done. The authors of those scripts had simply failed to predict that a non-Gecko browser from Apple would include the word "Gecko" in its user-agent identifier.
Found 164 days, 9 hours, 35 minutes, and 22 seconds ago
broken-links.com
January 22nd, 2008
The Internet Explorer team announced today that we will have to opt in to using the improved standards support in future versions of their browser , by means of a meta declaration in the head of our documents:
This is obviously a big deal, as shown by the fact that A List Apart have dedicated their latest release to it; first in the article Beyond DOCTYPE by Aaron Gustafson, which explains the reasons for the new switch, then From Switches to Targets by Eric Meyer, in which approval is given, albeit with reservations.
Found 164 days, 22 hours, 35 minutes, and 47 seconds ago
ctrambler.wordpress.com
Who would had thought it, Microsoft find itself needing a 'quirk' mode in IE8 .
'Quirk' mode had been common in other browsers such as Opera. They need it because IE is doing an extremely bad job in standard conformance.
It's great that Microsoft finally have to taste its own medicine. The strange thing is, to Microsoft, web standard conformance is the 'quirk', not its bad implementation of standard. This irks some commentators. I take a more practical route: in IE8, quirk is standard conformance, but in IE9 I want to see 'IE7′ as the quirk.
Found 164 days, 17 hours, 25 minutes, and 23 seconds ago
wincert.net
Wilson said Microsoft is planning to offer developers three modes in IE 8: the existing quirks mode, which will be compatible with current IE pages and applications; a "standards" mode, which will be the same as what's offered by IE 7 and "compatible with current content"; and a third, super standards mode that will require the insertion of a element to guarantee the highest level of standards compatibility. Wilson added: "We believe this approach has the best blend of allowing web developers to easily write code to interoperable web standards while not causing compatibility problems with current content.
Found 164 days, 4 hours, 15 minutes, and 4 seconds ago
whitesoap.com
A List Apart: Articles: Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8
Found 164 days, 4 hours, 8 minutes, and 1 second ago
blog.jeanpierre.de
Meta Madness by John Resig
Found 164 days, 2 hours, 28 minutes, and 50 seconds ago
"No matter what great leaps forward the Internet Explorer team make from now on, the majority of..."
agileweb.org
- Andy Budd
Found 164 days, 30 minutes, and 15 seconds ago
pixelbox.net
Roger Johansson
Found 163 days, 22 hours, 45 minutes, and 5 seconds ago
thecrumb.com
Great post on Slashdot today talking about Microsoft's announcement there will three 'modes' in IE8 - one of them requiring an additional meta tag.
The Slashdot comments are entertaining as always but honestly - did we really think MS could do something right? They screwed up the web years ago and now are trying to 'fix' things as only Microsoft can…
Update: more info on this on A List Apart- Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8
And John Resig has a good post on his blog about why this may not be such a big deal .
Found 163 days, 20 hours, 18 minutes, and 18 seconds ago
remysharp.com
If you're a developer or read any development blogs, you'll have seen the plans for IE8 and backward compatibility.
I'm not going to cover any of the detail as to why this breaks our development process , but instead offer up some questions. Only 8 for now
Read the rest of this entry »
Found 163 days, 17 hours, 26 minutes, and 15 seconds ago
visitmix.com
HTML5 reached working draft status yesterday , and A List Apart just published a thoughtful analysis of IE8's departure from DOCTYPE switching . So what better time to publish our interview with Molly Holzschlag and Jonathan Snook ? In this interview, they touch on some of the hot political issues with standards -- a conversation that we'll continue at Web Directions North and MIX08 . Enjoy!
Found 163 days, 15 hours, 27 minutes, and 46 seconds ago
kirabug.com
I'm a bad geek. I read an article about what could be a great solution for browser compatibility issues and my first though is OMG the browser bloat .
I'm sorry -- I don't want my browser to render a webpage the way it was written ten years ago, I want people to go back and cull their code of garbage. If the page is still valuable, then there's value in keeping it up to date. Clean out all those spoiled electrons, update their pages to match the current standards, and maybe just maybe take invalid/non-useful/non-relevant/garbage content down off the web.
Found 163 days, 11 hours, 57 minutes, and 51 seconds ago
