WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
142315
Web Inspector: REGRESSION (
r171645
): up/down key navigation of timeline sidebar tree elements is broken when scope bar filters are applied
https://bugs.webkit.org/show_bug.cgi?id=142315
Summary
Web Inspector: REGRESSION (r171645): up/down key navigation of timeline sideb...
Brian Burg
Reported
2015-03-04 17:31:15 PST
Steps to reproduce: 1. Populate some timelines data 2. Select the Layout timeline 3. Select a scope bar filter for a record type that is non-contiguous (usually, Styles Invalidated and Styles Recalculated are fine) 4. Click on a record tree element in sidebar 5. Keyboard up/down until it stops working (beeps) From my quick experiments, it appears that the sidebar content tree outline is rendered using the filtered tree elements, but pressing up/down keys tries to navigate to the next/previous unfiltered data grid node. If that node is filtered out, then nothing happens in response to key event (seems to eventually fire [NSResponder:noResponderFor] and beep.)
Attachments
[Patch] Proposed Fix
(5.78 KB, patch)
2015-06-09 15:47 PDT
,
Matt Baker
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2015-03-04 17:31:33 PST
<
rdar://problem/20048730
>
Matt Baker
Comment 2
2015-05-29 13:31:32 PDT
Caused by
http://trac.webkit.org/changeset/171645
. Looking over TreeOutline.js, the real problem seems to be with traverseNextTreeElement and traversePreviousTreeElement. The above revision changed the criteria for tree elements being considered revealed, causing the latent bug in element traversal to manifest.
Matt Baker
Comment 3
2015-06-09 15:47:31 PDT
Created
attachment 254609
[details]
[Patch] Proposed Fix
Timothy Hatcher
Comment 4
2015-06-11 07:48:56 PDT
Comment on
attachment 254609
[details]
[Patch] Proposed Fix View in context:
https://bugs.webkit.org/attachment.cgi?id=254609&action=review
> Source/WebInspectorUI/UserInterface/Views/TreeOutline.js:1039 > + var depthChange = 0;
Is this indent right?
Matt Baker
Comment 5
2015-06-15 17:25:31 PDT
(In reply to
comment #4
)
> Comment on
attachment 254609
[details]
> [Patch] Proposed Fix > > View in context: >
https://bugs.webkit.org/attachment.cgi?id=254609&action=review
> > > Source/WebInspectorUI/UserInterface/Views/TreeOutline.js:1039 > > + var depthChange = 0; > > Is this indent right?
Could you clarify?
Timothy Hatcher
Comment 6
2015-06-15 17:37:00 PDT
Comment on
attachment 254609
[details]
[Patch] Proposed Fix View in context:
https://bugs.webkit.org/attachment.cgi?id=254609&action=review
>>> Source/WebInspectorUI/UserInterface/Views/TreeOutline.js:1039 >>> + var depthChange = 0; >> >> Is this indent right? > > Could you clarify?
The patch on my phone looks like this like is a 4 spaces less than it should be. It could be the rendering or maybe there is a tab?
Matt Baker
Comment 7
2015-06-16 16:43:28 PDT
Comment on
attachment 254609
[details]
[Patch] Proposed Fix View in context:
https://bugs.webkit.org/attachment.cgi?id=254609&action=review
>>>> Source/WebInspectorUI/UserInterface/Views/TreeOutline.js:1039 >>>> + var depthChange = 0; >>> >>> Is this indent right? >> >> Could you clarify? > > The patch on my phone looks like this like is a 4 spaces less than it should be. It could be the rendering or maybe there is a tab?
Weird, it looks that way on my phone too. It looks correct on my laptop, and I confirmed that the indentation is identical to the line below it.
WebKit Commit Bot
Comment 8
2015-06-16 17:33:46 PDT
Comment on
attachment 254609
[details]
[Patch] Proposed Fix Clearing flags on attachment: 254609 Committed
r185629
: <
http://trac.webkit.org/changeset/185629
>
WebKit Commit Bot
Comment 9
2015-06-16 17:33:50 PDT
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.
Top of Page
Format For Printing
XML
Clone This Bug