Unable to type some mathematical symbols on chrome
See original GitHub issueSteps to Reproduce this:
- Create an exploration and add math expression input interaction.
- Click on preview button.
You’ll see that some mathematical symbols like =
, ^
, (
, )
etc., don’t work.
Expected Output: All symbols should work as they work in oppia.org.
Alternatively you can try the following link to reproduce the issue - https://oppiatestserver.appspot.com/create/16#/preview/Math Expression Input (scroll down to Math expression input card and click on preview button). There are also some console errors that pop up.
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Google Chrome: Math symbols don't appear correctly
I've been trying to figure out how to make the math symbols on this page to work, but with no luck. This is...
Read more >how do i do a less than or equal to symbol - Google Support
Ah, ok - I see. In any event, for a developer (such as I) the less than/equals sign is always simply <=.
Read more >Type Special Characters On a Chromebook (Accents ...
Typing special characters with a Chromebook can be done using unicode. Here's a handy reference to show you how.
Read more >How to type special characters and symbols on a Chromebook
Press Crtl + Shift + u and then let go of the keys at the same time. Type in the code for the...
Read more >Unable to render MathML content in Google Chrome
I found that MathJax can render Presentation MathML contents but cannot render Content MathML contents (I have both types of contents in my ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Following up from discussion with @hoangviet1993 – I think we can probably just unexclude the file in question (or even unexclude the whole folder containing the file).
Note that you can test a production env locally by running
bash scripts/start.sh --prod_env
.OK, great! Should you find any subsequent problem with this particular interaction. Feel free to re-open it!