- Original Message -
From: Jason Grant [EMAIL PROTECTED]
Boots.com is one of the most 'formsy' web sites out there.
I suggest you sign up for it and try to see what has been done there...
Regards.
boots.com redirects to bootsus.bri-global.com/ - is this the site you were
referring
My boots.com does not redirect to that URL.Try this insted:
http://www.boots.com/webapp/wcs/stores/servlet/TopCategoriesDisplay?langId=-1storeId=10052
http://www.boots.com/webapp/wcs/stores/servlet/TopCategoriesDisplay?langId=-1storeId=10052
Cheers,
Jason
On Sun, Oct 19, 2008 at 7:47 PM, [EMAIL
I have an obsession with web form styling - I cannot stand ugly web form
:-)
Fieldset, label and input tags are enough for basic and nice styling, no
extra div needed.
fieldset
legendspanContact Information/span/legend
label for= xyz/label
Actually, the label tag wrapped around form input is the old traditional
method.
The for attribute method was introduced later to allow designers greater
flexibility in positioning/styling forms whilst maintaining accessibility.
On Fri, October 17, 2008 12:53 am, [EMAIL PROTECTED] wrote:
Thank
- Original Message -
From: Jason Grant [EMAIL PROTECTED]
To: wsg@webstandardsgroup.org
Sent: Friday, October 17, 2008 4:51:46 AM GMT -05:00 US/Canada Eastern
Subject: Re: [WSG] labels as input wrappers + h6 in place of legend
You should also be aware of the fact that for a
You don't need the nested fieldset for styling, but for semantics and
general better structure/meaning of your form. It so happens that you can
also then style that section nicer if you need to. More bloated than it
needs to be? Yes.
Is it better to use a list instead of divs? Of course it is.
As
On Oct 17, 2008, at 9:50 AM, [EMAIL PROTECTED] wrote:
That's my next bone to pick, and why I really liked the label
wrapper. I really dislike the idea of wrapping the label
input in a div but I will likely have to for the exact point you
have made. I need lots of flexibility but want
Boots.com is one of the most 'formsy' web sites out there. I suggest you
sign up for it and try to see what has been done there.
It's not bad and it will give insight into today's commercial needs from
clients regarding forms.
Hope that helps as a concrete example.
Regards.
On Fri, Oct 17, 2008
Stuart Foulstone wrote:
Actually, the label tag wrapped around form input is the old traditional
method.
The for attribute method was introduced later to allow designers greater
flexibility in positioning/styling forms whilst maintaining accessibility.
Really? As far as I can tell looking at
Jason Grant wrote:
Ok you got both of these quite wrong for following reasons:
In the first instance you shouldn't use b or br / at all.
In the second instance you should not wrap input into label as the
label should quite clearly be used for denoting a label of an input
field and not the
I've always used label arount input fields labeltext: input type=text
//label without the for= attribute.
I've never had problems with it, and I don't think I've ever seen any
recommendation against it.
Johan Douma
[EMAIL PROTECTED]
2008/10/16 David Dorward [EMAIL PROTECTED]
Jason Grant
This is the first time for me to see someone proposing use of labelinput
//label structure.I agree that ol is not strictly necessary and that a
form is not necessarily a list, but one could argue that you are dealing
with a list of form input elements.
Read more why I do this here:
Johan – what you are describing is the correct usage in that scenario.
Thanks,
Tatham Oddie
callto:+61414275989 call:+61414275989, callto:+61280113982
call:+61280113982, skype:tathamoddie?call skype:tathamoddie, msnim:[EMAIL
PROTECTED] msn:[EMAIL PROTECTED],
Johan Douma wrote:
I've always used label arount input fields labeltext: input
type=text //label without the for= attribute.
I've never had problems with it, and I don't think I've ever seen any
recommendation against it.
There's a discussion about some problems with that pattern at:
2008/10/16 David Dorward [EMAIL PROTECTED]
Jason Grant wrote:
Ok you got both of these quite wrong for following reasons:
In the first instance you shouldn't use b or br / at all.
In the second instance you should not wrap input into label as the
label should quite clearly be used for
Ok you got both of these quite wrong for following reasons:
In the first instance you shouldn't use b or br / at all.
In the second instance you should not wrap input into label as the
label should quite clearly be used for denoting a label of an input field
and not the input field itself.
Using a
Hi Ben,
I've always used label arount input fields [...]
I don't think I've ever seen any recommendation against it.
Here's one for you:
http://green-beast.com/blog/?p=254
I haven't been paying attention to this, and someone's probably already said
it (if so, sorry), but it's also worth
Johan Douma wrote:
I've always used label arount input fields labeltext: input
type=text //label without the for= attribute.
I've never had problems with it, and I don't think I've ever seen any
recommendation against it.
Support is weaker then for the for attribute, so I would avoid it.
It
I understand where you’re coming from because for some designs the legend isn’t
easy to style consistently cross-browser, and so sometimes I have used a
heading instead. However if possible, using the legend is much better.
I also used to wrap form inputs in labels for the same reason as
Thank you everyone for your replies. So it seems the trusty old traditional
filedset
llegendContact Information/legend
label for=nameName/labelbr /
input id=name type=text
/fieldset
is the way to go to keep all browsers and screen readers happy. I think I can
likely lose the br / and
20 matches
Mail list logo
