![]() ![]() Generally speaking, i think it's best to choose a very universal format. you get locked-in to whatever system you choose - i don't like this option either Built for developers: Granular access to the editor’s content, changes and events through a simple API. If you save json, it doesn't sound to me like a universal format, so then you'll be stuck with whatever editor system can save/load that particular format. It is an ideal choice for developers who want to keep their content ready for Google's AMP, mobile content, instant articles, text-to-speech apps, and speech readers. ![]() however, loading up and injecting html is a serious xss security vulnerability: if an attacker could save malicious html, they could hijack your website - and html is difficult to sanitize for xss safety - so i'd say the html strategy is dead in the water Editor.js is an inline WYSIWYG editor that is generates clean structured JSON data. If you save html, then you could freely swap the underlying editor in the future. In addition to the standard HTML input formats, JSON Editor can also integrate with several 3rd party specialized editors. If you’re not familiar with the package, it’s a WYSIWYG editor that is built on top of Draft.js (which is built on top of React). #Wysiwyg json editor download#Nah, don't worry at all about the performance in deserializing the json, it's totally negligible.ĭisadvantages to saving the rich text as JSON? Download and try the JSON editing functionalities in JSONBuddy. A recent incident has been with React Draft Wysiwyg which we decided to use as part of our action to compose and send emails to people in your workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |