Like Jake I use tons of PassThru HTML and discovered that it created all kinds of problems when I'm developing cause I was doing lots of cutting and pasting of stuff. (I think it is has to do with how you highlight either the first or last "characther" of the content being cut and then where you place the cursor when you paste it. End or start of paragarph is not end or start of paragarph.) So, for the longest time the trick I used was to highlight all the PassThru HTML and turn it off, then check to see that it indeed is off - sometimes the tick box stays checked eventhough the text was not highlighted and that just about always indicated a problem at display time. Then I would painstaking try to identify the cause.
Now with CSS I now develop the "element" individualy on seperate notes design elements. Once I'm happy with it I then "plug" it into the final form. I find that this allows me to easily identify where the display "big" is and apply a patch is need be by wraping it is a custom tag.
In situations where I need greater control, I'm strying away from using embedded views and using agents in their place.
Like Jake I use tons of PassThru HTML and discovered that it created all kinds of problems when I'm developing cause I was doing lots of cutting and pasting of stuff. (I think it is has to do with how you highlight either the first or last "characther" of the content being cut and then where you place the cursor when you paste it. End or start of paragarph is not end or start of paragarph.) So, for the longest time the trick I used was to highlight all the PassThru HTML and turn it off, then check to see that it indeed is off - sometimes the tick box stays checked eventhough the text was not highlighted and that just about always indicated a problem at display time. Then I would painstaking try to identify the cause.
Now with CSS I now develop the "element" individualy on seperate notes design elements. Once I'm happy with it I then "plug" it into the final form. I find that this allows me to easily identify where the display "big" is and apply a patch is need be by wraping it is a custom tag.
In situations where I need greater control, I'm strying away from using embedded views and using agents in their place.