Alexander Prinzhorn

> I have added test unit with example which you mentioned in `src/compiler/parse/utils/__test__.ts` Thanks, I was mostly referring to testing attributes specifically. All tests are testing the entities inside HTML...

> I have found that the reason of `&amp` doesn't decode in `background-image: url(https://example.com/path?lib=test&amp=value);` is only in `&amp=xxx` structure. I assume there are certain characters that cannot follow an incomplete...

https://html.spec.whatwg.org/multipage/parsing.html#named-character-reference-state > If the character reference was [consumed as part of an attribute](https://html.spec.whatwg.org/multipage/parsing.html#charref-in-attribute), and the last character matched is not a U+003B SEMICOLON character (;), and the [next input character](https://html.spec.whatwg.org/multipage/parsing.html#next-input-character)...

> As it says, I think about we shouldn't no encode the html entity which not end withs ; and next character is =, number or alphabet. _Maybe_ we should...

I have one question regarding the general test setup, otherwise this lgtm. There are test files like `test/runtime/samples/html-entities/main.svelte` and the expected value in `_config.js`. I assume this is generated using...

@baseballyama thanks, that's precisely what I asked

This is basically https://github.com/sveltejs/svelte/issues/7082, correct?

I'm not sure this was ever supposed to work the way you're using it. If you remove `test` from your initial object it works as expected (`const functions = {}`)....

I didn't know `const` was implemented at all, let alone with those semantics. I was hoping https://github.com/sveltejs/svelte/issues/5572 would come some day, which behaves exactly the opposite from what you've described...

> Here is one of the ways to use such a `bind:` Here's what I would use to do the exact same thing: https://svelte.dev/repl/32a6b997d4b54b90adf0eb2efbd650f3?version=3.54.0 You're basically extracting the two functions...