Describe the bug
I wanted to skip through all the pages (38 pages in total - 50 items shown at a time) in the test run table, the first 1-15 pages are ok whilst I'm hammering the "next" button, but once it gets a bit beyond that, the table starts jumping around, until eventually the next button goes out of the viewport and I have to scroll to see it again.
I've hit the > button successfully 17 times with no issue:
it then jolted down a little bit going to the 18th page, which mean I nearly accidentally hit a test run row:
Then I clicked > again, and the whole table jolted downwards, the > is now off the screen:
Expected behavior
However I resize my window, the datatable should draw itself to fit inside it. It position should then be fixed within the confines of that area......it should probably have a minimum size it can be, because it would look awful otherwise (in which case, the view should extend out of the browser, causing the browser to show scrollbars).....but as you can see from my screenshots, this wasn't a probable here as the window was sized more than enough to house everything.
Instead there seems to be a lot of items conflicting with the sizing, causing odd behaviour.
Describe the bug
I wanted to skip through all the pages (38 pages in total - 50 items shown at a time) in the test run table, the first 1-15 pages are ok whilst I'm hammering the "next" button, but once it gets a bit beyond that, the table starts jumping around, until eventually the next button goes out of the viewport and I have to scroll to see it again.
I've hit the > button successfully 17 times with no issue:
it then jolted down a little bit going to the 18th page, which mean I nearly accidentally hit a test run row:
Then I clicked > again, and the whole table jolted downwards, the > is now off the screen:
Expected behavior
However I resize my window, the datatable should draw itself to fit inside it. It position should then be fixed within the confines of that area......it should probably have a minimum size it can be, because it would look awful otherwise (in which case, the view should extend out of the browser, causing the browser to show scrollbars).....but as you can see from my screenshots, this wasn't a probable here as the window was sized more than enough to house everything.
Instead there seems to be a lot of items conflicting with the sizing, causing odd behaviour.