crimson kindle
Sometimes when editing on the web ui with automatic preview, the live preview will bug somewhat and no longer reflect the correct text. It'd be nice to have a button that forces the document to be recompiled so that it's in sync with the source again. See attached picture for an example of the issue I describe (beginning of the second sentence of the first section, "Lorsqu'on" becomes "Souvorsqu'on")
gleaming schooner
That button seems a bit contrary to our goal. Better we fix that bug. Do you know of a reliable way to reproduce it?
tidal skiff
That button seems a bit contrary to our goal. Better we fix that bug. Do you kno...
Maybe it would be nice to recompile on Ctrl + S
The keybinding is in need of overwriting anyways IMO, because for people used to pressing it all the time, the "Save html page" popup is annoying as hell
And if everything compiled correctly anyways, no harm is done
tired phoenix
@crimson kindle @tidal skiff mind opening an issue for this and linking it here? Thanks.
bleak hearth
I’ve opened an issue I believe is related to this: https://github.com/typst/webapp-issues/issues/177
tired phoenix
Thanks!
I believe this particular issue is currently being worked on right now, so we should receive more updates soon™️ by the Typst team
midnight vale
That button seems a bit contrary to our goal. Better we fix that bug. Do you kno...
I agree, though admittedly I think a "Restart compiler" button somewhere is a good failsafe in case of anything.
I personally prefer that over reloading the page to restart the compiler (especially since that can feel unsafe).
I have yet to lose connection to the server, so I don't know if you have a failsafe for that.
But consider losing connection to the server and nothing is being saved.
Someone may think the compiler is just bugged, and instinctively click Ctrl+R (I certainly have been). At which point they lose progress.
Obviously I (or others) shouldn't instinctively hit Ctrl+R, but at such early stages of the app, I think it's better safe than sorry.
Even for late stages, I think it's justified just by the fact that anyone could find some niche code that has to lead to reloading.
In fact, I would say that as someone's working on something more niche, it's probably more likely they'll have lots of data to potentially lose.
gleaming schooner
I have yet to lose connection to the server, so I don't know if you have a fails...
All changes are also saved locally in the browser.
midnight vale
Wouldn't a web browser just say "Cannot connect" if the server was completely down and you refreshed the page?