[Bug]: Odd rendering of editor page

[IITYWYBMAB]

Installation Method

None

The Problem

Editor page rendering has some issues on Brave (Chromium 138.0.7204.184) .

Version of Stirling-PDF

Official docker, latest tag.

Last Working Version of Stirling-PDF

Unknown, new to project

Page Where the Problem Occurred

/view-pdf

Docker Configuration

services:
  stirling-pdf:
    image: docker.stirlingpdf.com/stirlingtools/stirling-pdf:latest
    ports:
      - 8069:8080
    volumes:
      - ./StirlingPDF/trainingData:/usr/share/tessdata # Required for extra OCR languages
      - ./StirlingPDF/extraConfigs:/configs
      - ./StirlingPDF/customFiles:/customFiles/
      - ./StirlingPDF/logs:/logs/
      - ./StirlingPDF/pipeline:/pipeline/
    environment:
      - DISABLE_ADDITIONAL_FEATURES=false
      - LANGS=en_US

Relevant Log Output

N/A

Additional Information

No response

Browsers Affected

Chrome

No Duplicate of the Issue

• [x] I have verified that there are no existing issues raised related to my problem.

[dosubot[bot]]

Hi @IITYWYBMAB! I'm Dosu and I’m helping the Stirling-PDF team.

This is a known issue affecting Chromium-based browsers like Brave and Chrome. Other users have reported odd UI rendering, especially on the /view-pdf page, often caused by CSS conflicts or changes in font weight on hover, which can make icons and menu items shift or render incorrectly. Clearing your browser cache or using incognito mode has resolved the problem for some users. If the issue persists, check for any console errors and try in a different browser (like Firefox) to see if it’s browser-specific. The frontend relies on PDF.js and standard browser APIs, so these quirks are likely due to recent Chromium updates or CSS interactions rather than Docker or backend configuration. You can find more details and user discussions about this issue here and here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[IITYWYBMAB]

Thanks for the update, I tried a private browser window in brave to eliminate the cache being an issue, yet it still renders in the same way.