Bruno Bornsztein
Bruno Bornsztein
Curious if there are any updates here? I'd love to keep using Legato for V4 if it's supported. If not, what are other people using instead?
@tpitale ok, I'd love to help out. Is [this](https://github.com/tpitale/legato/issues/137#issuecomment-589888626) still the best approach?
@tpitale happy to help out as much as possible! I just don't know the Legato internals all that well 😄
Ditto - this would be amazing.
I believe this has been discussed, but @daviferreira any more thoughts on using Scribe instead of native contenteditable? (see: https://github.com/lolJS/ghostwriter)
@nchase not sure - according to [this](https://github.com/guardian/scribe/issues/151) it seems like they're not supporting older browsers (but it's not clear exactly what they mean buy that). Looks like Safari 6 is...
Yup - however it may just be due to their testing setup. See here: https://github.com/guardian/scribe/issues/249 (bad Selenium support for Safari)
Here's my hack to fix it: ``` medium = new MediumEditor(.. your config here ...); el = medium.elements[0]; $(el).on("input", function() { $(el).find("span[style]").contents().unwrap(); }); ``` This basically just removes all spans...
Yeah, good point - hadn't thought of that. This issue is a pretty big deal for me; it basically renders the editor useless (since you can't count on consistent output)....