We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Something noncompletely unreasonable like
"non" <> H.i "complete" <> "ly"
will give different results depending on which rendered is used:
Text.Blaze.Renderer.Text.renderMarkup gives
Text.Blaze.Renderer.Text.renderMarkup
non<i>complete</i>ly
as intended.
Text.Blaze.Renderer.Pretty.renderMarkup gives
Text.Blaze.Renderer.Pretty.renderMarkup
non <i> complete </i> ly
which will be shown in the browser as
non complete ly
A possible workaround is to encapsulate such content with H.unsafeLazyByteString . HR.renderHtml, but this doesn't feel safe nor elegant.
H.unsafeLazyByteString . HR.renderHtml
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Something noncompletely unreasonable like
will give different results depending on which rendered is used:
Text.Blaze.Renderer.Text.renderMarkup
givesas intended.
Text.Blaze.Renderer.Pretty.renderMarkup
giveswhich will be shown in the browser as
A possible workaround is to encapsulate such content with
H.unsafeLazyByteString . HR.renderHtml
, but this doesn't feel safe nor elegant.The text was updated successfully, but these errors were encountered: