View Single Post
Old 05-03-2023, 07:53 PM   #143
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,708
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by slowsmile View Post
I'm not quite sure why removing empty spans i.e. span tags containing nothing -- would cause any problems. If it does cause major problems, as you say, then perhaps it's best that I should just remove it altogether from the plugin(with no selectable option in the user dialog). Thoughts?
Sorry for the confusion. I have no opinion on removing spans that contain no text between the opening and closing span tags. I'm not certain why they'd be there in the first place, but removing them should change nothing. I've been referring to spans that contain text, but whose tags have no attributes. Removing those can change how things render (as others have already illustrated).

One option would be to stop removing naked (no attributes) span tags by default with the plugin. Then make it a manual preference to remove them. Those who know the risks (and know what they're doing) and want to remove them anyway, could always manually add something like a

Code:
"remove_naked_spans": true,
to the plugin's .json preferences file that the plugin could then honor.
DiapDealer is offline   Reply With Quote