The HTML markup of Metafilter proper ("the blue") differs from the markup of Metatalk and Ask Metafilter. Given the upcoming changes to Metafilter's look, can we expect similarity in markup across the site, or should we explicitly not rely on undocumented features of Metafilter? [mi]
posted by orthogonality to Feature Requests at 12:46 PM (8 comments total)
Metafilter, on the other hand, puts all comments in a single <div>; to find the beginning of a particular comment, it's necessary to walk backward looking for an anchor tag, and to find the end, walk forward to find the span element containing the author's name.
This also makes it difficult for Mozilla browsers to identify individual comments, as can be seen by the different behavior of extensions like NukeAnything on Metafilter as compared to Metatalk.
Even the markup in MetaTalk and Ask could be slightly cleaner: currently the individual comment div has as its children the comment text (which can be arbitrarily many HTML elements) followed by the span element, which contains the author data. The span element is always the div's last child, but processing would be even easier if the comment text were enclosed in another div, thus making the comment div always have exactly two children.
Of course, the primary concern is that Metafilter work and that Mathowie not be unnecessarily burdened, or constrained to keep to a form a markup the site's outgrown because third parties have come to rely on it.
But a consistent markup -- if it doesn't otherwise detract from the site -- makes making third party tools easier.
posted by orthogonality at 1:02 PM on February 16, 2005