On smaller screens the feature matrices overflow to the right. This is both hard to browse and causes the "Fork me on GitHub" ribbon to sometimes get detached from one side. A good solution would be to make horizontal scrolling of the matrices independent from the rest of the site. To make it work well, the leftmost (extension name) column should not scroll horizontally and instead always be located on the left, while all cells that fit on the screen are shown next to it (with the rest hiding on either side).
In the same vain, if the headers could stick to the top edge of the screen (when a user is scrolling down) a related problem would also be solved. (Long matrices do not fit on the screen vertically. Thus their vendor/driver information is often not visible and the cells become hard to browse.)
Lastly, it would be extra nice if all matrices within one API family moved together when scrolled horizontally.
Oh, and while I marked this as a feature request, there is a non-zero chance I will try implementing it myself. (Can't promise it will be soon tho…)
On smaller screens the feature matrices overflow to the right. This is both hard to browse and causes the "Fork me on GitHub" ribbon to sometimes get detached from one side. A good solution would be to make horizontal scrolling of the matrices independent from the rest of the site. To make it work well, the leftmost (extension name) column should not scroll horizontally and instead always be located on the left, while all cells that fit on the screen are shown next to it (with the rest hiding on either side).
In the same vain, if the headers could stick to the top edge of the screen (when a user is scrolling down) a related problem would also be solved. (Long matrices do not fit on the screen vertically. Thus their vendor/driver information is often not visible and the cells become hard to browse.)
Lastly, it would be extra nice if all matrices within one API family moved together when scrolled horizontally.
Oh, and while I marked this as a feature request, there is a non-zero chance I will try implementing it myself. (Can't promise it will be soon tho…)