Most people have gotten the answer basically right — that the rules are different when you serve a page a billion times a day. Bytes begin to matter, and the current level of compression clearly shows that Google is concerned with saving bandwidth. A few points: One, people are implying that Google’s reasons for saving … Read more
The whole point of an anchor link is to scroll a page to a particular point. So if you don’t want that to happen, you need to attach an onclick handler and return false. Even just adding it as an attribute should work: <a href=”#button1″ id=”button1″ onclick=”return false”>button 1</a> A side of effect of the … Read more
You will not be able to store objects/arrays in the value attribute, however an option would be to use data-* attributes which supports json automatically with jQuery 1.4.3+ <select> <option data-value=”{“name”:”rajiv”,”age”:”40″}”>a</option> <option data-value=”{“name”:”mithun”,”age”:”22″}”>f</option> </select> And using .change() $(“select”).change(function(){ alert($(this).find(“:selected”).data(“value”).age); }); Example on jsfiddle
Try the following: word-wrap: break-word; white-space: normal; word-wrap is css3 (however it works in IE). You might not be able to get it working in older browsers however.
Have you considered nested UL’s? I believe this would validate: <UL> <LI> <UL> <LI></LI> <LI></LI> <LI></LI> </UL> </LI> <LI> <UL> <LI></LI> <LI></LI> <LI></LI> <LI></LI> <LI></LI> </UL> </LI> </UL> Your CSS trick was my first guess; too bad you can’t use that.
From WIKI: PCDATA Simply speaking, PCDATA stands for Parsed Character Data. That means the characters are to be parsed by the XML, XHTML, or HTML parser. (< will be changed to <, <p> will be taken to mean a paragraph tag, etc). Compare that with CDATA, where the characters are not to be parsed by … Read more
According to the XHTML Strict DTD, no, you’re allowed script, style, meta, link, object, title and base only. Transitional allows isindex as well, but still not noscript.
Look at the error messages that you get when you try that with http://validator.w3.org Apart from a warning that you haven’t specified a character encoding (and that it’s therefore assuming UTF-8), the main error is that a <p> isn’t allowed to contain non-inline content. You can either remove the <p> and </p> completely, or, move … Read more
Leave out the <p> tag unless the content of your table cell is truly a paragraph. It’s certainly possible to have paragraphs in tabular data, and in that case a semantic <p> would be appropriately placed. But for the common table with data in the cells eg. numbers, names, etc., don’t include the <p>.
I prefer to use as few <div>s as possible. <div class=”container”> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> <p>Hello, this is text.</p> … Read more