So this would be horrible if 24.2 will go in the wild. I do not know to which one I have to send this problem? If this is the wrong place here - please give me address of pre-release bug reports.
Thank you!
This is UI error. There is <sp-label> element which should belong to spectrum components. And Svelte is trying to set slot property to value label so it would be I believe <sp-label slot="label">. It first checks for existence of that property in HTML node and since it exists it tries to set that value. Otherwise, it would add a new attribute. But the problem is that node.slot is readonly property a cannot be changed therefore it fails and UI rendering stops. So I believe before <sp-label> part of the spectrum built-in components was read and write before but now it was changed to read only.
I think reason could be the same… but just with a different element. You can try yourself. Turn on break on error in DevTools and reload plugin and check if the place is same and what are the variables.
yes maybe - but it has to be solved from Adobe anyway. Or do you see a workaround here?
now I made a downgrade to 24.1.1 already because it stops my work otherwise - will check out later.
We’re looking into this. Unfortunately, I don’t have a solution / more info for you yet, but rest assured that we are aware and are looking into this => stay tuned.
In my case it was only caused by the sp-label element. Provisionally, the following workaround has prevented the error. The appearance will be different, so new CSS will need to be added.
There is no ETA yet since it takes some time to find the cause / the best solution, but as soon as I get any news, I’ll notify you here.
Currently, we’re looking into ways to fix this in a hotfix update for Photoshop 24.2, but we’ll have to wait and see what’s possible. I expect to be able to give you better information mid-end next week.
We are able to root cause and fix the Svelte starter plugin issue but couldn’t replicate the similar stack with a sample Preact app using a simple HTML that has <sp-label slot='label'>{text}</sp-label>. Though your stack trace is very similar to the one reported by Imperator and most probably has the same root cause, we’d like to confirm that our fix addresses both frameworks. Would you be able to share a sample that we can use to replicate this internally?
