WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
143545
Web Inspector: LogContentView should use higher level objects
https://bugs.webkit.org/show_bug.cgi?id=143545
Summary
Web Inspector: LogContentView should use higher level objects
Joseph Pecoraro
Reported
2015-04-08 17:58:49 PDT
* SUMMARY LogContentView should use higher level objects. Currently it searches and modifies elements directly, it should be dealing with View / Model objects at a higher level where possible.
Attachments
Add attachment
proposed patch, testcase, etc.
Nikita Vasilyev
Comment 1
2015-05-18 20:48:59 PDT
I was looking at "Web Inspector: Right/Left arrow no longer works in console to expand/collapse ObjectTrees" (
https://bugs.webkit.org/show_bug.cgi?id=141949
). To fix that bug I need to call ConsoleMessageView#collapse/expand from LogContentView. Currently, the only way to do it, AFAIK, is via `__messageView`: // FIXME: <
https://webkit.org/b/143545
> Web Inspector: LogContentView should use higher level objects this._element.__message = this._message; this._element.__messageView = this;
https://github.com/WebKit/webkit/blob/d722fe09e441157f1075c342ecf4d2fa7a57c24b/Source/WebInspectorUI/UserInterface/Views/ConsoleMessageView.js#L44-L46
Could you elaborate on "higher level objects"? How do you envision that?
Joseph Pecoraro
Comment 2
2015-05-18 21:17:35 PDT
> Could you elaborate on "higher level objects"? How do you envision that?
Our WebInspector View/Model objects, instead of DOM elements. Take TreeOutlines / TreeElements for instance. When working with TreeOutlines clients never dig into the DOM nodes querying DOM classes, it uses APIs that deal with use the higher level TreeOutline/TreeElements classes directly. In fact it may be wrong to go directly to DOM elements if for instance the "TreeElement" is "hidden" and querying to get the DOM element directly fails to respect that state.
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