I think I heard something about Google making their rich text editor open source recently. This wasn’t the old editor that uses execCommand - I believe that one is already available in their Closure library. I’m talking about the newer editor they built completely from scratch using custom JavaScript. This one handles everything internally like cursor positioning and text formatting without relying on browser APIs.
I’m pretty sure I saw this mentioned somewhere, maybe during a recent Google event or conference. Has anyone else heard about this or seen the actual release? I’ve been searching but can’t find any official announcement. Would really appreciate if someone could point me in the right direction or confirm if this actually happened.
Actually looked into this after seeing similar discussions. Google hasn’t open-sourced their modern WYSIWYG editor yet. You might be thinking of their recent tech talks about the architecture behind their new editor, but they only shared concepts - no actual code. The presentations covered ditching contentEditable and execCommand, which got developers pretty excited. Their Closure library still has the old editor, but the new version they built from scratch stays internal. Worth watching their dev blog and GitHub though - they sometimes open source internal tools once they’re mature enough.
ohh, totally feel you! i heard the same buzz but it’s pretty vague. like, they hinted at some updates but no links or anything official. weird that they wouldn’t share it if it’s released. let’s keep our eyes peeled for any updates!
Just checked their official channels and dev docs - nothing about open sourcing the custom WYSIWYG editor. You probably saw their engineering blog posts about rebuilding their editor without contentEditable. Those articles got tons of discussion in the dev community, which might’ve looked like a release announcement. Google’s been pretty vocal about how broken browser editing APIs are and their workarounds, but they’re keeping the actual code proprietary for now. Their engineering teams often take years between talking about internal tools and actually releasing them, so maybe there’s still hope.