Stuck on an issue?

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 (and \neq) broken in Chrome 72 Safari

See original GitHub issue

$\neq$ or $\not =$ doesn’t work correctly. Please take a look into the documentation too.

Issue Analytics

State:
Created 5 years ago
Reactions:9
Comments:32 (16 by maintainers)

Top GitHub Comments

3reactions

kevinbarabashcommented, Feb 9, 2019

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. 🙂

2reactions

jhugon61commented, Apr 21, 2019

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.

Top Results From Across the Web

Chrome Enterprise and Education release notes

Chrome now provides a custom default error page when Progressive Web Apps (PWAs) and Trusted Web Activities (TWAs) do not define a custom ......

Slide Layers Out of Order - Problem in Safari Has Now Spread ...

A new update to Chrome has exposed this Storyline 3 bug in Chrome -- so that modules (whenever they were created) will now...

Google Chrome on the App Store

Download the new Google Chrome for your iPhone and iPad. Now more simple, secure and faster than ever. Get the best of Google...

webGL not working in mac mini(in safari browser and chrome)

Upgrade Chrome to latest (72) and Safari (12) and try again. The versions you are running are several years old.

Video auto play is not working in Safari and Chrome desktop ...

The best fix I could get was adding this code just after the </video> <script> document.getElementById('vid').play(); </script> ...not pretty but somehow ...