WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
Bug 39428
Web Inspector: On-hover evaluation does not respect complex expressions.
https://bugs.webkit.org/show_bug.cgi?id=39428
Summary
Web Inspector: On-hover evaluation does not respect complex expressions.
Gianni Chiappetta
Reported
2010-05-20 08:33:29 PDT
Created
attachment 56597
[details]
Web Inspector Screenshot The Web Inspector seems to be reporting incorrect data, either in the object inspector on a breakpoint or in a watch expression. This may even be a JavaScriptCore bug? It's reproducible 100% of the time for me. Anyway, check out the attached screenshot, note the watch expression.
Attachments
Web Inspector Screenshot
(148.09 KB, image/png)
2010-05-20 08:33 PDT
,
Gianni Chiappetta
no flags
Details
Another screenshot.
(54.08 KB, image/png)
2010-05-20 09:14 PDT
,
Gianni Chiappetta
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Gianni Chiappetta
Comment 1
2010-05-20 09:14:36 PDT
Created
attachment 56599
[details]
Another screenshot. Another screenshot. Check the value of `lol` on the right.
Pavel Feldman
Comment 2
2010-05-20 09:18:27 PDT
We are evaluating only the last token ("length") which is wrong. We should add more stop symbols and disable on-hover for suffixes with prefixes containing illegal characters.
Joseph Pecoraro
Comment 3
2010-05-20 09:39:23 PDT
Yes. And the value you're seeing, 0, is likely window.length, the number of "child browsing contexts", which I would expect to be 0:
http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#dom-length
Brian Burg
Comment 4
2014-12-12 14:07:26 PST
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests. Please file a new bug (
https://www.webkit.org/new-inspector-bug
) if the bug/feature/issue is still relevant to WebKit trunk.
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