KaTeX: \not (and \neq) broken in ~~Chrome 72~~ Safari
$\neq$ or $\not =$ doesn’t work correctly. Please take a look into the documentation too.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 9
- Comments: 32 (16 by maintainers)
Commits related to this issue
- Change \not glyph to non-combining character Move `\not` glyph (`\@not`) from U+338 (COMBINING LONG SOLIDUS OVERLAY) to U+2044 (FRACTION SLASH). Both choices are a hack; what we want is a non-combin... — committed to edemaine/katex-fonts by edemaine 5 years ago
- Fix \not and \neq via new Unicode symbol U+E020 Fix #1842 — committed to edemaine/KaTeX by edemaine 5 years ago
- Fix \not and \neq on Chrome via new Unicode symbol U+E020 (#1852) * Fix \not and \neq via new Unicode symbol U+E020 Fix #1842 * Fix font metrics * Update screenshots * Use lower case lett... — committed to KaTeX/KaTeX by edemaine 5 years ago
- Fix \not (U+E020) RBearing (width) Fixes KaTeX/KaTeX#1842 on Safari. Also removed unused extra code (notin and noteq). — committed to KaTeX/katex-fonts by ylemkimon 5 years ago
- Fix \not (U+E020) RBearing (width) (#60) * Fix \not (U+E020) RBearing (width) Fixes KaTeX/KaTeX#1842 on Safari. Also removed unused extra code (notin and noteq). * Fix typo * Update fontM... — committed to KaTeX/katex-fonts by ylemkimon 5 years ago
- Fix \not (U+E020) RBearing (width) (#1878) Fixes #1842 on Safari. Also removed unused extra code (notin and noteq). — committed to KaTeX/KaTeX by ylemkimon 5 years ago
This is ridiculous. First Safari can’t handle negative advance so we get rid of it and then Chrome decides to add negative advance to combining characters that don’t have it. 😞
@edemaine thanks for coming up with a fix for this. 🙂
FWIW, a colleague suggested a workaround which appears to work on Safari with 0.10.1: use \cancel= instead of \neq. Granted the display is different for these two commands, but maybe others will find this is a useful workaround until the issue is fixed.
v0.10.1 is released, which includes a hotfix to this bug!
I’ve published 0.10.2 with a fix for this on Safari.
For those in a rush to deploy this fix (as I was) and using KaTeX via npm, you can use
to get a release with this bug fixed – but also with potentially dangerous unprotected
\includegraphicssupport, so beware!@kevinbarabash Could you review the fix in https://github.com/KaTeX/katex-fonts/pull/58?
I’m having the same issue with Chrome 72.0.3626.109 on my Mac and also Chrome 72.0.3626.105 on Android. Freakin’ hell.
https://github.com/KaTeX/katex-fonts/pull/58 is (most of) a fix to this bug.