View Single Post
Old 04-07-2014, 03:18 PM   #633
Rev. Bob
Wizard
Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.Rev. Bob ought to be getting tired of karma fortunes by now.
 
Rev. Bob's Avatar
 
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
Quote:
Originally Posted by Perkin View Post
Yeah, I know the niggle I've got had something to do with, as you say, a css styled tag which caused the layout to be changed, I just can't remember what it was completely.

As it was a while ago when I saw it, then it can't be in widespread use, so you should add 'empty' tags to the cleanup.
I can see how to do that with a self-closed empty container, just by adding an "if equals <i/>, <span/>, or <b/>" to the pair-routine processing. I just don't see how to do it with the container forms, because as far as I can tell, that code can't see both the open and close tags at the same time, or determine whether there's anything between them.
Rev. Bob is offline   Reply With Quote