Inconsistent processing of custom styles

[Damian]

There are some inconsistencies in the way certain style rules are applied and how they show up in the styles drop down. This is down to the lack of support for upper level elements including: <a>, <tr>, <td> etc.

When a style is added to the list of styles involving the use of an <a> tag, if it is through a custom plugin, it is listed as a <span> element, and if it is through the 'stylescombo/styles/default.js' file, it doesn't show up at all.

[Garry Yao]

Sorry I don't understand the issue where, could you plz attach your styles definition to exemplify it?

[Alfonso Martínez de Lizarrondo]

I'm not sure about the second part as that looks like a bug in that custom plugin.

The first part is a summary of several tickets: #536, #667, #668, #717, #1053, #1897 Maybe there are other ones in Toolbar or in General

[Frederico Caldeira Knabben]

In fact, this is one of the new features we would like to propose in the 3.3. The ticket for it is #536.