3

The display_name field of a user is HTML escaped. See here for example.

Is this expected behavior or a bug? The documentation doesn't mention it.

4

It's mentioned under the Safety section of the filters documentation that by default all response data can be safely inserted into HTML, which is why the data is pre-escaped in this case. You can try creating an unsafe filter using the unsafe parameter to use if you wish to avoid this conversion.

| improve this answer | |

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .