Jon Phipps's Library tagged html →  View Popular

The relationships among HTML, XML and XHTML are an area of considerable confusion on the web. We often see questions on the webkit-dev mailing list where people wonder why their seemingly XHTML documents result in HTML output. Or we’re asked why an XML construct like <b /> doesn’t actually close the bold tag.

This article will attempt to clear up some of that confusion.

HTML_TreeMenu is a wonderful PEAR package by Richard Heyes
for generating dynamic tree menus using PHP. HTML_TreeMenuXL
is my enhanced version of HTML_TreeMenu. My enhancements have been intended
to extend its flexibility and fix a few problems, and I've been placed that
Richard has incorporated many of my ideas back into the base package.

This page demonstrates HTML_TreeMenuXL, documents its usage,
and offers access to the source code.

While there are numerous mechanisms and enabling frameworks for retrieving
data asynchronously into an HTML document, the basic task of injecting
a significant amount of data into a document remains a typically laborious process.

To circumvent this laborious process, many developers instead opt to
asynchronously retrieve "markup fragments", which are made of data that has already been
fully-injected into the necessary HTML that can simply be inserted "as-is" into the main document.

While this approach works well enough, there are many use cases where it still
makes more sense to only retrieve pure data from the server.

IBDOM was designed to alleviate this tedium, while fully-embracing standard-compliant
documents, by providing an unobtrusive mechanism to "map data values" to JavaScript Objects.

The XAK TagSoup Clean-Up Service provides a simple online service to allow on the fly correction
of malformed and dodgy HTML documents found in the wild. This allows them to be processed further,
e.g. to extract metadata or apply XSLT transformations.

The service is based on John Cowan's TagSoup Parser.

This article describes what I think is a clever way of
automatically truncating the text of a paragraph:




• Truncate the text to a length of your choosing
• Do not truncate in the middle of a word (only on a word boundary)
• Keep the page search-engine friendly by publishing the complete non-truncated text
• Add an ellipsis to the end of the truncated text
• Make the ellipsis a link that expands the text to full length. Once expanded it cannot be collapsed again (but that functionality could be added just as easily)
• Assumes that the content is plain text with no markup.

Many Web designers use browser-detection techniques to ensure that their sites display properly on specific browser versions. It is important to ensure that the techniques chosen take into account future browser releases.

This topic shows three ways to detect current and future versions of Internet Explorer. Designers currently detecting browsers in their sites should verify that browser detection is necessary and, if so, ensure that the code accepts later versions of supported browsers.

Internet Explorer 7 contains a number of improvements to cascading style sheet (CSS) parsing and rendering over IE6. These improvements are aimed at improving the consistency of how Internet Explorer interprets cascading style sheets as recommended by the W3C in order that developers have a reliable set of functionality on which to rely.

In some cases a few of these changes may have the effect of making existing content render in ways that are not compatible with IE6. This is often seen with elements moving to a different area of the page or overlapping content when viewed in IE7. These issues are most common on content that is using particular CSS constructs (often know as "hacks" or filters) to work around bugs that existed under the strict mode in IE6. In this article we'll discuss why pages might be broken due to updated CSS support and the best ways to address the issues that result from it.