Bug 167110

Summary: Web Inspector: Timelines tab is unusable when inspector is docked bottom
Product: WebKit Reporter: Devin Rousso <hi>
Component: Web InspectorAssignee: Razvan Caliman <rcaliman>
Status: NEW    
Severity: Normal CC: bburg, inspector-bugzilla-changes, mattbaker, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Attachments:
Description Flags
[Image] Screenshot of Issue none

Devin Rousso
Reported 2017-01-16 21:15:19 PST
Created attachment 299018 [details] [Image] Screenshot of Issue It looks like the various "categories" of the timeline graph area are set with a fixed height, which take up all the vertical space. Also, since scrolling is redirected to changing the zoom of the timeframe, it is not possible to scroll past the graph area.
Attachments
[Image] Screenshot of Issue (519.00 KB, image/png)
2017-01-16 21:15 PST, Devin Rousso 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Blaze Burg
Comment 1 2017-01-17 09:43:51 PST
It would be great if the timeline overviews were responsive, or at least had a "big" and "small" version. I'm not sure how we could change the scrolling model to avoid this issue. The workaround, of course, would be to turn off some timelines, but this is not great.
Radar WebKit Bug Importer
Comment 2 2017-01-17 09:44:13 PST
<rdar://problem/30054421>
Matt Baker
Comment 3 2017-01-17 11:47:08 PST
(In reply to comment #1) > It would be great if the timeline overviews were responsive, or at least had > a "big" and "small" version. I'm not sure how we could change the scrolling > model to avoid this issue. The workaround, of course, would be to turn off > some timelines, but this is not great. We could have small versions of all timelines by default, and possibly include a disclosure triangle if a larger/details view is available (Memory). Instruments does something similar.
Razvan Caliman
Comment 4 2024-02-13 15:26:49 PST
Pull request: https://github.com/WebKit/WebKit/pull/24380
Note You need to log in before you can comment on or make changes to this bug.