E-mail List Archives
Re: Do Web developers tend to dislike the button element?
From: Mallory
Date: Aug 14, 2020 6:20AM
- Next message: Laura Fathauer: "Re: What three aspects of accessibility in an educational setting do you consider to be most helpful?"
- Previous message: Mallory: "Re: What three aspects of accessibility in an educational setting do you consider to be most helpful?"
- Next message in Thread: Patrick H. Lauke: "Re: Do Web developers tend to dislike the button element?"
- Previous message in Thread: Swift, Daniel P.: "Re: Do Web developers tend to dislike the button element?"
- View all messages in this Thread
One issue I remember with IE and buttons was a thick black outline which was difficult to remove. It only appeared in a certain state or situation, but it had plenty of its own threads in forums.
Another issue which hit IE7 and 8 (but I don't think 9+) was most buttons are inline-block but in IE they'd be full width like a block. The solution was to add two lines of CSS (overflow: visible plus width: auto), but if you didn't know it would work with those 2 lines, it was a lot of frustration, lol.
cheers,
_mallory
On Thu, Aug 13, 2020, at 3:00 PM, Swift, Daniel P. wrote:
> I also remember running into functional problems with older versions of
> IE and the button element. I can't remember what the specific problems
> were (going back 5 or so years), but it was enough of a show stopper
> that we could not use them.
>
> Dan Swift
> Senior Web Specialist
> University Communications and Marketing
> West Chester University
> 610.738.0589
>
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Patrick H. Lauke
> Sent: Wednesday, August 12, 2020 4:36 PM
> To: <EMAIL REMOVED>
> Subject: Re: [WebAIM] Do Web developers tend to dislike the button
> element?
>
> Historically, <button> elements used to be very stubborn against
> restyling cross-browser. One of the last annoying issues nowadays is in
> IE11 (where still supported by a site), where by default <button> has a
> visible "dipping" behaviour of one or two pixels when active, and it
> needs a lot of fiddling (last time I looked, including an additional
> wrapper element) to get rid of that.
>
> There also used to be some funky behaviour when it came to events,
> bubbling, etc in some browsers. That has luckily gone by the wayside now...
>
> Because of this history, a lot of articles, how-tos, libraries, etc used
> other elements like <a href="#"> or <span>s and <div>s...and this
> tradition stuck.
>
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/<https://www.splintered.co.uk> |
> https://github.com/patrickhlauke<https://github.com/patrickhlauke>
> https://flickr.com/photos/redux/<https://flickr.com/photos/redux> |
> https://www.deviantart.com/redux<https://www.deviantart.com/redux>
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > http://list.webaim.org/<http://list.webaim.org>
> List archives at
> http://webaim.org/discussion/archives<http://webaim.org/discussion/archives>
> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
> > > > >
- Next message: Laura Fathauer: "Re: What three aspects of accessibility in an educational setting do you consider to be most helpful?"
- Previous message: Mallory: "Re: What three aspects of accessibility in an educational setting do you consider to be most helpful?"
- Next message in Thread: Patrick H. Lauke: "Re: Do Web developers tend to dislike the button element?"
- Previous message in Thread: Swift, Daniel P.: "Re: Do Web developers tend to dislike the button element?"
- View all messages in this Thread