You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2019. It is now read-only.
I'm usually working on my small 13.3" laptop. The website looks a bit problematic at that screen size. To recreate - just resize your browser window. The feed on the right then hides the rightmost columns.
From my point of view, the solution would be to decide which columns are least important, and hide them first as the table width shrinks. And then make it possible to choose which columns to show.
Currently I'm not sure if the website can handle any new columns - I expect that in the future there will be more.
Another addition would be to make each row clickable (or something similar), and when a user clicks on it, the row would expand downwards and show all gem data, and maybe some additional data for which now there would be enough space.
Pjotr, am I making any sense? Was the width of the table/page ever an issue for you?
The text was updated successfully, but these errors were encountered:
I'm usually working on my small 13.3" laptop. The website looks a bit problematic at that screen size. To recreate - just resize your browser window. The feed on the right then hides the rightmost columns.
From my point of view, the solution would be to decide which columns are least important, and hide them first as the table width shrinks. And then make it possible to choose which columns to show.
Currently I'm not sure if the website can handle any new columns - I expect that in the future there will be more.
Another addition would be to make each row clickable (or something similar), and when a user clicks on it, the row would expand downwards and show all gem data, and maybe some additional data for which now there would be enough space.
Pjotr, am I making any sense? Was the width of the table/page ever an issue for you?
The text was updated successfully, but these errors were encountered: