Chris Chudzicki

Open one of the examples and run `mathbox.debug()` in the console. Some useful info is printed, but the last piece is: ``` api.js:218 Uncaught TypeError: Cannot read properties of null...

Update the jupyter notebook example to use current version

4

See discussion in https://github.com/unconed/mathbox/pull/17

memoized function has no length

4

Memoizing a function sets its length property to zero: ```js import memoizeOne from 'memoize-one' f = (a, b, c) => a*b*c memoF = memoizeOne(f) console.log(f.length) // 3 console.log(memoF.length) // 0...

Writing tests in typescript

6

In https://github.com/josdejong/mathjs/pull/2544#issuecomment-1109396849 @gwhitney pointed out that `index.d.ts` and `index.ts` are becoming rather large. Setting `index.d.ts` aside (admittedly, the problem is worse in that file!), the comment got me thinking... maybe...

Proposal: add a SensorOptions property to facilitate disabling drag on interactive elements

2

#### Problem Sometimes it is useful to make an entire element draggable, except interactive child elements. **Current Solution:** As discussed in https://github.com/clauderic/dnd-kit/issues/477, a current solution to this issue is a...

Python values don't print correctly after being used inside \text{}

1

If `\py{}` is used inside the `\text{}` command, the next use of `\py{}` prints the wrong value. Here's an example: ``` \documentclass{article} \usepackage{pythontex} \usepackage{amsmath} \begin{document} \begin{pycode} m1 = 3 m2...

Like `cross`. This is done already for most common function names. Also, make sure this doesn't impact MathQuill's performance.

1. Set calculated camera position 2. change axis scale or range — camera position is now incorrect 3. Update camera position — camera position is now correct This could be...