span
, div
, or table
elements. Over time, the hope is to make it so that all new comments are valid.Continuing my minimalist markup quest, I’ve converted posts to be mostly valid HTML5. The overall structure is correct, but individual comments may only be well-formed but may contain deviations from validity. Most posts will have no span
, div
, or table
elements. Over time, the hope is to make it so that all new comments are valid.
The HTML5 Validator is currently down, so I proceeded to install a local copy. Other than having to make the following change, all went smoothly.
=================================================================== --- build.py (revision 58) +++ build.py (working copy) @@ -77,7 +77,7 @@ ("http://www.slf4j.org/dist/slf4j-1.4.3.zip", "5671faa7d5aecbd06d62cf91f990f80a"), ("http://www.nic.funet.fi/pub/mirrors/apache.org/commons/fileupload/binaries/commons-fileupload-1.2-bin.zip", "6fbe6112ebb87a9087da8ca1f8d8fd6a"), # ("http://mirror.eunet.fi/apache/xml/xalan-j/xalan-j_2_7_1-bin.zip", "99d049717c9d37a930450e630d8a6531"), - ("http://mirror.eunet.fi/apache/ant/binaries/apache-ant-1.7.0-bin.zip" , "ac30ce5b07b0018d65203fbc680968f5"), + ("http://archive.apache.org/dist/ant/binaries/apache-ant-1.7.0-bin.zip" , "ac30ce5b07b0018d65203fbc680968f5"), ("http://surfnet.dl.sourceforge.net/sourceforge/iso-relax/isorelax.20041111.zip" , "10381903828d30e36252910679fcbab6"), ("http://ovh.dl.sourceforge.net/sourceforge/junit/junit-4.4.jar", "f852bbb2bbe0471cef8e5b833cb36078"), ("http://dist.codehaus.org/stax/jars/stax-api-1.0.1.jar", "7d436a53c64490bee564c576babb36b4"),
I’m also experimenting with hoisting the author’s name to a floating aside in the top right of each comment.
Sections are used to group comments by days. These groupings will adjust based on your local time zone.
The pages themselves display reasonably consistently between the three browsers that I have been testing with (Firefox 3.0, Safari 3.1.2, Opera 9.5), and mostly differ in the amount of support they have for CSS-based rounded corners (full, partial, none; respectively).
A bit offtopic, but... there are relative links in your feed’s “link” elements. Is that how it is supposed to be? It seems Akregator (KDE3) don’t like it... -_-
“/blog/2008/07/10/More-Minimalistic-Markup”
becomes
“file:///blog/2008/07/10/More-Minimalistic-Markup”
It looks like Firefox 3 doesn’t support border styles other than solid for the rounded corners, which makes things look a bit strange. For some reason, the rendering performance of your rails.intertwingly site is much worse than the “old” site in my Firefox 3. Scrolling is very jerky. The same doesn’t seem to be true for Opera 9.5, so I’m not sure what the deal is there.
LiveJournal doesn’t like the relative URLs in Sam’s Atom feed either. I’ve always just assumed Sam was doing it deliberately to catch out sloppy Atom implementations.
It looks like Firefox 3 doesn’t support border styles other than solid for the rounded corners, which makes things look a bit strange. For some reason, the rendering performance of your rails.intertwingly site is much worse than the “old” site in my Firefox 3. Scrolling is very jerky. The same doesn’t seem to be true for Opera 9.5, so I’m not sure what the deal is there.
LiveJournal doesn’t like the relative URLs in Sam’s Atom feed either. I’ve always just assumed Sam was doing it deliberately to catch out sloppy Atom implementations.
Clearly Akregator has a bug. The spec is clear on this matter.
Scrolling is smooth for me on all three browsers I’ve tested with. And all three browsers mentioned support border style of “outset” (note the difference in color between the top left and bottom right corners).
Sam and Tim are trouble makers, because I’ve noticed that problem with Akregator for a long time. And yes, it is a bug on their part :)
I’ve since moved to Liferea (1.4.4 on Ubuntu Gutsy), which handles Tim’s feed just fine but segfaults on Sam’s (presumably due to the inline SVG). One of these days I’ll update to a more recent version which I’ve heard handles things better.
The HTML5 Validator is currently down, so I proceeded to install a local copy.
I’m sorry about the inconvenience the downtime has caused.
Other than having to make the following change, all went smoothly.
Fixed. Thanks.
What’s the right way to link to apache.org software packages in such a way that the link stays stable when a new version? Should I always use archive.apache.org URLs?
I’m sorry about the inconvenience the downtime has caused.
It merely caused me to get around to doing something I had meant to do anyway. :-)
What’s the right way to link to apache.org software packages in such a way that the link stays stable when a new version?
Any static URI will defeat our mirroring system. For the volumes that this package is likely to get, I wouldn’t worry too much about it.