Weird inline Mathjax processing

[honggaruy]

Hi, I am not familiar with Mathjax syntax. But i think this is weird.

* A safe integer is an integer that
  * can be exactly represented as an IEEE-754 double precision number, and
  * whose IEEE-75 representation cannot be the result of rounding any other integer to fit the IEEE-754 representation
* For example, $ 2 ^ {53} - 1 $ is a safe integer,

The above case has no problem where the Mathjax line is the last li node. But if I add one more li node , it rendered like this; The Mathjax part is not processed.

* A safe integer is an integer that
  * can be exactly represented as an IEEE-754 double precision number, and
  * whose IEEE-75 representation cannot be the result of rounding any other integer to fit the IEEE-754 representation
* For example, $ 2 ^ {53} - 1 $ is a safe integer,
  * it can be exactly represented 

I want to show one more case. If I add few more lines and I ended it with Mathjax line like this, it shows no problem again.

* A safe integer is an integer that
  * can be exactly represented as an IEEE-754 double precision number, and
  * whose IEEE-75 representation cannot be the result of rounding any other integer to fit the IEEE-754 representation
* For example, $ 2 ^ {53} - 1 $ is a safe integer,
  * it can be exactly represented 
  * no other integer rounds to it under any IEEE-754 rounding mode.
* In contrast, $ 2 ^ {53} $ is not a safe integer.

But if i add strong tag to the not word in the last line, the Mathjax processor not working again as follows.

* A safe integer is an integer that
  * can be exactly represented as an IEEE-754 double precision number, and
  * whose IEEE-75 representation cannot be the result of rounding any other integer to fit the IEEE-754 representation
* For example, $ 2 ^ {53} - 1 $ is a safe integer,
  * it can be exactly represented 
  * no other integer rounds to it under any IEEE-754 rounding mode.
* In contrast, $ 2 ^ {53} $ is **not** a safe integer.

Can you tell me what is the problem ?

[jeffreytse]

Hi @honggaruy

Thank you for the reporting, I will do some further investigation.

Thanks and regards

[jeffreytse]

Hi @honggaruy

This issue has been addressed and fixed. Please update your plugin to the latest version.

Thanks and regards

[honggaruy]

After update, the problem solved !!