\tag is expected to be always flushed at right when equation is overflowed

Before reporting a bug

• Check common issues.
• Check the bug is reproducible in the demo. If not, check KaTeX is up-to-date and installed correctly.
• Search for existing issues.

Describe the pool rendering: For a long equation set to overflow-x: auto, the right-end \tag{} will overlap and scroll with the equation. You can use Eqs. 7.85 and 7.86 as a test case (with a narrow window), available here.

// allow katex equations scrolling horizontally, without vertical scrollbar
.katex-display > .katex {
    height: auto;
    overflow: hidden;
    overflow-x: auto;
}

Expected behavior: The \tag will be flush right no matter the equation is scrollable or not. I’m not familiar with CSS. I tried to play around

.katex-display>.katex>.katex-html>.tag {
    position: absolute;
    right: 0;
}

A feature of position mixturing absolute and static should be perfect. sticky doesn’t fit in current setting, it is a mixturing of relative and fixed as I understand.

[mbourne]

Any update/process on this?

[arctic-hen7]

I’ve been able to ‘fix’ (i.e. hack my way out of) this problem with the following CSS (closely inspired by @martinpflaum’s suggestion):

.katex-display > .katex > .katex-html > .tag {
  position: relative !important;
  right: -5rem !important;
}

@media (min-width: 1280px) {
  .katex-display > .katex > .katex-html > .tag {
    position: absolute !important;
    right: 1rem !important;
  }
}

On small screens (i.e. anything less than 1280px in this example), this will position the tag relatively to the equation, shifting it over by 5rem to give it some space. However, on larger screens, this leads to the tags being all out of sync, which looks frankly awful, so the second part of this just makes them absolutely positioned again in such cases (the right positioning there is just personal preference for me). It’s not perfect, especially not on tablet screens, but it’s better than the overlap.

Would it be appropriate to submit a PR for this, at least until someone comes up with something better? The default behavior at the moment is hardly ideal…