Peter E Higgins
Peter E Higgins
slightly terrified at the cross-browser implications here :) would be trivial to support foreColor, but would need to include a UX for a color picker, which could get large. Seems...
additional outloud thinking: should go ahead and do foreColor backColor as near-identical things. Wouldn't be horrible to provide the 'default' color selection as just accepting a string hex value to...
@davi added the tag, but this is a contenteditable "core" issue where if you have css rules that are styling things these `span[style]` tags are created when two conflicting font-rules...
I have a similar hack in place, but it causes all sorts of strange behavior to undo stack doing that dom manipulation that way.
I have a partial solution involving (one) of the causes, a backspace at the beginning of a node with trailing content causes the mismatched styles ... i do the unwrapping...
``` js define([], function(){ function replaceinner(node){ var range = document.createRange(), inner; range.selectNode(node); inner = range.cloneContents().textContent; range.deleteContents(); range.insertNode(document.createTextNode(inner)); } function _toarray(qsa){ return Array.prototype.slice.apply(qsa); } function unwrapper(node){ // find all 's in...
half tempted to just rip $.each use out of there and for(;;;) that shit.
... it almost already can. the (maybe old?) built-in preview editor POSTS content and returns template-less rendering of content.
hmmm. I think the easiest solution would be to add them all in the root in a singe LICENSE file. The inclusion of the BSD license is a small divergence...
the HEAD of plugd was converted to work with the new AMD format coming in 1.7 .. define() is the new provide/require() pattern. Sounds like you are trying to use...