Changing text style type doesn't correct applied styles

[MikeTO]

Change character style to paragraph (or vice versa)

1. Apply Heading 1 (para) and Emphasis (char) text styles to some text
2. Edit Emphasis and change its type to Paragraph - the text styles panel will now show Heading 1 (para) and Emphasis (para) but not [No Style (char)]. The context bar will show Para = Heading 1 and Char = Emphasis, even though Emphasis is no longer a character style and isn't in the list.
3. Using the Text Styles panel, click Emphasis to re-apply it. The text styles panel will now show just Emphasis (para) but still won't show [No Style (char)]. The context bar will show Para = Emphasis and Char = Emphasis.
4. You have to click [No Style (char)] on your own to clear up the confusion.

I think if I change Emphasis from character to paragraph then all paragraphs with Emphasis applied should be changed from whatever paragraph style they were to Emphasis, and all text ranges that had Emphasis applied as a character style should be set to [No Style (char)]. And vice versa.

Change paragraph or character style to group style

1. Apply Heading 1 (para) and Emphasis (char) text styles to some text
2. Edit both styles and change them to group styles - the text styles panel will now show two groups selected which is odd since groups cannot be selected in the panel.  The context bar will show the para and char styles still being set even though they're no longer in the list.
3. You have to click [No Style} for both para and char on your own to clear up the confusion.

I think if I change a style to a group then Publisher should detach the style from its text and apply [No Style].

[MikeTO]

I should probably add that I know there are lots of ways to end up with two para or char styles selected, such as applying Heading 1 to characters or changing Heading 1 to show in both panels, but I think changing type should clean up after itself. Changing the style type in a long publication with hundreds of uses of the style could lead to a lot of confusion.

[stokerg]

Hi @MikeTO,

Thanks for reporting this.

I've just got this logged with the Developers