Posts tagged “(x)HTML”
-
Be a good localStorage neighbor
While working on the client-side caching mechanism in eCSStender, I realized the dangers of
localStorage.clear()
and worked to come up with a solution. -
Audio Spectrum Analysis in JSON
I thought I would post the source for the the Spectrum Analysis tool I created for anyone wanting a quick way to get some data from their favorite tune and perhaps figure out a way to use it in a optimized fashion.
-
A Twitter Search Visualizer in Processing.js
I jumped over from Raphael back to Processing again today and built a visualizer for Twitter data.
-
Canvas, Audio, Raphael & Twitter
Last week I worked up an audio visualizer in Flash for a friend that yielded some nice results; doing the same thing with
canvas
and JavaScript requires a more roundabout method that is less accurate but more gratifying from a coding perspective. -
HTML Canvas & Processing.js
I have been experimenting with the new HTML5
canvas
element and trying to get up to speed on the syntax. -
Getting TinyMCE to respect empty alt attributes
By default (or at least in the default configuration provided under the LG TinyMCE extension for ExpressionEngine), TinyMCE will remove the
alt
attribute if it is empty. Obviously, for accessibility and validation reasons, this is highly undesirable and needs correcting. -
RIP XHTML 2
This decision by the W3C to not renew the charter for the XHTML2 Working Group has, rather unfortunately, brought out the worst in the Web standards community. Personally, I have mixed feelings about the decision.
-
Server-side FigureHandler thoughts
In reaction to my latest article for A List Apart, on FigureHandler, many folks have boldly claimed that this sort of thing should be done server-side. Here are my thoughts on the matter.
-
Alex Russell is not a heretic
First off, let me preface this by saying I just got back to the East Coast after catching a red-eye from San Francisco on Saturday night, so if I seem a bit incoherent, that’s likely why.
-
A better createElementWithName()
Back in 2005, I wrote a piece about IE’s abysmal generation of
NAME
d elements via the DOM (which, interestingly enough, has proven to be one of the most popular posts on the blog, pointing to the fact that this is an obvious pain point for many DOM scripters out there).