RESOLVED FIXED 151941
Wide tables should be scrollable on narrow mobile screens
https://bugs.webkit.org/show_bug.cgi?id=151941
Summary Wide tables should be scrollable on narrow mobile screens
Jon Davis
Reported 2015-12-07 06:41:00 PST
Currently tables with content that cannot be wrapped (Wide images) are not scrollable on narrow mobile screens. It makes it impossible to see all of the content.
Attachments
Patch (2.67 KB, patch)
2015-12-07 14:53 PST, Jon Davis
no flags
Patch (3.41 KB, patch)
2015-12-08 10:27 PST, Jon Davis
no flags
Patch (3.39 KB, patch)
2015-12-08 16:43 PST, Jon Davis
no flags
Jon Davis
Comment 1 2015-12-07 14:53:00 PST
Timothy Hatcher
Comment 2 2015-12-07 15:41:57 PST
Comment on attachment 266815 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=266815&action=review > Websites/webkit.org/wp-content/themes/webkit/scripts/global.js:100 > + var table = tables[i].outerHTML; > + var wrappedTable = "<div class=\"scrollable\"><div class=\"scrollable-padding\">" + table + "</div></div>"; > + tables[i].outerHTML = wrappedTable; Should do this without using outerHTML. You can make the divs with DOM operations and move the table element inside it, etc. That will avoid involving the parser, and security issues that innerHTML/outerHTML invites.
Jon Davis
Comment 3 2015-12-08 10:27:39 PST
Timothy Hatcher
Comment 4 2015-12-08 10:46:07 PST
Comment on attachment 266906 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=266906&action=review > Websites/webkit.org/wp-content/themes/webkit/scripts/global.js:105 > + paddingDiv.classList.add('scrollable-padding'); This could be done earlier, next to the scrollableDiv.classList.add.
Jon Davis
Comment 5 2015-12-08 16:43:54 PST
WebKit Commit Bot
Comment 6 2015-12-08 20:15:29 PST
Comment on attachment 266954 [details] Patch Clearing flags on attachment: 266954 Committed r193808: <http://trac.webkit.org/changeset/193808>
WebKit Commit Bot
Comment 7 2015-12-08 20:15:32 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.