Special characters are incorrectly displayed as html entities in PLP

The filters of the PLP display special characters such as & and " as their html entities & and ". The built-in Results Layout component does not have the same problem It outputs & and " as they are.

The code should be fixed to address this bug. Currently anyone that codes a custom PLP will start with this lightning quickstart, which means that all of Salesforce's customers that have a custom PLP have this problem. It's possible that this happens in other areas of code as well, but I've noticed it on the PLP search result filters.


Compare the custom PLP search result filters with the built-in Results Layout component, which reportedly renders special characters correctly. Trace the filter output and identify where ampersands and quotation marks become HTML entities; done means the custom PLP displays those characters as characters rather than encoded entities.

Written by the indexing model from the issue text.