I can see the postitives either way, but I still believe (IMVHO) that it's counter-intuititive to only apply an operation to part of the selection. It should be up to the user to realize that their choice was odd

I ended up applying H2 to both paras in BV, joining them, and finally inserting a line break so as to end up with a single H2 with 2 lines

Quote:

It does make sense to be able to apply a change like that to all the tags in a selection. Although it would be interesting to see how it handled any internal <span><em><strong>, etc. tags.

What was interesting was to use [H2] in code view with only a single <p>...</p> selected.
It ended up as <h2><p>...</p></h2>. I was expecting it to just replace the <p> tags. Just unexpected is all

I can see the postitives either way, but I still believe (IMVHO) that it's counter-intuititive to only apply an operation to part of the selection. It should be up to the user to realize that their choice was odd

I ended up applying H2 to both paras in BV, joining them, and finally inserting a line break so as to end up with a single H2 with 2 lines

What was interesting was to use [H2] in code view with only a single <p>...</p> selected.
It ended up as <h2><p>...</p></h2>. I was expecting it to just replace the <p> tags. Just unexpected is all

Paul

Sigil is quirky (It really is the toolkit's used fault). It has been that way since 2.0

Don't Select in BV for those tag buttons... Just click to set the cursor (insertion point) on the line. Now click the button.