I’ve run into an odd and inconsistent behavior with the @post-reading-time element and wanted to document it here in case others experience the same — or if it’s something the Bricks team needs to review.
The issue
When using @post-reading-time with an HTML prefix (for example an icon):
<i class="fas fa-timer"></i>
Bricks renders this correctly only when the element is inside a Query Loop and therefore targeting the queried post’s content.
However, when using the same element inside a template (Header, Single, Section template, etc.) that is not inside a Query Loop, the HTML prefix is rendered literally as text — e.g.:
<i class="fas fa-timer"></i> 3 min read
Possible explanation?
It seems Bricks might be sanitizing or escaping the element output differently when it’s not tied to a loop context.
This makes sense from a security perspective, but results in inconsistent behavior.
Why this matters
If you want consistent reading-time formatting across your site (single templates, archive loops, cards, etc.), the icon-prefix approach only works sometimes, depending on context.
