Skip to content

Threaded post support for NodeBB

Let's Build It

  • 5 Votes
    3 Posts
    245 Views

    Very good like always 😉

  • Page control arrows for PWA

    Solved Customisation
    27
    25 Votes
    27 Posts
    455 Views

    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems.

    /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android }

    Once you’re in that rabbit hole, it’s impossible to get out of it.

  • 3 Votes
    16 Posts
    493 Views

    @phenomlab
    Ah, got it working!
    I reversed the CSS addition to put z index high, and then I could see another error box saying fork title must be at least 3 characters.
    So made the new fork title longer and button responded.

  • NodeBB: Consent page

    Solved Configure
    16
    4 Votes
    16 Posts
    560 Views

    @DownPW I still do not see any issues.

  • 11 Votes
    14 Posts
    613 Views

    @dave1904 excellent news. Thanks for the feedback

  • 36 Votes
    55 Posts
    4k Views

    @DownPW I see why. The code relies on the existence of

    [component="topic/quickreply/container"]

    However, this by definition means that the below has to be enabled

    aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png

    It will then work

    7fb38631-e0f3-46ef-b652-00929d927b13-image.png

    For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component.

    The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on 🙂

  • 1 Votes
    5 Posts
    565 Views

    @DownPW very useful tip. Thanks

  • CSS codes for fa-info icon

    Solved Customisation
    9
    6 Votes
    9 Posts
    499 Views

    I have just figured it out…

    it can be targeted with text-decoration-color:

    I was mistakenly using color