w3c

I read somewhere that when creating a HTML email, you should use the table-based layout. You should not care about creating tableless css based layout. Is that true? I have to create a newsletter layout for my company, but I dont feel confortable writing 3 nested tables. If you want your HTML-email to look good in most email clients, you should write your HTML as it still was 1999 :) I'd highly recommend paying a visit to the Email Standards Project website. It lists almost every major email client (both standalone and web-based) on the market and outlines how much HTML support is built into

I have an address that is going to be displayed on a webpage, but it is not the address for the author of the page. How should this be coded to be semantic given the w3c recommendation of: The ADDRESS element may be used by authors to supply contact information for a document or a major part of a document such as a form. This element often appears at the beginning or end of a document. You could use the hCard Microformat to describe your address. The advantage of Microformats is that you can use them in your existing documents to enrich them. Here’s an example derived from the example from the

So I've been playing with Google's +1 button trying to get it on my website, but it's not W3C compliant. Here's the code: <!-- Place this tag in your head or just before your close body tag --> <script type="text/javascript" src="http://apis.google.com/js/plusone.js"> {lang: 'en-GB'} </script> <!-- Place this tag where you want the +1 button to render --> <g:plusone size="medium" href="http://www.example.org"></g:plusone> Does anyone know why this happens and how to make this compliant? Thanks EDIT: To get this to pass through the validation, I wrote an article on my website . Quentin Does

So we all know that the DOM (Document Object Model) is an interface that represents HTML pages in web browsers and that you can interact with it using JavaScript. And now and then I read comments about needing a web browser to use the DOM. But is this true? Aren't there other implementations of the DOM such as in server side JavaScript engines, screen scrapers, unit testing frameworks, other programming languages besides JavaScript, etc? Or has this really never been done? And now and then I read comments about needing a web browser to use the DOM. But is this true? Of course not. Your

I am reading CSS specs, the section on Visual Formatting Model and trying to understand what is the difference between these two terms: containing block and block container box . What confuses me is the variation of words that are used for what seems to be completely different concepts: box vs block containing vs container Is block same as box when talking about visual formatting CSS? If not, what is the difference? Are both of these something that is "visible" on the screen? In general, how should I think when I see block in the specification? Also what should first come to my mind when I

What is the correct syntax for using the defer attribute in your javascript? I have seen it done two ways: 1: <script defer >...</script> 2: <script defer="defer">...</script> From experience [and a reference I cannot find] I am more inclined to used the second option, but I just double checked the official w3c site and it seems that option 1 is correct. Thanks defer is a boolean attribute [HTML 4.01 spec] : Some attributes play the role of boolean variables (e.g., the selected attribute for the OPTION element). Their appearance in the start tag of an element implies that the value of the

If you use deprecated attributes or tags <center> , <font color="red"> , or <td valign="top"> etc. in XHTML 1.0 Strict (no depr. attributes), modern browsers (I will use Chrome as an example) still take notice of and use them. If you use HTML5 <video> on an XHTML 1.0 Strict DOCTYPE Chrome will still recognize it - it's not as if they'd program it to not. I tested the worst deprecated, capitalized, and unquoted attribute code I could write, along with HTML5 audio, with the XHTML 1.0 Strict DOCTYPE in Chrome and it rendered flawlessly. Here's the code I tested, working flawlessly in Chrome (red