View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0022132||mantisbt||ui||public||2017-01-06 19:09||2020-08-09 19:20|
|Priority||normal||Severity||major||Reproducibility||have not tried|
|Summary||0022132: Some tables gets off screen and cant be scrolled conveniently|
The same issue described by 0021817 affects view_all_bug_page, where if a number of columns are selected to be shown, the content of the issues list is partly hidden and cant be scrolled conveniently.
|related to||0027114||feedback||syncguru||Long unbreakable text does not auto wrap in bug details page|
|has duplicate||0021817||new||adm_config_report.php configuration table overflows screen and is not usable|
|has duplicate||0021702||closed||cproensa||Horizontal scroll bar not shown|
|related to||0021818||new||Forms and tables are not fitted to viewport sizes, eg: mobile browsers|
|related to||0023335||new||"Update issue" layout can be too wide|
|related to||0025166||new||Debug log in screen is easily overflowed due to sql queries|
There are some js solutions. For example: https://github.com/Amphiluke/floating-scroll
I have this branch as a proof of concept:
As we use a library for the View Issues table, we should look for the following feature:
The above is what I ideally would like to see for this control. How much of it is out of the box vs. something that we have to build on top of a control, I don't know. @syncguru may have better experience in this space to comment.
A workaround is to use the left/right cursor keys.
What you are describing is something in the line of DataTables library (as an example)
Note that the issue here does not relate to how the table is built or behaved.
Since the new UI, table containers are lmited to maximum screen width, but contained data can be wider, this issue is relevant.
This is susceptible to happen on any table div, so my suggestion atm is to implement this feature in all responsive-table divs.
That's not a satisfactory UX solution. As a workaround may work, but i couldn't instruct the users to use that.
Maybe 0027114 will address this ?