search

tsengwoody / Access8Math

Allows access math content written by MathML ; Assist writing math content by LaTeX
GNU General Public License v2.0
31 stars 15 forks source link

Access8Math does not read MathML content in Chrome #87

Closed MohamedNoordin closed 8 months ago

MohamedNoordin commented 8 months ago

For the first time I tried Access8Math, it worked very well without problems in Google Chrome, but when I disabled the add-on and then re-enabled it, it doesn't speak out MathML content in Chrome when I move over a line that contains MathML content, although the navigator object role is expressed as "MATH". Even when I hit the space bar for the dialog or the popup to open on the MathML element, nothing happens. Now, when I browse MathML content, NVDA speaks none. Peace and quiet. However, I tried to install both of MathCAT and MathPlayer, I tried to switch the math reader speach source to both of MathCAT and MathPlayer, also without a result.
When I tried to read math content in Edge using Access8Math, it reads MathML content without any problem. The problem lies in Google Chrome web browser. I am not sure what the problem is, but I am sure that I need it to work instantaneously.
I can provide any relavant logs/documentations once requested.

tsengwoody commented 8 months ago

Please confirm if the issue of not being able to read math content in Chrome persists when you disable Access8Math and switch to using MathPlayer. I haven't happend this problem after disabling and then reactivating Access8Math on my end. Perhaps you could provide the log for me to check what happen.

MohamedNoordin commented 8 months ago

I'm sorry, but the functionality only returned after closing all Chrome instances and opening a new clean session. Simply closing and reopening the specific Chrome instance/session was ineffective.
Unfortunately, I don't have relevant logs to share at this time. However, this suggests a potential instability issue within either Chrome, NVDA, or Access8Math.
Since the issue seems resolved for now, I'll close this issue. If I encounter the behavior again, I'll reopen a new issue with relevant logs attached for further investigation.
Thank you for your understanding.