Which IS semantic and separates content (the link) from presentation (a
button).
On Mon, February 23, 2009 10:56 pm, Chris F.A. Johnson wrote:
On Tue, 24 Feb 2009, John Horner wrote:
Thanks for all the discussion so far. It seems I'll have to re-code.
I will definitely not be using
Which IS semantic and separates content (the link) from presentation (a
button).
On Mon, February 23, 2009 10:56 pm, Chris F.A. Johnson wrote:
On Tue, 24 Feb 2009, John Horner wrote:
Thanks for all the discussion so far. It seems I'll have to re-code.
I will definitely not be using
...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Chris F.A. Johnson
Sent: Tuesday, 24 February 2009 9:56 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] IE and the button element
On Tue, 24 Feb 2009, John Horner wrote:
Thanks for all the discussion so far. It seems
Chris F.A. Johnson
On Tue, 24 Feb 2009, John Horner wrote:
1) Button elements don't need styling, they take their styling from
the user's operating system, which they are, I assume, familiar and
comfortable with. I won't be reinventing the wheel.
Button elements are styled by the
On Tue, February 24, 2009 1:54 am, John Horner wrote:
Advantages of using buttons:
1) Button elements don't need styling, they take their styling from the
user's operating system, which they are, I assume, familiar and
comfortable with. I won't be reinventing the wheel.
Actually, the
Nick Fitzsimons wrote:
Actually, the specific purpose of the button is to allow one to have
buttons that *don't* look like ordinary buttons:
Buttons created with the BUTTON element function just like buttons
created with the INPUT element, but they offer richer rendering
possibilities: the
On Tue, February 24, 2009 10:57 am, David Dorward wrote:
Nick Fitzsimons wrote:
Actually, the specific purpose of the button is to allow one to have
buttons that *don't* look like ordinary buttons:
Buttons created with the BUTTON element function just like buttons
created with the INPUT
On Feb 24, 2009, at 7:28 AM, Nick Fitzsimons wrote:
the point is that it *behaves*
like a button. In other words its purpose is to provide a specific
kind of
functionality
and if I remember correctly, the functionality to be provided as
originally stated was a link to a next page. I'd
John Horner wrote:
I adopted the use of the button element in an application I'm working
on, used like this:
a href=foo.htmlbuttonfoo/button/a
one main reason I liked buttons is that they can be disabled with an
attribute, which was useful for things like keeping a next button
everywhere,
Rob wrote:
Buttons were mainly designed as triggers for javascript behaviour,
I disagree, if you look at the original HTML 4 material, you will see
that the button element promoted as an improved input element.
Why not
form action=foo.html type=postbutton type=submitfoo/button/form
--
Nick
IMHO, not very semantic in nature. We need the button element to be able to
carry a valid link-type attribute. Enclosing it in a form just don't cut it.
It must be able to stand by itself as an alternative means to activate a
hyperlink, as another aspect of its functionality.
Med vennlig hilsen /
Frank Palinkas wrote: http://dev.opera.com/articles/accessibility/
On Mon, Feb 23, 2009 at 1:43 PM, Nick Cowie cowie.n...@gmail.com
mailto:cowie.n...@gmail.com wrote:
Rob wrote:
Buttons were mainly designed as triggers for javascript behaviour,
I disagree, if you look at the
[mailto:li...@webstandardsgroup.org] *On
Behalf Of *Frank Palinkas
*Sent:* 23 February 2009 12:56
*To:* wsg@webstandardsgroup.org
*Subject:* Re: [WSG] IE and the button element
IMHO, not very semantic in nature. We need the button element to be able to
carry a valid link-type attribute. Enclosing
On Mon, Feb 23, 2009 at 2:10 PM, michael.brocking...@bt.com wrote:
Surely the button element is REQUIRED to be enclosed in a form ??
Is it though? Just looking at HTML 4.01, I don't think it's
forbidden/invalid to have form elements outside of form
: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Patrick H. Lauke
Sent: 23 February 2009 14:52
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] IE and the button element
On Mon, Feb 23, 2009 at 2:10 PM, michael.brocking...@bt.com wrote:
Surely the button element
2009/2/23 Frank Palinkas fmpalin...@gmail.com:
IMHO, not very semantic in nature. We need the button element to be able to
carry a valid link-type attribute. Enclosing it in a form just don't cut it.
We are talking HTML 4 here, so to have a link you have to use an
anchor tag, a form or
Patrick H. Lauke wrote:
On Mon, Feb 23, 2009 at 2:10 PM, michael.brocking...@bt.com wrote:
Surely the button element is REQUIRED to be enclosed in a form ??
Is it though? Just looking at HTML 4.01, I don't think it's
forbidden/invalid to have form elements outside of form
Nick Cowie wrote:
2009/2/23 Frank Palinkas fmpalin...@gmail.com:
IMHO, not very semantic in nature. We need the button element to be able to
carry a valid link-type attribute. Enclosing it in a form just don't cut it.
We are talking HTML 4 here, so to have a link you have to use an
Nick Cowie wrote:
Frank is correct, a link is semantically correct way to go and to get
the behaviour John wants, he is better off using javascript than a
button. Though I don't know of a way of disabling a link with
javascript
? capture the click event and stop it.
In the bad old obtrusive
On Mon, Feb 23, 2009 at 3:39 PM, Robert O'Rourke r...@sanchothefat.com wrote:
I don't really know how toread the DTDs properly
Yeah, it's obscure for sure.
!ELEMENT BUTTON
http://www.w3.org/TR/html401/interact/forms.html#edef-BUTTON - -
(%flow;
There was a wee bug (or two!) in that link I posted, very sorry.
http://www.sanchothefat.com/dev/sfhelp/validations.php
If you validate that page now it works with the buttons outside of a
form. They do however need to be contained by a block element such as a div.
Patrick H. Lauke wrote:
On Mon, Feb 23, 2009 at 3:39 PM, Robert O'Rourke r...@sanchothefat.com wrote:
I don't really know how toread the DTDs properly
Yeah, it's obscure for sure.
!ELEMENT BUTTON
http://www.w3.org/TR/html401/interact/forms.html#edef-BUTTON - -
(%flow;
Thanks for all the discussion so far. It seems I'll have to re-code. I will
definitely not be using Javascript. It seems entirely logical to me that there
should be such a thing as a button, which can exist outside a form, which has
an HREF attribute or can be wrapped in an anchor. But if there
On Tue, 24 Feb 2009, John Horner wrote:
Thanks for all the discussion so far. It seems I'll have to re-code.
I will definitely not be using Javascript. It seems entirely logical
to me that there should be such a thing as a button, which can exist
outside a form, which has an HREF attribute or
John, I like your approach - I think I might start using it. IMO -
button means button whether it is in a form or not. And
button has more meaning than input type="button|submit".
Don't give into design by committee, just look at how it ruined Tim
Berner-Lee's original vision for the web. He
Agree. It is very easy to style the anchor element.
Chris F.A. Johnson wrote:
On Tue, 24 Feb 2009, John Horner wrote:
Thanks for all the discussion so far. It seems I'll have to re-code.
I will definitely not be using Javascript. It seems entirely logical
to me that there should be such a
the styling comes directly from the OS and the user is
familiar with it.
-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Chris F.A. Johnson
Sent: Tuesday, 24 February 2009 9:56 AM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] IE
27 matches
Mail list logo
