WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
147348
Web Inspector: Type profiler return types aren't showing up
https://bugs.webkit.org/show_bug.cgi?id=147348
Summary
Web Inspector: Type profiler return types aren't showing up
Saam Barati
Reported
2015-07-27 19:09:07 PDT
The JSC patch that changed text offsets to start from the open paren of the parameter list instead of the open brace of the function body broke the type profiler's protocol.
Attachments
patch
(5.54 KB, patch)
2015-07-27 19:16 PDT
,
Saam Barati
joepeck
: review+
joepeck
: commit-queue-
Details
Formatted Diff
Diff
patch
(6.73 KB, patch)
2015-08-17 13:40 PDT
,
Saam Barati
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Saam Barati
Comment 1
2015-07-27 19:16:16 PDT
Created
attachment 257626
[details]
patch
Joseph Pecoraro
Comment 2
2015-07-28 12:30:16 PDT
Comment on
attachment 257626
[details]
patch View in context:
https://bugs.webkit.org/attachment.cgi?id=257626&action=review
> Source/WebInspectorUI/UserInterface/Models/ScriptSyntaxTree.js:179 > - divot: node.body.range[0] > + divot: node.isGetterOrSetter ? node.getterOrSetterRange[0] : node.range[0] // "f" in function, "s" in set, "g" in get, first letter in any method name for classes.
Is this compatible with iOS 9 (a soon to be considered Legacy backend that wouldn't have had your recent backend changes). If not, maybe we should make this a function so that it would be easier to read. Something like: function functionReturnDivot(node) { // COMPATIBILITY (iOS 9): Legacy Backends something something something. // FIXME: Need a better way to determine backend versions. Using DOM.pseudoElement because that was added after iOS 9. if (!DOMAgent.hasEvent("pseudoElementAdded")) return node.body.range[0]; // "f" in function, "s" in set, "g" in get, first letter in any method name for classes. return node.isGetterOrSetter ? node.getterOrSetterRange[0] : node.range[0]; } Would be good to have a frontend test for this so it won't regress again in the future. But I won't make you write one now.
Saam Barati
Comment 3
2015-08-17 13:40:29 PDT
Created
attachment 259178
[details]
patch
Matt Baker
Comment 4
2015-08-17 14:33:17 PDT
Comment on
attachment 259178
[details]
patch View in context:
https://bugs.webkit.org/attachment.cgi?id=259178&action=review
> Source/WebInspectorUI/ChangeLog:8 > +
Bug #145995
changed the starting offset of a function to
Nit: We typically use the form <
https://webkit.org/b/xxxxxx
> when referencing bugs in the WebInspector change log.
Blaze Burg
Comment 5
2015-08-17 14:38:27 PDT
Comment on
attachment 259178
[details]
patch r=me
WebKit Commit Bot
Comment 6
2015-08-17 15:57:31 PDT
Comment on
attachment 259178
[details]
patch Clearing flags on attachment: 259178 Committed
r188549
: <
http://trac.webkit.org/changeset/188549
>
WebKit Commit Bot
Comment 7
2015-08-17 15:57:35 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