-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add prosemirror support #970
Comments
Those Nextcloud links allow me to download the files, but I don't think they open the same editor view you are seeing. There is not place for Firenvim to be involved from an end users view without an account on your server (or a federated instance). |
Hmm I tested it several times, you should be able to edit the What browser are you using? |
@alerque Very weird, I can access the documents, served under a prosemirror instance, and edit them in Firenvim with the dedicated browser shortcut. Maybe your Firefox is too old or one of your extension is interfering? |
No my Firefox is not too old and I checked extensions. Yes I did find the trouble. Firefox has a crazy pants way of (not) recovering from a few errors. At the time I first opened something on that domain the disk where my cache was was full. Firefox noted the error, but now even having cleared up 100+ Gigs on the cache disk, rebooted, restarted Firefox, and trying to refresh the site it keeps throwing an This is not the site, Nextcloud, Firenvim, or any extension's fault: it is a known bug in Firefox that it doesn't recover from this error gracefully. I've run into it before on other sites and I think you have to manually clear local storage or something for the site to get it to recover. For the life of me I can't figure out what the magic sequence is right now. It works fine in private browsing mode but even with all extensions disabled and "clear site data and cookies" it still won't run in normal mode for me. Relevant Firefox bug report (opened 7 years ago). |
ZZ
or:wq
) the newlines (and thus the paragraphs) disappeared.I added three shared files to reproduce the bug:
.c
(doesn't work): https://cloud.daknuett.eu/s/M3YgKWiNKPDrDEq.md
(works): https://cloud.daknuett.eu/s/KAkPjDLSBn6pHTG.txt
(doesn't work): https://cloud.daknuett.eu/s/cZ79BjaA2tk5oMaThe files have different suffixes; it appears like the results depend on the file suffix.
The text was updated successfully, but these errors were encountered: