jejacks0n/mercury — comment on commit 575e4451383502251f10512cecdf85dffb847d33
File: vendor/assets/javascripts/mercury.js line 254
By JeanMertz:

What is the reason for the `span` (and `div`) tag to allow classes? As far as I can see, if you copy content from somewhere else, the styles attached to these classes will be lost anyway, unless you copy from within your own website, but even then I believe allowing classes can be quite disruptive if the class contains things like a large width or height value or other things.

Furthermore, I'd argue that it'd be a good choice to allow `spans` and `divs` to have the `style` attribute. This is because Mercury itself actually uses inline styles on spans and divs to set things like `background-color` or `text-align`. If the user copies things from one editable region into another, it should be expected to look the same as the original.

In the future it would be nice to also filter the content inside the `style` attribute, but this is maybe a bridge too far at the moment.