@Shaggy Yes, chrome on ios. I find chrome better than safari, safari is kind of clunky in my opinion

@EmbodimentofIgnorance iOS Chrome is, pretty much, just a shell for Safari so any bugs in the latter are most likely going to be present in the former. In this case, Safari still requires position:sticky to be prefixed (Prefixing?! In 2019?!). I have it fixed for the next update.

What happened to me only supporting Chrome with this project?! :D :\

Took a stab at tweaking Ace's language files for JS to see if I could get it to handle Japt's auto-closing, single quoted strings and (nested) interpolation and surprisingly, it did quite well :)

Obviously, though, we don't need the full range of JS highlighting for Japt so I'm still going to have to write a custom language file to save the overhead of, essentially, loading the same file twice. And keeping the editor synced with the original textarea and keeping the browser's undo/redo stack updated is going to be tricky but, all-in-all, this is definitely looking viable :)

Just pushed an update that fixes the position of the docs on iOS and adds a toggle for syntax highlighting, a Ctrl+G shortcut for auto-golfing & tooltips for keyboard shortcuts while Ctrl is pressed.

Trying to decide where the best place to put the toggle for disabling and enabling auto-run is - any suggestions? I was thinking above the input field.

Pushed another update. This one adds header & footer fields (which get included in the transpiled JS) and, because there's no so fecking many fields, non-essential ones are collapsed by default.

Also made some progress on the syntax highlighting front, solving the issue of how to keep everything synced and made a (very small) start into the language file. This one's going to take time as I try to account for as many edge cases as possible (and RegEx!) but it's looking very promising :)

Bonus: Ace supports language switching so I'll be able to highlight code between $s as JS.

@Oliver It's started happening for me again. Every damn time I load the page! Once is cool to draw attention to all the extra shit going on in the sidebars but it's starting to annoy the piss out of me.

I don't know why it's happening; the only logical (but not reasonable) reason I can think of is that, for some sort of efficiency reasons, Chrome Android first renders a page and then applies any CSS transforms.

@EmbodimentofIgnorance is the docs sidebar sitting properly on your iOS device now?

Wow I missed a lot of neat updates

@Shaggy Auto-run as in run the program on form load? Personally, I wouldn't add a toggle to turn that off. I love that feature. If you are going to add a bunch of toggles though, maybe add a [Tools] section somewhere so the main page isn't cluttered and offputting to new users

I love that some of the fields are collapsed by default. That makes it look really good

How does that differ from Notes?

Why is there a green border around the version in the Method sections, but not on Shortcuts?

And RegExp

And others

I don't know if I like that clicking the version on a method inserts the method into the Code field

As far as a Tools or Settings section. Maybe do something like the search where it reveals a new panel with inputs

When I compress something, I don't like that I can't manually copy the output. I know there's a button for that, but the option to do it manually would be nice

I like how holding Ctrl reveals the hotkeys