pull down to refresh

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!

  1. One of the cool side effects of this was learning, for the first time, non-english speakers were using SN and how.

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

reply
48 sats \ 2 replies \ @Angie 3h

Yo hablo español,

reply
Yo hablo español

And we are all the better because of it. Looking forward to learning more about Cuba from you

reply
0 sats \ 0 replies \ @Angie 30m

Cuando quieras solo pregúntame 🙋😅

reply
48 sats \ 2 replies \ @k00b OP 5h

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

  1. could be auto-translated
  2. was usable when auto-translated
reply

Fascinating. Let me type in Chinese or Japanese and see if SN translations are accurate enough!

Will get back to you

reply
0 sats \ 0 replies \ @Angie 28m

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, 👍

reply
100 sats \ 1 reply \ @Scoresby 6h

Merry Christmas! My mobile editing cheer just went up to 11!

reply
102 sats \ 0 replies \ @k00b OP 5h

It's not fixed yet, but should be improved in a few days after some review and testing.

reply
150 sats \ 4 replies \ @k00b OP 7h
some Android keyboards are buggy

I should say, they are buggy when intersected with contenteditable=true implementations in Android browsers. contenteditable=true is 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.

reply
0 sats \ 2 replies \ @k00b OP 7h
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.

reply
0 sats \ 1 reply \ @k00b OP 7h

This guy did a pretty excellent job: https://canvas-editor.com/demo

... but it's closed source.

reply
0 sats \ 0 replies \ @k00b OP 5h

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

reply
0 sats \ 0 replies \ @sox 7h
new ContentEditable standard should see the light of day soon.

this is amazing news!

reply
100 sats \ 0 replies \ @sox 7h

I have yet to review the Android keyboard megafix, but I’m pumped!

Merry Christmas SN 🎄

reply

Yeah a lot of the bugs have been fixed

reply
0 sats \ 0 replies \ @Angie 3h

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 🧡⚡

reply
0 sats \ 0 replies \ @SSS_S_S 3h

Glad it’s finally fixed.

(Before, whenever I clicked translate, the page would just go to “Not Found.”)

reply