I noticed these ads a week or so back while reading Mary-Jo Foley’s blog… love the reference to the Tron mono-cycle in the first one, Awsome!
I know, I know… it’s been so long since I posted anything that I probably don’t have any readers anyway (if I had any in the first place , and this shouldn’t have a any disastrous effects on the site… but… I’m flipping the over to a new server later today so there may be a temporary glitch in the Matrix.
Please remain calm, do not be alarmed… DON’T PANIC service will NOT return to normal after the switch… I may actually start posting here again!
Stay tuned… or tune in… or whatever you need to do
Update: Having just updated the database I’m now all switched over. With the exception of a minor outage courtesy of a duff plugin everything went very smoothly.
I’ve been meaning to blog this for a while having come across the problem on a project last year. When including conditional comments in a page rendered using XSL templates the comment has to be structured in a way that doesn’t break the stylesheet. While this sounds simple it took a few attempts to get a working solution.
<xsl:comment>[if lte IE 6]<![CDATA[>]]>
<link rel="stylesheet" type="text/css" href="styles.css" />
The comment must be structured inside an
<xsl:comment> block which, when rendered to the browser, becomes a standard html comment and the greater than and less than brackets on the stylesheet link itself must be entered using their respective character entity codes “
>” and “
I’m not going to rant on about how Firefox is a better browser, although in my opinion it is, or cry over flaws in Internet Explorer that give me head aches almost every day. What I would like to explain is why Firefox should have a place at the heart of every web developers process.
Firefox is an invaluable, time-saving tool regardless of weather you’re designing standards compliant visions of pure css beauty or, at the other end of the scale (more on that in another post) , customising templates for enterprise CMS products targeted exclusively at corporate environments running Internet Explorer.
So why is Firefox so invaluable? Well, firstly it renders pretty reliable standards compliant output which is a good starting point but more important is its extensibility. The combination of this open extensibility and some very smart web developers willing to contribute has led to a tool-set that no other browser has been able match, not that many (if any) seem to really be trying.
Firefox add-ins that should be in every web designers toolkit:
And a couple of less developer oriented add-ons I have found useful on a daily basis:
And finally, in the interests of fairness and to show my openness on this subject, if you’re absolutely determined NOT to use Firefox (you poor poor fools! ) then here are some (lesser) solutions for the IE oriented among you:
As the toolbars primary focus is on accessability rather than development it also comes with some pretty nifty features such as a colour contrast analyser, gif flicker checker, the ability to switch to greyscale.This is actually a REALLY powerful tool and a vast improvement over some other attempts at a web developer style toolbar for Internet Explorer.