Update: Final edit. Switched to STRICT DTD, removed italic to match the image in the question, and reverted back to full colour names for ids to show intent as per OPs comment on question, and sorted the main column of id names in the css into the order they appear in the html. I also … Read more
It’s better to have the default be non-javascript, and then let a javascript code overwrite with a javascript enabled page. Doesn’t have to be much. Can just be a display:none; block, which is then set to display:block; by javascript, and vice versa for the non-js page.
Here is a more efficient way of fading out an element: function fade(element) { var op = 1; // initial opacity var timer = setInterval(function () { if (op <= 0.1){ clearInterval(timer); element.style.display = ‘none’; } element.style.opacity = op; element.style.filter=”alpha(opacity=” + op * 100 + “)”; op -= op * 0.1; }, 50); } you … Read more
The solution is to specify box model for form elements, and browsers tend to agree most when you use border-box: input, select, textarea { -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; } There’s normalize.css project that aggregates such tricks.
Use absolute positioning: #div1{ width: 100%; height: 50px; background-color:red;/*Development Only*/ } #div2{ width: 100%; position: absolute; top: 50px; bottom: 0; background-color:blue;/*Development Only*/ } <div id=”div1″></div> <div id=”div2″></div>
If you want the “old” rendering, and no button to show up on the toolbar so that users can switch modes you can use this: <head> <!– Mimic Internet Explorer 7 –> <meta http-equiv=”X-UA-Compatible” content=”IE=EmulateIE7″ > <title>My Web Page</title> </head> other options (old and new) include:IE=5, IE=7, IE=8, or IE=edge (edge equals highest mode available)
To remove the trailing comma, use the :last-child pseudo-class, like so: #taglist li:last-child:after { content: “”; }
Yes you can use a div inside a li and it will validate. <!ELEMENT li %Flow;> <!ENTITY % Flow “(#PCDATA | %block; | form | %inline; | %misc;)*”> <!ENTITY % block “p | %heading; | div | %lists; | %blocktext; | fieldset | table”>
The ramification is that w3c comes along in 2, 5, 10 years and creates an attribute with the same name. Now your page is broken. HTML5 is going to provide a data attribute type for legal custom attributes (like data-myattr=”foo”) so maybe you could start using that now and be reasonably safe from future name … Read more
You should read Beware of XHTML, which is an informative article that warns about some of the pitfalls of XHTML over HTML. I was pretty gung-ho about XHTML until I read it, but it does make several valid points. Including the following bit; XHTML 1.x is not “future-compatible”. XHTML 2, currently in the drafting stages, … Read more