1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Browser Issue 'Delete Thread' Button

Discussion in 'Resolved Bug Reports' started by holder10, Feb 19, 2011.

  1. holder10

    holder10 Active Member

    Hi,

    I just tried styling buttons and it seems to me as if the 'Delete Thread' (when being on a thread page, clicking on 'Thread Tools' and then on 'Edit Thread') isn't styled as all the other ones are. You can even see this without a custom button styling: The active effect is slightly different.

    Maybe it's on purpose or just on my copy of the default theme though. Can anybody check that please?

    Thanks,
    Lennart
     
  2. Brogan

    Brogan XenForo Moderator Staff Member

    Looks fine here.

    button.PNG
     
  3. holder10

    holder10 Active Member

    Yeah, it looks fine like that. However, when clicking on them, I get these different effects as active states - I didn't see the one from 'Delete Thread' anywhere else:

    Bildschirmfoto 2011-02-19 um 22.12.42.png Bildschirmfoto 2011-02-19 um 22.13.17.png

    Plus, when applying custom styles, it neither applies my active nor my text color style.
     
  4. Mike

    Mike XenForo Developer Staff Member

    This is a browser issue - the "delete thread" button is actually an <a>, while the cancel button is indeed a button. It looks FF (at least) only gives the active effect on a link in certain circumstances. For example, click and hold the delete link (you'll see hover) but now drag away and you'll see active. With the actual button, you'll see active as soon as it's clicked.
     
  5. Kier

    Kier XenForo Developer Staff Member

    It would appear that this is simply the result of the Delete Thread... button being an <a /> and the other two buttons being <input /> tags. The <a /> tag does not switch to its :active state on click, as the <input /> tags do, but if you force the <a /> tag into its :active state, it reflects the same styling as the <input /> tags. Therefore, all we can do is blame browser implementation.

    Screen shot 2011-02-21 at 15.39.26.png
     
  6. holder10

    holder10 Active Member

    I see, that sucks though. Thanks for letting me know!
     
    Kier likes this.

Share This Page