Skip to content

Footer bar add center text

Solved Customisation
41 2 19.9k 1
  • @phenomlab

    I did the test on my desktop 34-inch screen in browser full screen and it works, then goes on my smartphone. (OnePlus 8T)

    Everything is fine unless I missed something 😉

    I mark as solved 🙂

    wrote on last edited by
    #29

    @DownPW that’s great news. Seems to work on my 32" desktop monitor fine, and also on my OnePlus 9 Pro 😁

  • @DownPW that’s great news. Seems to work on my 32" desktop monitor fine, and also on my OnePlus 9 Pro 😁

    wrote on last edited by DownPW
    #30

    @phenomlab

    very odd, there are a bug :

    –> floatright text is invisible only on Firefox and is OK on chromium browser with the same code ?!

  • @phenomlab

    very odd, there are a bug :

    –> floatright text is invisible only on Firefox and is OK on chromium browser with the same code ?!

    wrote on last edited by
    #31

    Other bug :

    On home page. I must scroll down to see the footerbar.
    She’s not appear directly

  • Other bug :

    On home page. I must scroll down to see the footerbar.
    She’s not appear directly

    wrote on last edited by DownPW
    #32

    And lasts bugs on firefox Mobile (test with a smartphone, not on an develloper view on desktop) :

    • Like on chromium browser smartphone : On home page. I must scroll down to see the footerbar. She’s not appear directly

    • On firefox mobile, I have these when I scroll all the way down and when I scroll up/down:

    02fda5d2-c617-4dd6-9ee8-968bdd703f89-image.png 451947b8-c9e3-44c3-a356-08ce806de3b3-image.png

  • DownPW DownPW has marked this topic as unsolved on
  • @phenomlab

    very odd, there are a bug :

    –> floatright text is invisible only on Firefox and is OK on chromium browser with the same code ?!

    wrote on last edited by phenomlab
    #33

    @DownPW said in Footer bar add center text:

    floatright text is invisible only on Firefox and is OK on chromium browser with the same code ?!

    Typical Mozilla.

    Use this instead

    #floatright {
      float: right;
      bottom: 1px;
      font-size: 90%;
      line-height: 2.0;
      display: flex;
      position: fixed;
      right: 10px;
    }
    

    You might find that this messes with the alignment of text, so you’ll need to adjust line-height accordingly, or make the difference up with either margin or padding

    The #console-nav-footer element disappearing on Firefox is due to a bug - see https://bugzilla.mozilla.org/show_bug.cgi?id=1585254 and https://bugzilla.mozilla.org/show_bug.cgi?id=1760924

    The issue here is that the .row class used in core is set as below

    970e8fac-23c7-4621-975c-423a152ab3dd-image.png

    In Firefox, this has the undesired artefact of pushing other divs down because the browser interprets this as outside of the margins. You can prove this theory by removing the tick from the margin-right class shown above when in DEV mobile view - you should see the footer appear as soon as you remove the margin-right value from .row - in effect, you are setting the margins back to 0 meaning the content is rendered correctly.

    You could write a custom JS function to apply the right CSS to resolve this issue, but in fairness, it’s very easy to fake the Browser String, which could lead to more problems that you set out to solve.

    There are other ways to address this specific issue, but if it were me, I’d accept the bug until the Mozilla team actually address it.

  • @DownPW said in Footer bar add center text:

    floatright text is invisible only on Firefox and is OK on chromium browser with the same code ?!

    Typical Mozilla.

    Use this instead

    #floatright {
      float: right;
      bottom: 1px;
      font-size: 90%;
      line-height: 2.0;
      display: flex;
      position: fixed;
      right: 10px;
    }
    

    You might find that this messes with the alignment of text, so you’ll need to adjust line-height accordingly, or make the difference up with either margin or padding

    The #console-nav-footer element disappearing on Firefox is due to a bug - see https://bugzilla.mozilla.org/show_bug.cgi?id=1585254 and https://bugzilla.mozilla.org/show_bug.cgi?id=1760924

    The issue here is that the .row class used in core is set as below

    970e8fac-23c7-4621-975c-423a152ab3dd-image.png

    In Firefox, this has the undesired artefact of pushing other divs down because the browser interprets this as outside of the margins. You can prove this theory by removing the tick from the margin-right class shown above when in DEV mobile view - you should see the footer appear as soon as you remove the margin-right value from .row - in effect, you are setting the margins back to 0 meaning the content is rendered correctly.

    You could write a custom JS function to apply the right CSS to resolve this issue, but in fairness, it’s very easy to fake the Browser String, which could lead to more problems that you set out to solve.

    There are other ways to address this specific issue, but if it were me, I’d accept the bug until the Mozilla team actually address it.

    wrote on last edited by DownPW
    #34

    @phenomlab Thanks for the information, after research it seems to firefox don’t like sticky position too 😞

    I will test tonight your fix, I’m on the office actually

    Thanks

  • @phenomlab Thanks for the information, after research it seems to firefox don’t like sticky position too 😞

    I will test tonight your fix, I’m on the office actually

    Thanks

    wrote on last edited by
    #35

    @DownPW no problems. Let me know how it goes

  • @DownPW no problems. Let me know how it goes

    wrote on last edited by
    #36

    @phenomlab

    problem resolv for floatright on Firefox desktop with your last css above. thanks 👍
    For information, in my research I have seen this link wit hother fix (not tested) : https://stackoverflow.com/questions/27521676/position-sticky-not-working-in-firefox

    😉


    –> Now, I search to resolve if possible these 2 smartphone bugs (only on Firefox mobile version, OK on Chromium-based browsers ) :

    A- if I collapse the footerbar I end up with black space at the bottom :

    c7f4ce50-325a-4307-8fc4-eefe8296cdba-image.png

    B- In fact, the footerbar remains fixed and does not come down automatically if you zoom in on a page. Ceal works on Chromium-based browsers (vivaldi, brave, etc.)

    You have the same bug on sudonix

  • @phenomlab

    problem resolv for floatright on Firefox desktop with your last css above. thanks 👍
    For information, in my research I have seen this link wit hother fix (not tested) : https://stackoverflow.com/questions/27521676/position-sticky-not-working-in-firefox

    😉


    –> Now, I search to resolve if possible these 2 smartphone bugs (only on Firefox mobile version, OK on Chromium-based browsers ) :

    A- if I collapse the footerbar I end up with black space at the bottom :

    c7f4ce50-325a-4307-8fc4-eefe8296cdba-image.png

    B- In fact, the footerbar remains fixed and does not come down automatically if you zoom in on a page. Ceal works on Chromium-based browsers (vivaldi, brave, etc.)

    You have the same bug on sudonix

    wrote on last edited by
    #37

    @DownPW absolutely another Firefox related bug, so will need to check this. I don’t typically use Firefox myself so I’m not surprised at all that this specific issue manifests itself on sudonix also.

  • DownPW DownPW has marked this topic as solved on
  • @phenomlab

    problem resolv for floatright on Firefox desktop with your last css above. thanks 👍
    For information, in my research I have seen this link wit hother fix (not tested) : https://stackoverflow.com/questions/27521676/position-sticky-not-working-in-firefox

    😉


    –> Now, I search to resolve if possible these 2 smartphone bugs (only on Firefox mobile version, OK on Chromium-based browsers ) :

    A- if I collapse the footerbar I end up with black space at the bottom :

    c7f4ce50-325a-4307-8fc4-eefe8296cdba-image.png

    B- In fact, the footerbar remains fixed and does not come down automatically if you zoom in on a page. Ceal works on Chromium-based browsers (vivaldi, brave, etc.)

    You have the same bug on sudonix

    wrote on last edited by
    #38

    @DownPW I actually am unable to replicate this issue on sudonix.com via Firefox on a mobile. I did find a bug in the tooltip code (I render them slightly differently so that’s my own fault). However, the issue does indeed manifest itself on your site - this can only be an issue with the CSS.

    I know there is custom JS we developed for the footer bar, but this seems to work as desired. The odd positioning of the footer bar on scroll can only be Firefox’s interpretation of bottom: 0; when using position: fixed; - you might want to try bottom: 0px; instead as Mozilla may not fully understand CSS shorthand.

  • @DownPW I actually am unable to replicate this issue on sudonix.com via Firefox on a mobile. I did find a bug in the tooltip code (I render them slightly differently so that’s my own fault). However, the issue does indeed manifest itself on your site - this can only be an issue with the CSS.

    I know there is custom JS we developed for the footer bar, but this seems to work as desired. The odd positioning of the footer bar on scroll can only be Firefox’s interpretation of bottom: 0; when using position: fixed; - you might want to try bottom: 0px; instead as Mozilla may not fully understand CSS shorthand.

    wrote on last edited by DownPW
    #39

    @phenomlab Where you see bottom: 0; ?

    You seem to have not the bug on sudonix but yesterday yes. odd

    I don’t know. I can’t find the problem at the moment

  • @phenomlab Where you see bottom: 0; ?

    You seem to have not the bug on sudonix but yesterday yes. odd

    I don’t know. I can’t find the problem at the moment

    wrote on last edited by
    #40

    @DownPW said in Footer bar add center text:

    Where you see bottom: 0; ?

    Under div#console-nav-tab

  • @DownPW said in Footer bar add center text:

    Where you see bottom: 0; ?

    Under div#console-nav-tab

    wrote on last edited by
    #41

    @phenomlab said in Footer bar add center text:

    div#console-nav-tab

    Ah ok test with bottom: 0px !important; idem


Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Heading text on NodeBB forum

    Solved Customisation
    27
    1 Votes
    27 Posts
    11k Views
    phenomlab
    @mventures I’ve not done anything here.
  • Link Text Colour.

    Solved Customisation customise
    5
    2
    2 Votes
    5 Posts
    2k Views
    Sampo2910
    @phenomlab Thx again for the reply. Well I am sure that it will be well worth the wait. I will watch with anticipation. For now it is OK. Just small minor irritations I fell in a lot of NodeBB ‘default’ things.
  • 5 Votes
    9 Posts
    6k Views
    DownPW
    @phenomlab Very very great Mark Thanks again, It’s perfect now ! –> I share my code that I modified. I’ve added French and English comments. If you see things to change Mark, don’t hesitate. As usual, all the access paths (FA icons, logo) will have to be modified according to your architecture. You can also very well add/remove time slots and change welcome messages to suit your needs. Widgets ACP/HTML Widget Footer Logo <center> <br><br> <img id="thislogo" src="path/to/my/image"> </center> Widget Welcome Message <!-- IF loggedIn --> <div class="getUsername">, <a href="/me"><span class="username"></span></a></div> <!-- ENDIF loggedIn --> CSS – I added the size font-weight: 900; in the CSS because otherwise some FA icon wasn’t displayed correctly and reduce margin : i#thisicon { font-family: "Font Awesome 5 Free"; font-style: normal; margin-right: 8px; font-weight: 900; } .getUsername { padding-top: 20px; text-align: right; } /*Smartphone*/ /*On désactive le message de bienvenue"*/ /*We disable the welcome message"*/ @media all and (max-width: 1024px) { .getUsername { display: none; } } JAVASCRIPT // ------------------------------------------ // Welcome Message avec icône et Footer logo // Welcome Message with icon and Footer logo // ------------------------------------------ $(window).on('action:ajaxify.end', function (data) { //On récupère le username dans le DOM et on l'affiche //We retrieve the username from the DOM and display it function updateUsername() { $('.getUsername .username').text(app.user.username); } if (document.readyState === 'loading') { document.addEventListener('DOMContentLoaded', updateUsername); } else { updateUsername(); } //On déclare les variables principales (themessage & thehours) ainsi que les variables secondaires correspondants aux plages horaires //We declare the main variables (themessage & thehours) as well as the secondary variables corresponding to the time slots var thehours = new Date().getHours(); var themessage; var wakeup = ('Good day'); var morning = ('Good morning'); var lunch = ('Bon appétit'); var afternoon = ('Good afternoon'); var drink = ('Cheers'); var evening = ('Good evening'); var night = ('Good night'); var welcome = ('Welcome'); var matched = false; //On peux ici tester le résultat du code en spécifiant une heure (!!!IMPORTANT: Commenter une fois le script testé!!!) //Here we can test the result of the code by specifying a time (!!!IMPORTANT: Comment once the script has been tested!!!) //thehours = 20 //On déclare les plages horaires avec les icones FA et les logos //We declare the time slots with FA icons and logos path if (thehours >= 0 && thehours < 6) { themessage = night; theicon = "fa-solid fa-moon"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 6 && thehours < 8) { themessage = wakeup; theicon = "fa-solid fa-mug-hot"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 8 && thehours < 12) { themessage = morning; theicon = "fa-solid fa-sun"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 12 && thehours < 13) { themessage = lunch; theicon = "fas fa-hamburger"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 13 && thehours < 16) { themessage = afternoon; theicon = "fa-solid fa-sun"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 16 && thehours < 18) { themessage = welcome; theicon = "fa-solid fa-rocket"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 18 && thehours < 19) { themessage = drink; theicon = "fa-solid fa-wine-glass"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 19 && thehours < 20) { themessage = lunch; theicon = "fas fa-pizza-slice"; thelogo = "/assets/customlogo/XXX.png"; } else if (thehours >= 20 && thehours < 24) { themessage = evening; theicon = "fa-solid fa-tv"; thelogo = "/assets/customlogo/XXX.png"; } // Si la page active est un topic, on désactive/cache le message de bienvenue // If the active page is a topic, we deactivate/hide the welcome message if (window.location.href.indexOf("topic") > -1) { console.log("This is a topic, so hide the user welcome message"); $('#thisuser').hide(); } // Sinon, on affiche le message en fonction, l'icone FA et son emplacement (prepend) // Otherwise, we display the message in function, the FA icon and its location (prepend) else { $('.getUsername').prepend("<i id='thisicon' class='" + theicon + "'></i>" + themessage); $("#thislogo").attr("src", thelogo); //$('.getUsername').prepend("<img id='thisicon' src='" + thelogo + "'></>" + themessage); } });
  • [NodeBB] Import custom Font

    Solved Customisation custom fonts nodebb css
    12
    3 Votes
    12 Posts
    5k Views
    phenomlab
    @cagatay you’ll need to define this in the body tag (or another element if you want greater or more granular targets) - for example body { font-family: "Poppins"; font-size: 16px; } Essentially, you use the font-size CSS directive.
  • [NODEBB] Scroll Button

    Solved Customisation css javascript html scroll button
    7
    1
    0 Votes
    7 Posts
    3k Views
    phenomlab
    @downpw ooops. Forgot that. Thanks for adding.
  • [NODEBB] Welcome Message

    Solved Customisation css html nodebb
    20
    2
    13 Votes
    20 Posts
    9k Views
    phenomlab
    @DownPW the ‘js’ code for the banner takes the time from the client, so what it displays really depends on the regional settings for the operating system. I’ve not seen this issue myself but would like to see some examples of screenshots if possible.
  • NodeBB Footer

    Solved Customisation footer nodebb
    10
    1 Votes
    10 Posts
    4k Views
    JAC
    @phenomlab said in NodeBB Footer: @jac and you. Hope all is well and you recover quickly Thanks pal
  • CSS Help on my Flarum

    Solved Customisation
    5
    2
    2 Votes
    5 Posts
    3k Views
    phenomlab
    @mike-jones Yes, you’ll typically see this type of behaviour if there is another style that has higher priority in the sense that yours will be overridden. Using !important will override the higher preference, but should be used sparingly rather than everywhere.