-
Suggestion
-
Resolution: Won't Do
-
None
-
1
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
As of https://jira.atlassian.com/browse/CONF-23145, for large tables, a horizontal scrollbar appears at the bottom of the table.
This, in some cases affects usability greatly, since you have to scroll down to the bottom of the table to reach the scrollbar, then to get to the right side of the table, then back up to the top to see the contents of the field.
It would make sense to have this function to be optional, configurable on a per-table basis. Once implemented, it would be nice to have a default behavior configured on an instance/space basis, which then can be overridden on table-level.
- is related to
-
- Closed
- relates to
-
- Gathering Interest
[CONFSERVER-28225] Have entire page scroll horizontally instead of just tables
Gavin Maartens
added a comment - Issue https://jira.atlassian.com/browse/CONF-31476 refers...
As per the CSS workaround posted in the referred jira, is there a similar workaround for the current issue?
I've tried setting the table width to 100% with this CSS, but it does not work (I still get horizontal scrollbars)
".table
"
In my view, horizontal scrollbars are a massive readability fail. I'd like the issue fixed as per @Peter Binney's last comment, but I would settle for a workaround, if someone can provide one?
Thanks!
Gavin Maartens
added a comment - Issue https://jira.atlassian.com/browse/CONF-31476 refers...
As per the CSS workaround posted in the referred jira, is there a similar workaround for the current issue?
I've tried setting the table width to 100% with this CSS, but it does not work (I still get horizontal scrollbars)
".table
{table-layout: fixed; width: 100%}
"
In my view, horizontal scrollbars are a massive readability fail. I'd like the issue fixed as per @Peter Binney's last comment, but I would settle for a workaround, if someone can provide one?
Thanks! 
H K
added a comment - This looks like a duplicate of CONF-27557 . 
Peter Binney
added a comment - Hi John - this is nothing to do with the browser (we use, predominantly, IE8 but the problem exists on Firefox and Chrome inter alia).
It is (as you know) caused by the change in styling for tables (as your documentation team have found and, I gather, had to fix for themselves).
Yes, if you are a computer geek and can tell that there's text missing off to the right of the screen, you can right-arrow to get to it.
But most web page readers don't know this.
Also, if the table and screen size "fit" to one of the columns, there is no visual clue that there is more information to the right that you can't see (until you scroll down to the bottom of the table and see the horizontal scroll bar).
I appreciate that there's a trade-off. The new behaviour fixes the problem that a wide table on a page makes all flowed text as wide as that table, thus requiring horizontal scrolling to read that non-wide-table text.
This is why I suggest you have a control that allows the page author to decide how to handle wide tables (with the default being the way it used to work!).
Peter Binney
added a comment - Hi John - this is nothing to do with the browser (we use, predominantly, IE8 but the problem exists on Firefox and Chrome inter alia ).
It is (as you know) caused by the change in styling for tables (as your documentation team have found and, I gather, had to fix for themselves).
Yes, if you are a computer geek and can tell that there's text missing off to the right of the screen, you can right-arrow to get to it.
But most web page readers don't know this.
Also, if the table and screen size "fit" to one of the columns, there is no visual clue that there is more information to the right that you can't see (until you scroll down to the bottom of the table and see the horizontal scroll bar).
I appreciate that there's a trade-off. The new behaviour fixes the problem that a wide table on a page makes all flowed text as wide as that table, thus requiring horizontal scrolling to read that non-wide-table text.
This is why I suggest you have a control that allows the page author to decide how to handle wide tables (with the default being the way it used to work!).
Hi peter.binney@commerzbank.com, the behaviour is implemented the way you describe in 5.0, it was changed after beta-3. (It's not a customisation on http://confluence.atlassian.com)
Having said that, I'm not sure if it will stay that was as it causes some other issues.
What browser do you use, does it not allow you to click on the table and use the arrow keys to scroll?
Peter Binney
added a comment - Note that Atlassian's documentation team had to customise Confluence to make their pages readable!
See: https://support.atlassian.com/browse/CSP-96595
Peter Binney
added a comment - Note that Atlassian's documentation team had to customise Confluence to make their pages readable!
See: https://support.atlassian.com/browse/CSP-96595
Thank you for raising this suggestion.
We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our updated workflow for Suggestions
Cheers,
Confluence Product Management