WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WORKSFORME
141483
Web Inspector: console.log does not always work with filters enabled
https://bugs.webkit.org/show_bug.cgi?id=141483
Summary
Web Inspector: console.log does not always work with filters enabled
Brian Burg
Reported
2015-02-11 12:55:26 PST
Steps to reproduce: 1. Open the console 2. Run the following
> var a = Symbol("foo") > console.log(a) > console.log(a)
The first log of 'a' will not log anything and add 'undefined' as a new console result. The second will correctly add Symbol("a") to the console.
Attachments
[Animated GIF] Current behavior
(86.16 KB, image/gif)
2016-06-10 12:09 PDT
,
Nikita Vasilyev
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2015-02-11 12:55:46 PST
<
rdar://problem/19801162
>
Joseph Pecoraro
Comment 2
2015-02-11 14:00:16 PST
This is working correctly for me. Can you show me what you see, and what you would expect? Note: var x = 1; will cause undefined.
Brian Burg
Comment 3
2015-02-11 14:53:18 PST
Missing repro step: Turn on the "Error" option in the console filter bar. It works fine without a filter toggled.
Joseph Pecoraro
Comment 4
2015-02-12 18:26:14 PST
Not specific to Symbol. Can reproduce equally well with a string.
Nikita Vasilyev
Comment 5
2016-06-10 12:09:16 PDT
Created
attachment 281027
[details]
[Animated GIF] Current behavior Looks like "works as expected" to me.
Blaze Burg
Comment 6
2016-06-10 14:07:22 PDT
Agree, looks fixed.
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