Sander
Sander
@pastelsky I don't think it is related to my changes, but sure
SvelteKit reached version 1.0.0 today🚀 @pooledge I can dig into it if you could share a small repo with the issue?
> Oh, didn't you ask for a repo, did you? > > [Minimum repro @ GH](https://github.com/pooledge/playwright-19411). > > > > Thanks! Found out how to download it, thanks anyway!
Hi @oliver-freudrich-packwise, the `update()` works indeed only on framework components at the moment. Any reason why you want to update native HTML elements?
@mxschmitt yeah, agree. Think it's possible to add but if a native HTML element is being updated you probably did it by mistake and don't want that in the first...
@oliver-freudrich-packwise Thank you for clarifying. Throwing a custom error when updating a native HTML element would still be useful. That's one thing that should be fixed. It seems that updating...
Hey @yury-s, hopefully next release. I'm a bit buried in work ATM.
Seems like a duplicate ticket: https://github.com/microsoft/playwright/issues/14511
The `svelte/internal` module is used for [testing slots](https://github.com/microsoft/playwright/blob/a6827772a5f210ca5b760586e0b685ef0054cfbb/tests/components/ct-svelte-vite/tests/slots.spec.ts#L5-L12), but it appears that `slots` are replaced by snippets/render tags in Svelte 5. There are more breaking changes: https://svelte-5-preview.vercel.app/docs/breaking-changes so i think...
@pavelfeldman any chance this one could passthrough?