pagure

#2284 Wrong rendering for certain (README) files
Closed: Fixed Opened by hosiet.

Closed: Fixed
Reopen Issue

Check out this page: https://pagure.io/fork/zhsj/pagure/blob/debian/f/debian

You can see the rendering of README.source file is completely messed up by a < char inside the text.

Metadata Update from @pingou:
- Issue tagged with: bug

The cause is that in jinjia template:

   {% if safe %}
     {{ readme | noJS |safe }}
   {% else %}
     {{ readme | noJS }}
   {% endif %}

the input first is filtered with noJS, which escaped unsafe things. Since the ext is .source, the input is marked unsafe, then jinja escapes it again and results double escape.

I doubt why we treat different ext files with safe and unsafe, since they both will be filtered by noJS and return safe string.

pr https://pagure.io/pagure/pull-request/2289

Fixed in the PR mentioned above

Fixed in the PR mentioned above

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None

bug

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.