Replies: 3 comments
-
I just now filed this as an issue in case the protection should be added to the private _commitText() method. |
Beta Was this translation helpful? Give feedback.
-
And this is the generated HTML of the card. The exception occurs when value changes for the text within the <div class="attr-value" id="..."> {valueText}</div> elements as well at the three div tags w/ids: "card-timestamp", "os-rls-name", and "daemon-upd-flg" have occurred. |
Beta Was this translation helpful? Give feedback.
-
For the record, I found what was exciting lit to be generating the exception. I found code that was changing {text} within the <div id="idvalue">{text}<div> but incorrectly from within the updated() method. while render() had already placed this text correctly. After removing the offending code from updated() the exception is no longer generated! |
Beta Was this translation helpful? Give feedback.
-
I'm guessing that it is my HTML construction that is causing this:
Expanding the exception shows this (in Chrome Browser - developer tools):
This is for working Lovelace cards in Home Assistant (well, working until the exception!):
Symptoms: These cards, once the exception occurs, just stop updating many of the values. If the page is reloaded, the update once again until the next exception.
There are similar, not the same, issues in the lit repo. I've not filed this yet, I would suspect that I should file if lit-html should at least defend against this.
I am eager to find the cause and fix this as I have many users of this card. What's the best way to get help identifying the cause even if it's my HTML/CSS construction?
Thanks in advance for your help/guidance!
Stephen (Github: Ironsheep)
FYI- I'm building/running against:
"lit": "^2.6.1",
"lit-html": "2.6.1",
"lit-element": "3.2.2",
"@lit/reactive-element": "1.6.1"
Beta Was this translation helpful? Give feedback.
All reactions