DomSanitizer should keep style attributes in HTML, but sanitize them if needed

[pcroc]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

DOM sanitizer removes style attribute from all elements.

Expected behavior

DOM santitizer keeps the style attribute on elements, but sanitizes the actual style value if needed, so something innocuous like style="text-align: center" isn't lost.

Minimal reproduction of the problem with instructions

http://plnkr.co/edit/AjJMr2pDz8IxvucnpTbC?p=preview

What is the motivation / use case for changing the behavior?

Displaying blog posts or other CMS content which uses inline styles for layout/styling.

Environment

Angular version: 4.3.6

[Jahrenski]

Totally relevant because the only way to allow styles at the moment is to entirely trust the input.
The use case for this is displaying user input from a rich text editor.
I want to strip any dangerous bits about javascript, resourceURL and the such but keep the style attributes intact.

[waterplea]

Just hit the same thing working on a WYSIWYG. Native execCommands for justification and highlight colors add styles for background color and for text-align but these styles are removed by sanitation. Would be great to have sanitizer remove only dangerous stuff!

[Vandivier]

Please take a look at the following, and consider upvoting, as a generic solution for this and other similar problems:
#36650

but sanitize them if needed could specifically be solved by using a trustAttribute I suggest in the above issue.

[jessicajaniuk]

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular version.

If the problem still exists in your application, please open a new issue and follow the instructions in the issue template.