RESOLVED FIXED 56912
Web Inspector: move node searching and node highlight related methods from InspectorAgent to DOMAgent
https://bugs.webkit.org/show_bug.cgi?id=56912
Summary Web Inspector: move node searching and node highlight related methods from In...
Ilya Tikhonovsky
Reported 2011-03-23 03:18:22 PDT
%subj%
Attachments
Patch (62.12 KB, patch)
2011-03-23 03:23 PDT, Ilya Tikhonovsky
no flags
Patch (62.00 KB, patch)
2011-03-23 03:43 PDT, Ilya Tikhonovsky
pfeldman: review-
Ilya Tikhonovsky
Comment 1 2011-03-23 03:23:57 PDT
WebKit Review Bot
Comment 2 2011-03-23 03:29:41 PDT
Ilya Tikhonovsky
Comment 3 2011-03-23 03:43:52 PDT
Build Bot
Comment 4 2011-03-23 04:11:34 PDT
Yury Semikhatsky
Comment 5 2011-03-23 05:43:03 PDT
Comment on attachment 86597 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=86597&action=review > Source/WebCore/inspector/DOMNodeHighlighter.cpp:216 > +} // unnamed namespace unnamed -> anonymous or just // namespace ? > Source/WebCore/inspector/InspectorAgent.cpp:127 > + m_instrumentingAgents->setInspectorAgent(this); There should be symmetric call reseting InspectorAgent. > Source/WebCore/inspector/InspectorDOMAgent.cpp:100 > +static const char searchingForNode[] = "searchingForNode"; Is it still in use? > Source/WebCore/inspector/InspectorDOMAgent.cpp:917 > +bool InspectorDOMAgent::searchingForNodeInPage() const No need to expose this through a public method, just use m_searchingForNode directly in this class. > Source/WebCore/inspector/InspectorInstrumentation.cpp:161 > + if (!inspectorAgent->enabled()) You wouldn't need this check if you used instrumentingAgents()->inspectorDOMAgent(), please fix.
Ilya Tikhonovsky
Comment 6 2011-03-23 06:23:25 PDT
Pavel Feldman
Comment 7 2011-03-28 23:04:31 PDT
Comment on attachment 86597 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=86597&action=review This is r- for several reasons, I wonder how it ended up with r+. > Source/WebCore/inspector/DOMNodeHighlighter.h:37 > +namespace DOMNodeHighlighter { Why custom namespace? What is wrong with using WebCore? This is not standard approach afaik. > Source/WebCore/inspector/DOMNodeHighlighter.h:39 > +void DrawNodeHighlight(GraphicsContext&, Node*); Methods in WebCore start with lower case. > Source/WebCore/inspector/Inspector.json:676 > + "name": "setSearchingForNode", DOM domain is documented, you should not introduce commands that are not documented into it.
Pavel Feldman
Comment 8 2011-03-28 23:07:01 PDT
Comment on attachment 86597 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=86597&action=review > Source/WebCore/inspector/Inspector.json:696 > + { "name": "frameId", "type": "string" } Hm. DOM domain does not operate frameIds. This is the term from a different "Network" domain. This command does not belong here.
Pavel Feldman
Comment 9 2011-03-28 23:18:51 PDT
Comment on attachment 86597 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=86597&action=review > Source/WebCore/inspector/InspectorDOMAgent.cpp:65 > +#include "InspectorAgent.h" 1) I think it is very wrong to add a dependency from InspectorDOMAgent to InspectorResourceAgent. 2) I also think it is very wrong to put dependency from any agent to InspectorAgent I think reasons above are sufficient to roll this change out.
Pavel Feldman
Comment 10 2011-03-28 23:23:07 PDT
(In reply to comment #9) > (From update of attachment 86597 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=86597&action=review > > > Source/WebCore/inspector/InspectorDOMAgent.cpp:65 > > +#include "InspectorAgent.h" > > 1) I think it is very wrong to add a dependency from InspectorDOMAgent to InspectorResourceAgent. read as of InspectorDOMAgent from InspectorResourceAgent > 2) I also think it is very wrong to put dependency from any agent to InspectorAgent > read as of any agent from InspectorAgent > I think reasons above are sufficient to roll this change out. Morning brains confused, blood boils :)
Note You need to log in before you can comment on or make changes to this bug.