#Weird glitch with big table
13 messages · Page 1 of 1 (latest)
I have similar issues in Safari but I am on 6.5 latest (top half of a story is not rendered unless something happens on the screen) - it does not happen in any other browser though
wow yeah that does look strange..
1 is it both in dev and prod?
2 does it happen in all browsers?
3 ...on all computers?
4 Do you know how many DOM elements are being rendered in the failing state?
It looks like the browser is completely choking on rendering, the preview is in an iframe so it can't have any effect on the manager UI.
Will try to give you more details later today @dire jewel but the thing is that in isolation it works as expected. Also I render only 96 rows of the table so not sure exactly what is going on, but will ping you with more details soon for the things you asked
@dire jewel attached a video, happens only in Chrome, Firefox and Safari as working smoothly. The weird part is that when I click the fullscreen mode the issue stops. Should I open a bug report to the repo? Wdyt?
Strange. Yeah a bug report is a good idea, so more people can see it and so we have a minimal reproduction.
But TBH I wouldn't get my hopes up for a fix soon, this sounds like native browser behaviour gone bad.
Not sure though why Chrome is behaving like this @dire jewel 🤔 Here is the compiled storybook: https://neo4j-table-v1-needle-feedback.surge.sh/?path=/story/tables-resizable-columns--resizable-columns
If you click Storybook's on top right Fullscreen and toggle you will see that something happens when the sidebar appears
Also first be sure to increase the entries in the table
oh wow, I see the exact same thing
for me, it happens already at 25 entries. EXCEPT if I resize the browser window to be really short, then it works for 25 and 50 as well.
Really weird indeed, not sure what is breaking but will try to create a reproduction repo next days to open it as an issue
Hmm I'm seeing a circular structure in the story context whenever I interact with any of them, I don't know if that is causing weird behavior. It could also be nothing at all, and totally in purpose. it's currentContext -> hooks -> currentContext ->...., does any of that ring a bell?
Are you doing something fancy with the context, globals, decorators, etc.?