There ain't much to see here, but I wanted to comfort anyone who has been experiencing issues with the new editor.
The main thing is that browser translations should work again (the new editor was restoring the original text when the translation tried to change the page).[1] There were also some inconsistencies with how markdown was rendered that @sox also fixed.
For anyone experiencing issues on Android, @rblb believes he's found and fixed the underlying cause. tldr some Android keyboards are buggy and we need to defend ourselves against them.
Merry Christmas!
One of the cool side effects of this was learning, for the first time, non-english speakers were using SN and how. ↩
From the PR:
This explains why I've had trouble reproducing it on emulator and is really useful info.
This has been a really good insight from @rblb, I hadn't thought of that. Excellent work to be honest.
This is the ultimate upside for developing in public. Yes, it's hard mode compared to the safety of a private repo, but look at the undiluted awesome you get for it. Thanks for not adopting the Goog/MS/Signal(!) model of throwing the blueprint to a walled garden over the fence (aka virtue signal FOSS.)
Gracias por el arreglo no estaba entrando en la plataforma era muy difícil estar copiando para traducir. Ya están en las grandes ligas wui 🧡⚡
In regard to 1, any interesting insights on the use cases of non-English speakers?
Merry Xmas and May SN grow from strength to strength
I didn't glean much other than there's more than one of them here and they need auto-translation. I didn't know SN
Fascinating. Let me type in Chinese or Japanese and see if SN translations are accurate enough!
Will get back to you
Antes se traducía automáticamente todo luego solo los encabezados pero no el resto ahora todo se traduce automáticamente otra vez muy feliz como lombriz, 👍
Yo hablo español,
And we are all the better because of it. Looking forward to learning more about Cuba from you
Cuando quieras solo pregúntame 🙋😅
I should say, they are buggy when intersected with
contenteditable=trueimplementations in Android browsers.contenteditable=trueis its own unavoidable abomination, and we should always feel sorry for browser devs because their job is incredibly hard.On the brightside, a new ContentEditable standard should see the light of day soon.
Hmmmm regardless, I'm beginning to think the only right way to implement an in-browser WYSIWYG is to use an HTML canvas. Kind of like Figma - control the pixels yourself.
This guy did a pretty excellent job: https://canvas-editor.com/demo
... but it's closed source.
This is the most approachable actively maintained open source project I could find: https://github.com/Hufe921/canvas-editor
OnlyOffice is AGPL but they use a canvas: https://github.com/ONLYOFFICE
Collabora Online also uses canvase and is licensed under MPL 2: https://github.com/CollaboraOnline/online
this is amazing news!
Merry Christmas! My mobile editing cheer just went up to 11!
It's not fixed yet, but should be improved in a few days after some review and testing.
Namaste 🙏
Everyone can be in SN ❤️
Glad it’s finally fixed.
(Before, whenever I clicked translate, the page would just go to “Not Found.”)
I have yet to review the Android keyboard megafix, but I’m pumped!
Merry Christmas SN 🎄
Yeah a lot of the bugs have been fixed
Merry Christmas