Custa1200
Havok13andaThird

Should they really be called <asp:cheapinputimpostersthatareabitchtostyle>?

Started looking into making our own control that inherited from asp:button but outputs html buttons but seems we have run aground pretty early al due to, drum roll please.... du.. du.. daaaah!!! IE.

Why is it that IE still cannot get the functionality of an html button (HTML 4.0 even at that) This effectively makes this one HTML element completely useless to developers.

Is the reason there is no "switch" attibute (like they nicely did in .NET 2 for labels?) to make an asp:button render out to a proper HTML button becuase of the inability still of the IE team to deliver functionality that can be used?

HTML 4.01 Specification

W3C Recommendation 24 December 1999

Seems like such a long time ago doesn't it?

phreaks

Great post.
Very direct, concise and to the point.

Perplexed

W3bbo
The Master of Baiters

Custa1200 wrote:
Should they really be called <asp:cheapinputimpostersthatareabitchtostyle>?

Uhm....

<asp:button /> typically renders <input type="submit" /> or <input type="button" /> (I forget which one specifically since I never use it).

Why not just use HtmlButton? Which renders good ol' fashioned <button> which can be styled pretty easily?

And IE is fully comformant with the CSS Level 2 Revision 0 and HTML4.01 specifications in this area.

Ion Todirel
buuu

it always renders <input type="submit" ..., and you have CssClass what else do you need?

and also isnt button obsolute? i remeber some browser can't handle it right, was it firefox?

ZippyV
Fired Up

Custa1200 wrote:
Is the reason there is no "switch" attibute (like they nicely did in .NET 2 for labels?) to make an asp:button render out to a proper HTML button becuase of the inability still of the IE team to deliver functionality that can be used?

HTML 4.01 Specification W3C Recommendation 24 December 1999

<!ELEMENT BUTTON - -
     (%flow;)* -(A|%formctrl;|FORM|FIELDSET)
     -- push button -->
<!ATTLIST BUTTON
  %attrs;                              -- %coreattrs, %i18n, %events --
  name        CDATA          #IMPLIED
  value       CDATA          #IMPLIED  -- sent to server when submitted --
  type        (button|submit|reset) submit -- for use as form button --
  disabled    (disabled)     #IMPLIED  -- unavailable in this context --
  tabindex    NUMBER         #IMPLIED  -- position in tabbing order --
  accesskey   %Character;    #IMPLIED  -- accessibility key character --
  onfocus     %Script;       #IMPLIED  -- the element got the focus --
  onblur      %Script;       #IMPLIED  -- the element lost the focus --
  >








I don't see a switch attribute anywhere.

W3bbo
The Master of Baiters

Ion Todirel wrote:
it always renders <input type="submit" ..., and you have CssClass what else do you need?

and also isnt button obsolute? i remeber some browser can't handle it right, was it firefox?

<button> isn't obsolete; on the contrary, it's advisable to use <button> instead of <input type="submit"> since it's more accessible (the button content is within the element tags, allowing for stuff like <acrony> and <abbr> instead of as an attribute value).

Watch out though, VS2005 doesn't recognise the type="" attribute on the <button> element.

typemismatch

who advised to use <button...> ??? I'd like to know since it doesn't work in a lot of browsers? go ahead try it.

ZippyV
Fired Up

The specification wrote:
Note. Authors should note that the BUTTON element offers richer rendering capabilities than the INPUT element.

Rossj

Woops.

Custa1200
Havok13andaThird

ZippyV wrote:

Custa1200 wrote:Is the reason there is no "switch" attibute (like they nicely did in .NET 2 for labels?) to make an asp:button render out to a proper HTML button becuase of the inability still of the IE team to deliver functionality that can be used?

HTML 4.01 Specification W3C Recommendation 24 December 1999

<!ELEMENT BUTTON - -
     (%flow;)* -(A|%formctrl;|FORM|FIELDSET)
     -- push button -->
<!ATTLIST BUTTON
  %attrs;                              -- %coreattrs, %i18n, %events --
  name        CDATA          #IMPLIED
  value       CDATA          #IMPLIED  -- sent to server when submitted --
  type        (button|submit|reset) submit -- for use as form button --
  disabled    (disabled)     #IMPLIED  -- unavailable in this context --
  tabindex    NUMBER         #IMPLIED  -- position in tabbing order --
  accesskey   %Character;    #IMPLIED  -- accessibility key character --
  onfocus     %Script;       #IMPLIED  -- the element got the focus --
  onblur      %Script;       #IMPLIED  -- the element lost the focus --
  >








I don't see a switch attribute anywhere.

The "switch" attriibute I was talking about on asp:labels is "AssociatedControl" which changes the rendering of an asp:label from a span to a proper html label which gets a for attribute with value of what you set the assciatedcontrol element to. an asp:label pretty much should never be used without this attribute unlss you require the extra piece of markup around the text. It would be nice if there was an attribute that switched between rendering it as an input or a button.

The problem lies with the way that IE ignores the value attribute and instead uses the content of the button element. Give it a try with a regular html button with a runat server, give the button an id and a name and a value of something and put some html between the button tags and try to press the button in IE vs any other browser.

Custa1200
Havok13andaThird

typemismatch wrote:
who advised to use <button...> ??? I'd like to know since it doesn't work in a lot of browsers? go ahead try it.

If by a lot of browsers you mean IE you are corrrect. As far as advising to use it, there are many many reasons to use it over input, the only reason so far not to use it is IE.

Custa1200
Havok13andaThird

Ion Todirel wrote:
it always renders <input type="submit" ..., and you have CssClass what else do you need?

and also isnt button obsolute? i remeber some browser can't handle it right, was it firefox?

No it is IE that cannot handle it correctly.

Custa1200
Havok13andaThird

Custa1200 wrote:
ZippyV wrote:
Custa1200 wrote:Is the reason there is no "switch" attibute (like they nicely did in .NET 2 for labels?) to make an asp:button render out to a proper HTML button becuase of the inability still of the IE team to deliver functionality that can be used?

HTML 4.01 Specification W3C Recommendation 24 December 1999
<!ELEMENT BUTTON - - (%flow;)* -(A|%formctrl;|FORM|FIELDSET) -- push button --> <!ATTLIST BUTTON %attrs; -- %coreattrs, %i18n, %events -- name CDATA #IMPLIED value CDATA #IMPLIED -- sent to server when submitted -- type (button|submit|reset) submit -- for use as form button -- disabled (disabled) #IMPLIED -- unavailable in this context -- tabindex NUMBER #IMPLIED -- position in tabbing order -- accesskey %Character; #IMPLIED -- accessibility key character -- onfocus %Script; #IMPLIED -- the element got the focus -- onblur %Script; #IMPLIED -- the element lost the focus -- >

I don't see a switch attribute anywhere.
The "switch" attriibute I was talking about on asp:labels is "AssociatedControl" which changes the rendering of an asp:label from a span to a proper html label which gets a for attribute with value of what you set the assciatedcontrol element to. an asp:label pretty much should never be used without this attribute unless you require the extra piece of markup around the text. It would be nice if there was an attribute that switched between rendering an asp:button as an input or a button.

The problem lies with the way that IE ignores the value attribute and instead uses the content of the button element. Give it a try with a regular html button with a runat server, give the button an id and a name and a value of something and put some html between the button tags and try to press the button in IE vs any other browser.

Custa1200
Havok13andaThird

ZippyV wrote:

Custa1200 wrot


  name        CDATA          #IMPLIED
  value       CDATA          #IMPLIED  -- sent to server when submitted --


I don't see a switch attribute anywhere.

These are the attributes that IE struggles with. Instead of using the value associated with the name the content(innerHTML) of the button gets associated to the name. If you do a search for "IE button value bug" in your fave search engine, I am sure you can all get a lil deeper into this.

asp:button ...

HTML 4.01 Specification

W3C Recommendation 24 December 1999