3 Comments
- PlancksCnst, on 02/18/2008, -0/+1I sincerely hope that browsers (by default) only come with one (or possibly two) rendering engine versions and allow us to decide if or if not we want to install more. Also, if more than one rendering version is installed, we should have the choice to only view pages with the most recent (or n most recent) version(s). If the browser vendors don't do this, it will lead to serious bloat.
It would also be nice (I have no idea if it's possible) to have a standard rendering engine api, which will allow allow applications to use various rendering engines (gecko, trident, presto, khtml, webkit, etc.) to display content. - PlancksCnst, on 02/18/2008, -0/+1Page rendering bugs are not typically a fix for minor versions; with this new element, indeed, page rendering changes should never be included in minor versions.
- scjessey, on 01/22/2008, -0/+1"A List Apart" has basically teamed up with certain members of the Web Standards Project to become Microsoft's bitches. Realizing that IE8 would probably screw up IE7-designed sites, Microsoft have conceived a new way to make life difficult for developers. This time, a new META element (that serves a similar function to Microsoft's "Conditional Comments") is designed to trigger a legacy rendering system. Quite how browser vendors are supposed to build browsers that support multiple versions (conceivably hundreds when minor updates are considered) and then squeeze their software into things like cellular phones is beyond me.



What is Digg?