Andreas

Thank you @pcgilday, this is great. Works like a charm, even `height: 1px;` 🤦 To avoid any unexpected issues with other browsers I would limit this to IE10 and 11...

@devongovett @mischnic Is there any update on this? We observe high memory consumption too in contrast to parcel 1.

I have the exact same problem. Unfortunately query terms which are even an exact match are rated lower that partial matches. E.g.: you have a data set off `[foo, foobar]`...

All tests pass: > 1..567 ># tests 567 ># pass 567 ># ok

@yoshuawuyts @kristoferjoseph @bcomnes May I asked you to look into this as soon as you have some free time? I'm happy to get your feedback:)

That previous comment is incorrect. @AutoSponge does not understand the flow of program execution during runtime and he is trolling my reputation.

@yoshuawuyts Thanks for your quick and very friendly answer. Btw the [main contributor of `morphdom`](https://github.com/patrick-steele-idem/morphdom/graphs/contributors) is @patrick-steele-idem

I opened my debugger and tracked it down, it seems to be caused by setting namespaced attributes without it's namespace, but rather by it's local name (it works in chrome...

Very interesting the DOM spec of `getAttributeNS` and `setAttributeNS` seems to be irritating. https://dom.spec.whatwg.org/#dom-element-getattributens > `getAttributeNS(namespace, localName)` > https://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-localname > A local name is the local part of a qualified...

I have just raised the same issue for morphdom https://github.com/patrick-steele-idem/morphdom/issues/124