Not really: adding padding-right enlarge the legend (and make it depend on the screen resolution). What I really want was to have a full styleable block element, but maybe I'm asking too much to the rendering engines.
Time to say goodbye to the <legend> element.
I'll use an <h1> header just...
Before posting, I've spent some hour in googling, and the only solution (= bad workaround) I found is:
<form>
<fieldset>
<legend><span>Titolo</span></legend>
<p><label>Un testo: <input type="text" /></label></p>
<p><input type="submit" value="CONFERMA" /></p>
</fieldset>...
I've the following code fragment:
<form>
<fieldset>
<legend>Titolo</legend>
<p><label>Un testo: <input type="text" /></label></p>
<p><input type="submit" value="CONFERMA" /></p>
</fieldset>
</form>
Now I want be able to manage <legend> as a common <div>:
legend { display...
It sounds good: this way I can encapsulate all the js specific customizations in support.js. The problem is that, apart js is a scripting language in the client side, I don't know ANYTHING about ecma scripting.
Because <noscript> cannot be inside <head>, I was thinking also <script> cannot be used.
Checking the w3c documentation carefully, I discovered I was wrong: what a stupid question...
Thank you for your help!
Hi all,
I implemented a hierarchy browser using javascript when available. Whithout javascript, I wanted a full-expanded menu.
I solved with the following code:
<link rel="stylesheet" type="text/css" ref="style.css"></link>
<noscript>
<link rel="stylesheet" type="text/css"...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.