Home/ Questions/Q 601871
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T16:45:42+00:00

I started using a diagnostic css stylesheet, e.g. http://snipplr.com/view/6770/css-diagnostics–highlight-deprecated-html-with-css–more/ One of the suggested rules

  • 0

I started using a diagnostic css stylesheet, e.g.
http://snipplr.com/view/6770/css-diagnostics–highlight-deprecated-html-with-css–more/

One of the suggested rules highlights input tags with the type submit, with the recommendation to use <button> as a more semantic solution. What are the advantages or disadvantages of <button> with type submit (such as with browser compatibility) that you have run across?

Just to be clear, I understand the spec of <button>, it has a defined start and end, it can contain various elements, whereas input is a singlet and can’t contain stuff. What I want to know essentially is whether it’s broken or not. I’d like to know how usable button is at the current time. The first answer below does seem to imply that it is broken for uses except outside of forms, unfortunately.

Edit for 2015

The landscape has changed! I have 6 more years experience of dealing with button now, and browsers have somewhat moved on from IE6 and IE7. So I’ll add an answer that details what I found out and what I suggest.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Answering from an ASP.NET perspective.

    I was excited when I found this question and some code for a ModernButton control, which, in the end, is a <button> control.

    So I started adding all sorts of these buttons, decorated with <img /> tags inside of them to make them stand out. And it all worked great… in Firefox, and Chrome.

    Then I tried IE6 and got the “a potentially dangerous Request.Form value was detected”, because IE6 submits the html inside of the button, which, in my case, has html tags in it. I don’t want to disable the validateRequest flag, because I like this added bit of data validation.

    So then I wrote some javascript to disable that button before the submit occurred. Worked great in a test page, with one button, but when I tried it out on a real page, that had other <button> tags, it blew up again. Because IE6 submits ALL of the buttons’ html. So now I have all sorts of code to disable buttons before submit.

    Same problems with IE7. IE8 thankfully has this fixed.

    Yikes. I’d recommend not going down this road IF you are using ASP.NET.

    Update:

    I found a library out there that looks promising to fix this.

    If you use the ie8.js script from this library: http://code.google.com/p/ie7-js/

    It might work out just fine. The IE8.js brings IE5-7 up to speed with IE8 with the button tag. It makes the submitted value the real value and only one button gets submitted.

    • 0