Why was this issue changed from "bug" to "improvement"? It worked before and is broken now and there was no need to change it. So it's a bug.

Likewise affected. 

Now, to style my job descriptions I need to use the Simple Theme plugin, but since I can't add class to a div anymore, I need to use selectors like 

  div#description>div>div:nth-child(2)

to style them.  Or, I suppose, I can switch to using style="" since all my job descriptions are generated with Job DSL anyway.

Guys any update on that issue?
We have the same problem and I'm looking for workaround since we can not use CSS classes.

No reaction? Seriously?

Still forced to use 1.8 because of these unnecessary restrictions

See the comments in https://github.com/jenkinsci/antisamy-markup-formatter-plugin/pull/12#issue-461987547 that describe why the defaults were made more restrictive.

No, these comments do not describe why it was made THAT restrictive. While it might be reasonable to remove form elements (and even that is still something the user should be able to decide instead of saying "We know what's best for you"), it is NOT reasonable to remove attributes like class or title.

We too are facing lot of issues after upgrading from 1.8 to 159.v25b_c67cd35fb, all dropdowns which are using div id and class for chevron down are getting removed. We had requirement to upgrade this plugin inorder to fix vulnerable versions with other plugins. When this issue can be addressed? any help on this please.

sirishabonthu as far as I can tell, there is no intention to change from the current behavior of the plugin.

markewaite  Div id and class attributes are getting removed and the dropdowns in the description are no longer working when upgraded OWASP MarkUp formatter from 1.8 to 159.v25b_c67cd35fb. We tried upgrading jenkins version to 2.387.3 which supports Customizable HTML Formatter Plugin, and defined policy to allow the div id and class attributes. Now the dropdowns are working as before.