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

Partial Fix +Quote with css rule text-transform:uppercase

Discussion in 'Resolved Bug Reports' started by Case, Mar 1, 2014.

  1. Case

    Case Active Member

    Style Properties > Message Elements > 'Public' Controls Container

    If I add the rule 'text-transform:uppercase;' there the link at the bottom of a post becomes uppercase but the text goes down.

    So it displays like this:


    It seems to load that link last on the page. Sometimes it snaps back onto one line but I've had users say the link just stays formated like the above for them all the time.

    Any reason that can't be uppercase? Or is there another way to achieve that?

    This is in Chrome.
    Divvens likes this.
  2. Jeremy

    Jeremy Well-Known Member

    You can edit the phases and make them Uppercase.
    Case likes this.
  3. Case

    Case Active Member

    Well, yea. Not ideal if I want all the controls and text at the bottom of a post uppercase though.
    Divvens likes this.
  4. Divvens

    Divvens Well-Known Member

    It doesn't work when you want the other buttons uppercase as well! I use the uppercase on all control buttons like like/reply etc and turn them into a button using CSS, I'm sure many also apply rules on all the whole controls container, so this probably needs to be fixed.
  5. Brogan

    Brogan XenForo Moderator Staff Member

    It will be fixed, the workaround in the meantime is to edit the phrase.
    Amaury likes this.
  6. Jeremy

    Jeremy Well-Known Member

    You can edit the other phrases as well. It is still an open bug report, meaning Mike or Kier will look at it soon. I provided a solution, not a fix.
    Amaury likes this.
  7. rellect

    rellect Well-Known Member

    Seems like a redraw is needed as the '+Quote' string is inserted using javascript.

    discussion.js (full), line 523
    Changing into
    Seems to fix it.
  8. Mike

    Mike XenForo Developer Staff Member

    In general, this is a Chrome bug -- it's maintaining a 0 width when this CSS is applied. I don't have a clue why. When customizations trigger browser bugs, it's not always something we can reasonably workaround. For example, I wouldn't consider the double toggle to be a "reasonable" workaround in this case.

    I have, however, made some tweaks that may improve rendering performance which seems to sort the issue.
    Case likes this.

Share This Page