xhtml

问题 First thing: I know that there is interface to W3C validator: http://pear.php.net/package/Services_W3C_HTMLValidator/ But I don't know if I can install it on cheap hosting server. I don't think so. I need validator for my seo tools within my Content Managment System so it must be pretty much portable. I would love to use W3C but only if it would be portable. I can also use Curl for this but it won't be elegant solution. The best one I found so far is: http://phosphorusandlime.blogspot.com

问题 is there any css validator with CSS3 and vendor specific extensions support? I only want to see problem other than CSS 3 and vendor specific extensions related errors. And is there any better xhtml css validator than W3C's? 回答1: You can select "CSS Level 3" in the More options>Profile section of the W3C CSS Validator. Although this won't help with the vendor-specific errors. It looks like there is no intention to support these in the W3C validator. 回答2: The W3C Validator unfortunately goes

问题 Is it possible to validate iFrames in xhtml 1.0 strict? Preferably without any use of javascript to inject the iframe into the page. I know there is no point in validating just for the sake of validation, but lets just say that I like the green validation message on w3c ;) (I am forced by factors beyond my control to use iframes) Or maybe there is something very similar I can use in xHTML to get iframe-like behavior without losing compatibility across different browsers? (object?) Perhaps

问题 So my questions is similar to this: crop text too long inside div What I don't want to do is have a hard end to the text (chopping off whatever text overflows). The desired output would not include an ellipses (...) but would "fade" away. So if I had something like: <div class="text">This is the really long area of text that I want to chop</div> then at wherever I decide, say midway in wa|nt... the n would be half faded, and the t would be almost completely faded. Of course the positioning is

问题 Like it says. 回答1: Using semantic markup means that the (X)HTML code you use in a page contains metadata describing its purpose -- for example, an <h2> that contains an employee's name might be marked class="employee-name" . Originally there were some people that hoped search engines would use this information, but as the web has evolved semantic markup has been mostly used for providing hooks for CSS. With CSS and semantic markup, you can keep the visual design of the page separate from the

问题 HTML markup: <ul id="portfolio"><li class="web"> <span class="info">August 2007 <a href="http://awebsite.com" rel="external">visit</a></span> <a href="/assets/image.jpg" class="fancybox" rel="web"> <img src="/assets/imagelarge.jpg" alt="Rising Star Ranch" /> <span class="title">Some Title</span> Some other text... </a> </li> </ul> jQuery: $("ul#portfolio li").fadeTo("slow", 0.3); In Firefox 3 and 3.5 as well as IE7, this behaves as expected and fades out all elements within the 'li'. In IE8,

问题 In how many ways and places we can place comment in CSS? Can placement of comment can creat any problem in css rendering and validation? How to show comment in Firebug? How to write good comment for big and small changes in CSS How to CSS readable, clear from comment for easier management 回答1: The CSS specification spells this out definitively: Comments begin with the characters /* and end with the characters */ . They may occur anywhere between tokens, and their contents have no influence on

问题 I have to convert from one XML (XHTML) file to another using XSLT. The rules of transformation are: <div id="ta12" class="bl" style="dis:bl"> has to be replaced with <div class="pass" value="50"> The values of id="t0b" and "t1b" have to be replaced with id="ta0b8" and "ta3b8" respectively. <input type="radio" name="o0" id="t0"/> has to be replaced with <input type="radio" name="key0b8" value="0" id="ta0q" class="block" /> (And likewise in the file) Input file: <?xml version="1.0" encoding=

问题 If i have same navigation on 2 places in every page , one is in dropdown and again is in left sider bar will it create difficulties for screen reader user? 回答1: It shouldn't be an issue. Assuming the drop down is a combo box there won't be duplicate text spoken since screen readers only read the selected item in a combo box by default not the entire list of items. I find links are the best way for me to navigate a frequently used page since most screen readers have the ability to generate a

问题 I'm learning XSLT and Javascript and I'm trying to load some XSLT generated XHTML using the loadXML() function and I'm getting the following parsing error while using IE (might also be happening in FF to, not sure)... The server did not understand the request, or the request was invalid. Error processing resource 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd' The line in the XHTML it's stumbling on while parsing must be... <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional/