Thanks for reporting. Please provide a reproducible case.

I have added a bit more Detail with a Link to some evidence

I can see the issue on your page but I'm still not able to reproduce it. Using the formula you posted, no scrollbar appears:

I'm closing this as non-reproducible as it's unclear to me whether you are using customizations that might cause the error, because you supplied incomplete information in the mkdocs.yml section. If you manage to craft a minimal reproducible example with a clean installation, I'm happy to look into it and fix it.

I am having the same issue. You can see the scrollbars on my documentation's site here: https://firestarter-io.github.io/node-algorithm/algorithm/firespread/slope/

The code for this particular page can be found here: https://github.com/firestarter-io/node-algorithm/blob/rothermel-slope-aspect-ros/docs/algorithm/firespread/slope.md

If it helps, my mkdocs.yml looks like this:

site_name: name
nav:
  - About: index.md
  - Algorithm:
      - Overview: algorithm/overview.md
      - Data:
          - Types: algorithm/data/types.md
      - Fire Spread:
          - Slope: algorithm/firespread/slope.md
      - Notes: algorithm/notes.md
  - Components:
      - Campaign: components/campaign.md
      - Extent: components/extent/extent.md
      - BurnMatrix: components/burnmatrix.md
      - Cell: components/cell/cell.md
      - Priority Queue: components/queue/queue.md

theme:
  name: material
  logo: assets/flame.png
  favicon: assets/flame-docs.png
  highlightjs: true
extra_css:
  - stylesheets/extra.css
extra_javascript:
  - javascripts/config.js
  - https://polyfill.io/v3/polyfill.min.js?features=es6
  - https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js
markdown_extensions:
  - attr_list
  - pymdownx.superfences
  - pymdownx.arithmatex:
      generic: true
  - pymdownx.highlight:
      use_pygments: true

I'm not sure if this is the same as @LuciferUchiha 's issue, or if some external plugins / js / css may be causing the issue.

I came up with a CSS hack. In the project's extra_css, add this:

.MathJax.CtxtMenu_Attached_0 mjx-container[jax='CHTML'][display='true'] {
	margin: 0 !important;
}

That seemed to fix it for me. I'll leave the offending docs published for a little while so @squidfunk can take a look.

Short of a hacky CSS hack to stop this, I'm not sure what I might do to fix it.

@slutske22 I was able to fix it by adding

.md-typeset div.arithmatex {
    overflow: hidden;
}

Particularly overflow-y should be hidden. That's what I usually do. I don't usually hide the X direction. I don't often overflow in that direction, but I've never seen scroll issues related to the X direction.

Correct could be slightly preciser however I haven't run into any problems yet with this solution

Adding an example that seems to reproduce the issue for me:

• Source https://gist.github.com/akhmerov/8cbb4aa3af32d318f3fda76ffb5bf603
• Generated output: https://antonakhmerov.org/misc/site.zip
• Deployed website: https://antonakhmerov.org/misc/site/

I have confirmed that the scrollbar isn't gone upon replacing the html content with the one that is known to work, nor upon replacing the stylesheet (both using browser dev tools). All the dom elements seem to have identical sizes with and without the problem.

A PR is appreciated. Note that overflow: hidden as suggested in #3354 (comment) is likely not the solution, as this will break scrolling on narrow screens when the formula exceeds the width of the viewport.

@squidfunk Can you reopen this issue. It's not fixed yet.

Sure. If somebody manages to fix it, I'm happy to merge it.

Okay, I think I have a fix in e063108. I'm still not able to reproduce it, but #3354 (comment) was of great help, so I could copy over the generated markup to have a case to work on.

Released as part of 8.1.5. Please reopen if the issue still persists.

Just to mention something I noticed in case it reappears: it depends on the web browser.

I was still on version 8.1.4 and the issue only occurred with Chrome and Edge Chromium. But on Firefox it was fine.

Since both Chrome and Edge use the same engine behind the scene (Chromium) I suspect it is a floating precision or rounding issue where a one pixel difference make it appear or not.

Note: I'm on Windows 11, I didn't try on other OS.