Skip to content

NodeBB v3 Chat Very Slow

Moved Performance
47 3 20.9k 1
  • wrote on last edited by
    #33

    They deactivate background and box shadow on nodebb communauty :

    image.png

  • They deactivate background and box shadow on nodebb communauty :

    image.png

    wrote on last edited by
    #34

    @DownPW None of those will impact the box size. Let me have a look.

  • wrote on last edited by
    #35

    yep not box size but we don’t see the bug

  • yep not box size but we don’t see the bug

    wrote on last edited by
    #36

    @DownPW what exactly is the bug? I’ve tested it, and it behaves normally from what I see (unless I completely missed something)?

  • wrote on last edited by
    #37

    Size is good, is just the focus when we type text it has changed

    on 3.1.7 :

    image.png

    On 3.2.0 here :

    6e7b686d-031c-4e98-927e-a5df67906c25-image.png

  • Size is good, is just the focus when we type text it has changed

    on 3.1.7 :

    image.png

    On 3.2.0 here :

    6e7b686d-031c-4e98-927e-a5df67906c25-image.png

    wrote on last edited by
    #38

    @DownPW Yes, that’s input:focus - it’s used to style much larger boxes on focus, but I’ll need to create an exemption here.

  • wrote on last edited by
    #39

    Nodebb communauty :

    image.png

  • Nodebb communauty :

    image.png

    wrote on last edited by phenomlab
    #40

    @DownPW @cagatay Thanks for reporting. Should match now.

    f99597be-2d44-4c14-a46d-c803de6d9347-image.png

  • wrote on last edited by
    #41

    yep better 🙂

    Solution ?

  • yep better 🙂

    Solution ?

    wrote on last edited by phenomlab
    #42

    @DownPW As you indicated, but I need to make this more specific because it disables a wanted UI experience elsewhere

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        /*box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important; */
        border-color: transparent !important;
    }
    

    Starting with this CSS

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        border-color: transparent !important;
    }
    .write-container .form-control:focus {
        box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important;
    }
    
  • wrote on last edited by
    #43

    Have you find better solution or this is the final @phenomlab ?

  • Have you find better solution or this is the final @phenomlab ?

    wrote on last edited by
    #44

    @DownPW this is the final solution from my perspective. The above code resolves the issue here.

  • Have you find better solution or this is the final @phenomlab ?

    wrote on last edited by
    #45

    @DownPW i m also using last codes on my web site.

    .form-control:focus {
        background: var(--bs-body-bg) !important;
        color: var(--bs-body-color) !important;
        border-color: transparent !important;
    }
    .write-container .form-control:focus {
        box-shadow: 0 0 0 2px var(--bs-tag-bg) inset !important;
    }
    
  • wrote on last edited by
    #46

    I have search and I use this code. What do you think ?

    textarea.bg-transparent.text-body.form-control.chat-input.mousetrap.rounded-0.border-0.shadow-none.ps-1.py-0 {
        box-shadow: 0 0 0 1px transparent inset !important;
    }
    
  • I have search and I use this code. What do you think ?

    textarea.bg-transparent.text-body.form-control.chat-input.mousetrap.rounded-0.border-0.shadow-none.ps-1.py-0 {
        box-shadow: 0 0 0 1px transparent inset !important;
    }
    
    wrote on last edited by
    #47

    @DownPW Seems fine.


Related Topics
  • What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    5k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • Page control arrows for PWA

    Solved Customisation nodebb
    27
    25 Votes
    27 Posts
    15k Views
    phenomlab
    @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.
  • Upgrade issues

    Solved Configure nodebb
    2
    1
    2 Votes
    2 Posts
    1k Views
    DownPW
    Use this code git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x And you will have the latest version without specifying it https://docs.nodebb.org/configuring/upgrade/
  • Nodebb design

    Solved General nodebb
    2
    1 Votes
    2 Posts
    1k Views
    phenomlab
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • Plugin to show images in teasers

    General nodebb teaser image plugin hook
    6
    1
    2 Votes
    6 Posts
    2k Views
    phenomlab
    @dave1904 I’d start by adding a console.log function to hookData so you can see what is being returned return hookData; console.log(hookData):
  • build nodebb Warning in entrypoint size limit

    Solved Performance nodebb
    2
    0 Votes
    2 Posts
    1k Views
    phenomlab
    @eeeee they are nothing to worry about, and can be ignored.
  • NODEBB: Nginx error performance & High CPU

    Solved Performance performance nodebb nginx
    69
    4
    14 Votes
    69 Posts
    63k Views
    DownPW
    @phenomlab Seems to be better with some scaling fix for redis on redis.conf. I haven’t seen the message yet since the changes I made # I increase it to the value of /proc/sys/net/core/somaxconn tcp-backlog 4096 # I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! #save 900 1 #save 300 10 #save 60 10000 If you have other Redis optimizations. I take all your advice https://severalnines.com/blog/performance-tuning-redis/
  • How to fix header side as boxed

    Solved Customisation header boxed sudonix nodebb
    10
    1
    6 Votes
    10 Posts
    3k Views
    cagatay
    @phenomlab yes it caused a problem for mobile users. thank you for helping …