Using Qute asHtmlAttributes is escaping the quotes in the output

[ia3andy]

Describe the bug

Using Qute asHtmlAttributes is escaping the quotes in the output:

<form action="{it}" method="{method ?: 'POST'}" {_args.skip('method', 'it').asHtmlAttributes}>
 {#authenticityToken/}
 {nested-content}
</form>

The workaround is to use: asHtmlAttributes.safe

Expected behavior

<form action="/HtmxApp/save/6" method="POST" hx-put="/HtmxApp/save/6" hx-swap="&quot;outerHTML&quot;" hx-target="this">

I believe the value (inside the quote) should be escaped

Actual behavior

<form action="/HtmxApp/save/6" method="POST" hx-put="&quot;/HtmxApp/save/6&quot;" hx-swap="&quot;outerHTML&quot;" hx-target="&quot;this&quot;"
">

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

3.6.5

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @mkouba (qute)

[mkouba]

The is straightforward, except that we must change the return type of the UserTagSectionHelper.Arguments.asHtmlAttributes() method from String to RawString. As a consequence, a user will need to use {_args.asHtmlAttributes.value} to access the String methods... which I believe is not a big deal.

[ia3andy]

@mkouba you need to update the doc

[mkouba]

Oh yes, we could mention that the values are always escaped but other than that the docs is IMO ok.

[ia3andy]

Oh yes, we could mention that the values are always escaped but other than that the docs is IMO ok.

@mkouba I mean for the {_args.asHtmlAttributes.value}. See https://quarkus.io/guides/qute-reference#arguments

[mkouba]

Oh yes, we could mention that the values are always escaped but other than that the docs is IMO ok.

@mkouba I mean for the {_args.asHtmlAttributes.value}. See https://quarkus.io/guides/qute-reference#arguments

Well, I think that 99% of users will never need {_args.asHtmlAttributes.value} but it wouldn't hurt to be more specific.

[ia3andy]

@mkouba so _args.asHtmlAttributes actually works as it is? I just misunderstood what you mean before by "to use it as a String", if that's the case, you can ignore my comment :)

[mkouba]

@mkouba so _args.asHtmlAttributes actually works as it is? I just misunderstood what you mean before by "to use it as a String", if that's the case, you can ignore my comment :)

Yes, it does. But you get a RawString instead. So for example {_args.asHtmlAttributes.toUpperCase} would not work but it used to work before... (now you would need to use {_args.asHtmlAttributes.value.toUpperCase})