Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
\not =, \neq, \ne, etc. not aligned correctly inside iframe [pen included]
See original GitHub issueBefore 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 bug:
As the title says, \not =, \neq, \ne, etc. are not aligned correctly inside the iframe even though it loads fine outside an iframe; other things don’t seem to have issues, including fractions, which seems to have been reported before
(La)TeX code: The code of (La)TeX you tried to render:
a \ne b
a \neq b
a \not = b
(in math mode, both display and inline)
Expected behavior: i’d expect it to look the same inside and outside an iframe because everything else seems to do that
Pen: https://codepen.io/anon/pen/XLvvvL
Environment (please complete the following information):
- KaTeX Version: 0.10.2
- Device: MacBook Air 2018
- OS: OSX Mojave (10.14.5), also tested on Windows 10
- Browser: FireFox 68.0, Safari 12.1.1, Chrome 75.0.3770.142
- Version: see above?
Additional context: n/a; thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Indeed, although I think they’re most often (?) used with
src, and in that context, it makes sense to inherit the DOCTYPE of the linked document.The problem is that the iframe doesn’t have a
<!DOCTYPE html>, so it’s running in quirks mode. Addingiframe.write('<!DOCTYPE html>')fixes the problem.I forget what our current state is with respect to quirks mode (level of support), but I think rendering issues like this are not unexpected.