Bug 191622

Summary: Web Inspector: Remove unused DataGrid and TreeOutline code
Product: WebKit Reporter: Matt Baker <mattbaker>
Component: Web InspectorAssignee: Matt Baker <mattbaker>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, hi, inspector-bugzilla-changes, webkit-bug-importer
Priority: P3 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch
none
Patch
none
Patch for landing none

Matt Baker
Reported 2018-11-13 20:33:41 PST
- DOMTreeOutline property `_selectEnabled` duplicates `_selectable` in the base class - TreeOutline methods `removeChildrenRecursive` and `reattachIfIndexChanged` are no longer used
Attachments
Patch (7.01 KB, patch)
2018-11-13 20:35 PST, Matt Baker
no flags
Patch (14.75 KB, patch)
2018-11-14 15:07 PST, Matt Baker
no flags
Patch for landing (14.72 KB, patch)
2018-11-28 11:18 PST, Matt Baker
no flags
Radar WebKit Bug Importer
Comment 1 2018-11-13 20:33:56 PST
Matt Baker
Comment 2 2018-11-13 20:35:27 PST
Devin Rousso
Comment 3 2018-11-14 09:46:39 PST
Comment on attachment 354761 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=354761&action=review Looks good. I'd like to test this on my computer to make sure we aren't missing any edge-cases where `selectable` is `false` while `selectEnabled` is true (it looks like this may be the case when the "Show All Nodes" button is added). > Source/WebInspectorUI/UserInterface/Views/DOMTreeOutline.js:35 > + super(null, selectable); I just looked around, and it seems that `WI.ErrorObjectView` is the only user of `WI.TreeOutline` that specifies an `element`. Perhaps you could refactor that view and `WI.TreeOutline` as well to remove that parameter. > Source/WebInspectorUI/UserInterface/Views/TreeElement.js:-65 > - removeChildrenRecursive() { return WI.TreeOutline.prototype.removeChildrenRecursive.apply(this, arguments); } It looks like `WI.DataGrid` has a similar function that isn't used :P
Matt Baker
Comment 4 2018-11-14 15:07:25 PST
Devin Rousso
Comment 5 2018-11-26 10:39:53 PST
Comment on attachment 354857 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=354857&action=review r=me > Source/WebInspectorUI/UserInterface/Views/ErrorObjectView.css:61 > + -webkit-padding-start: 16px Did you test this in RTL? Is this the correct behavior? > Source/WebInspectorUI/UserInterface/Views/ErrorObjectView.js:2 > + * Copyright (C) 2015-2018 Apple Inc. All rights reserved. I'm not sure what our "style" is on this, but I've heard both that "it should only be the most recent year" and "it should be every year it was significantly modified". Maybe confirm which is preferred?
Matt Baker
Comment 6 2018-11-28 11:18:03 PST
Comment on attachment 354857 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=354857&action=review >> Source/WebInspectorUI/UserInterface/Views/ErrorObjectView.js:2 >> + * Copyright (C) 2015-2018 Apple Inc. All rights reserved. > > I'm not sure what our "style" is on this, but I've heard both that "it should only be the most recent year" and "it should be every year it was significantly modified". Maybe confirm which is preferred? I'll use the more conservative "2015, 2018".
Matt Baker
Comment 7 2018-11-28 11:18:32 PST
Created attachment 355894 [details] Patch for landing
Joseph Pecoraro
Comment 8 2018-11-28 11:23:07 PST
> > I'm not sure what our "style" is on this, but I've heard both that "it should only be the most recent year" and "it should be every year it was significantly modified". Maybe confirm which is preferred? > > I'll use the more conservative "2015, 2018". I have seen us moving to ranges more and more: "2015-2018". The source repository has complete history of the edits of the file so exact years is cumbersome and ultimately unnecessary.
WebKit Commit Bot
Comment 9 2018-11-28 11:47:09 PST
Comment on attachment 355894 [details] Patch for landing Clearing flags on attachment: 355894 Committed r238626: <https://trac.webkit.org/changeset/238626>
WebKit Commit Bot
Comment 10 2018-11-28 11:47:10 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.