-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
iframe
inserted into "dynamic" table header
#10597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please provide a proper reproduction for the issue as instructed by the issue template:
A single code snippet with missing imports does not meet the above criteria. Dimension bindings may be one possible reason for your issue. |
Here's a repo to reproduce the bug. Because I needed the It is TRUE that it is caused by the dimension binding. Because I needed the I originally had a temporary solution by using |
This should belong to Svelte repo, not SvelteKit specific. However, the reason are size bindings they use iframe trick to react to resize because they're created before ResizeObserver was introduced You can use new ones that utilize ResizeObserver under the hood and don't need the iframe, check out here |
Yeah ResizeObserver bindings would be the way to do this now. If you absolutely need to use the old way for legacy reasons, you can maybe bind to dimension updates on a hidden element placed inside the table cell. Likely not much we can do here otherwise. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
I made a dynamic table which columns are displayed upon user preference, using stores.
When the user choses to display the last column a weird
<iframe>
is inserted in the<thead>
row elements before the newly displayed<th>
element. And this, of course, breaks the table flow.Reproduction
Make a table like the following tree:
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
I get the following
iframe
inserted before the last column:I made sure all browser plugins are disabled but still got the same output.
The text was updated successfully, but these errors were encountered: