What is this bar called?

[DownPW]

Will test ASAP, i’m on new OGproxy conf now

[DownPW]

And where you put/replace this @phenomlab ? :

@phenomlab said in What is this bar called?:

And replace with this

<div id="readingposition" class="reading-meter" style="bottom: 0px;">
    <div class="reading-meter-background rounded-1 border border-gray-300 ready">
    <div class="reading-meter-progress-bar rounded-1" id="progress-bar">
        </div>
  </div>  
  </div>```

In the custom header I guess ?

[DownPW]

It seems to be worse. The JS no longer works.

When I remove the customJS and custom Header code. The website is OK

Could there be an error/omission in the given code? A typo in the code?

[phenomlab]

@DownPW strange. Is this on your dev server? I’ll take a look tomorrow morning.

[DownPW]

nope on my VM but you have an account on dev server

[phenomlab]

@DownPW ok. I’ll try it there tomorrow.

[phenomlab]

@DownPW said in What is this bar called?:

It seems to be worse. The JS no longer works.

When I remove the customJS and custom Header code. The website is OK

Could there be an error/omission in the given code? A typo in the code?

I must have been drunk or high on something else when I provided the code as there are large chunks of CSS missing, and a rogue closing parenthesis! That’s what too much work does I suppose

I’ve implemented the CORRECT version of this on your DEV site (tested ok) and updated the post so it reflects reality

[DownPW]

I thought something was missing…

I totally understand. Very tired me too at the moment and like you a lot of work provided between my job and the one done outside on PW

[phenomlab]

@DownPW said in What is this bar called?:

I totally understand. Very tired me too at the moment and like you a lot of work provided between my job and the one done outside on PW

Yes, that’s exactly the problem. Work is very demanding and has to come first, so I fit this (Sudonix) in whenever I can - often late into evenings and it’s easy to make even the simplest of mistakes

[phenomlab]

All - i found some bugs in the previous code that was posted, and have rectified the error. Please replace any code you are using with the revised version.

[DownPW]

@phenomlab

I don’t know why the reading-meter-progress-bar doesn’t appear on my smartphone (dev instance) when I scroll down but appear a little on scroll top ?

[phenomlab]

@DownPW That must be some sort custom CSS. I can’t reproduce that here. ,

[DownPW]

odd, no problem on desktop, just smartphone

[DownPW]

@phenomlab

It seems that code who caused problem :

/* Menu Brand Header */
@media (max-width: 767px)  {
  .socialicons {
    display: none !important;
  }
  [data-widget-area=brand-header] .d-none {
    display: inherit !important;
  }
  /* Button topic navbar header color */
  .sticky-tools .btn-ghost-sm i {
    color: var(--bs-alert-info-color) !important;
  }
}

If i delete :

[data-widget-area=brand-header] .d-none {
  display: inherit !important;
}

Reading progress bar is good now but my icons (menu and theme swatch applet) dissapear

[phenomlab]

@DownPW I’d put that CSS back. It’s set like that for a reason, so you’ll need to be more specific with the target so you can unset.

[DownPW]

Sorry but I do not understand too much @phenomlab because if I keep this code, the reading bar does not work on smartphone

[phenomlab]

@DownPW what I mean is target from higher above so the CSS you apply to the end target is not the same as an existing element.

[DownPW]

for brand header or for progress bar ?

[phenomlab]

@DownPW progress bar.

[DownPW]

@phenomlab

I just tested by deleting all the custom CSS code and keeping only the following CSS code

#pageUp {
  display: inline-block;
  background: var(--bs-body-component-active);
  width: 50px;
  height: 50px;
  text-align: center;
  border-radius: 0.375rem;
  position: fixed;
  bottom: 70px;
  right: 80px;
  transition: background-color .3s, opacity .5s, visibility .5s;
  opacity: 0;
  visibility: hidden;
}
#pageUp.show {
  opacity: 1;
  visibility: visible;
  z-index: 10000;
  color: var(--bs-body-navbar-color) !important;
}
a#pageUp.show:hover {
  background: var(--bs-dropdown-link-hover-bg);
  border: 1px solid var(--bs-border-color);
}
a#pageUp i {
    position: absolute;
    top: 32%;
    left: 35%;
}
.reading-meter {
    position: fixed;
    width: 100%;
    top: 0;
    left: 0;
    right: 0;
    height: 2px !important;
}
 
div#readingposition {
    background-color: var(--bs-body-navbar) !important;
    color: var(--bs-body-color) !important;
    height: 2px;
    z-index: 1000;
}
 
.reading-meter-progress {
    border: 1px solid var(--bs-border-color);
    width: 100%;
}
 
.reading-meter-background {
    background: var(--bs-body-bg);
}
 
.reading-meter-progress-bar {
    background: var(--bs-progress-bg-bar);
    height: 2px;
}
input#percentage {
    display: none;
}
 
@media (max-width: 767px) {
    #pageUp {
        bottom: 60px;
        right: 30px;
      }
    }
 
 
 
 /* Menu Brand Header */
@media (max-width: 767px)  {
  .socialicons {
    display: none !important;
  }
  [data-widget-area=brand-header] .d-none {
    display: inherit !important;
  }
  /* Button topic navbar header color */
  .sticky-tools .btn-ghost-sm i {
    color: var(--bs-alert-info-color) !important;
  }
}

There is clearly a conflict between his 2 codes.