#14 Negated relations don't get crossed in Webkit browsers



I'm using jsMath 3.6b on my site and I just noticed that the negated relations don't get crossed in Chrome and Safari 4. You can check it in the online example at http://www.math.union.edu/~dpvc/jsMath/symbols/relations.html where \neq (not eqal) displays the same way than the "equal" sign. The same is for the other ones too, \notin the only operator which gets crossed.

As a sidenote: thank you for this wonderful application, this was a quite simple and crossbrowser option to display math on our Drupal site :)


  • Davide P. Cervone

    Thanks for the bug report. The character used by \not seems to be a zero width character (so it combines with the character that follows it by overlapping it), and WebKit sometimes doesn't seem to want to display this (sometimes it does, but I haven't been able to determine the conditions that determine when). For example \not works properly when used in the interactive lab (where I usually test things). Most peculiar.

    In any case, I will include a fix in the next release of jsMath. Until then, however, you can do the following:

    Create a file (say jsMath/local/safari-patch.js) that contains the following lines:

    if (jsMath.browser === "Safari" || jsMath.browser === "Chrome") {

    then add "local/safari-patch.js" to the loadFiles array in your easy/load.js file.

    I note that you are using Drupal, and a quick check of the implementation of jsMath for Drupal suggests that the jsMath module creates the equivalent of the easy/load.js file on the fly, but that there is a configuration panel for jsMath that you can use to set the loadFiles array. I don't know much about Drupal, so can't tell you where to find that panel, but if you know where it is, you should be able to add local/safari-patch.js to the loadFiles list.

    Hope that helps.


  • Davide P. Cervone

    • status: open --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks