Skip to content

Difficult to move posts now, on mobile.

Bugs

Related Topics
  • What plugins are being used here on Sudonix?

    Solved General
    4
    4 Votes
    4 Posts
    387 Views

    @Norrad Are you looking for anything in particular? I only ask because Sudonix uses a number of custom functions which I wrote, but all are available on GitHub and fully supported here.

  • Smart Widgets

    Solved Configure
    9
    3 Votes
    9 Posts
    462 Views

    @Panda said in Smart Widgets:

    So why is that, or conversely why would the function to expose username ever be required, as it seems app.user is already an available global object?

    It is, yes, but not if you are using it outside of a widget. The function I wrote is also historical and comes from the 2.x train 🙂

  • NodeBB upgrade now cant post

    Solved Bugs
    5
    2 Votes
    5 Posts
    392 Views

    @Panda yes, for some reason, that is the case. If you need an urgent response, it’s probably better to post here because of the time difference.

  • NodeBB Theme/Skin Switcher

    Solved Customisation
    38
    7 Votes
    38 Posts
    3k Views

    @Teemberland great spot ! You should create a PR for that so they can include it in the official repository.

    Just be aware that any subsequent releases will overwrite your fix without the PR.

  • Adding fileWrite to nodebb code

    Solved Configure
    16
    5 Votes
    16 Posts
    773 Views

    @eveh this might be a question for the NodeBB Devs themselves. In all honesty, I’m not entirely sure without having to research this myself.

  • CSS codes for fa-info icon

    Solved Customisation
    9
    6 Votes
    9 Posts
    636 Views

    I have just figured it out…

    it can be targeted with text-decoration-color:

    I was mistakenly using color

  • FIXED: Annoying cosmetic bug on mobile view

    Moved Bugs
    13
    3 Votes
    13 Posts
    1k Views

    And now, after all this time 😕 I finally discovered that the CSS I previously referenced was for something else - and used the same CSS name, so I’ve had to reinstate this block 🤦

    .tab-content { max-height: 0; padding: 0 2em; color: #898989; background: #eeeeee; transition: all 0.35s; margin-top: -5px; }

    And, add this below to make it more specific.

    .emoji-tabs .tab-content { height: 100%; max-height: 100%; padding: 0; margin: 0; }
  • 0 Votes
    9 Posts
    923 Views

    @downpw I’m inclined to agree with this. There isn’t much else you can do, and provided it works with no odd looking artefacts in other browsers, then ok. The :before and :after are pseudo classes and very well supported across all browsers (except perhaps Internet Exploder, but who uses that these days ?)