- PDF Hammer – PDF Hammer is a website that allows you to edit your PDF files online for free.
- Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 – When a new version of that browser comes along and fixes bugs or misinterpretations of the spec (or introduces new ones) or in any way changes behavior, sites break and our clients, bosses, and users get very unhappy.
- From Switches to Targets: A Standardista’s Journey -This actually makes browser vendors more susceptible to pressure to fix their bugs, and less fearful of doing so. Thatâ€™s huge, as fundamentally game changing as was DOCTYPE switching, but on an ongoing basis.
- Better Email Links: Featuring CSS Attribute Selectors – We can use this similarity between links to our advantage, so that we can apply CSS styling to only email links.
- Understanding CSS Colour modes – CSS 2 and 3 offer a number of different ways to pick colours. While everyone knows the hexadecimal notation, fewer people know the RGB notation and colour keywords, and the new colour modes that CSS3 introduces are still a riddle to most.
- Draft of HTML 5 Hints at a Brave New Web – HTML 5 presents a major change from HTML 4, and it will still be a long time before youâ€™re likely to see HTML 5 markup in your browser.
- HTML 5 – W3C Working Draft 22 January 2008. This is the draft straight from the W3C. Not the easiest thing to read/understand, but certainly a great resource (obviously).
- HTML 5 differences from HTML 4 – HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. This article describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes.
- HTML5 Shiv – Assuming that it’ll be a while before most browsers attempt to implement most of HTML 5 we need to start thinking of ways to tackle the creation and rendering of HTML 5 components in the meantime.
Perhaps you figured out the pattern for these links (except for the PDF hammer link)? The HTML 5 draft was finally released on the 22nd of January. The web has been a twitter with this and the fact that Microsoft has said that Internet Explorer 8 will include a “super standards” mode. The key is that this standards mode will require a particular META tag to enable this type of rendering. This has also sent the web into a frenzy because people are claiming that this will destroy progressive enhancement. The truth of the matter, as Eric Meyer points out, is that this will not be a detrimental change. The key moving forward will be that your websites will theoretically continue to work exactly how you coded them for the foreseeable future. In theory, even if we’re all using IE10 your website that was designed for IE6 will still render just fine. The other point that Eric makes is that browser vendors will be able to implement new web standards much more quickly now that they’d no longer need to fear breaking millions of websites. Essentially current websites would remain untouched by new changes to IE’s rendering engine. Unless the developer specifically codes the website to use the new render engine, which we can assume means that the developer has tested the page for issues, it would default to the legacy rendering engine that has proven to work. This is really a good thing for web designers, web standards supporters, and browser vendors.