Bug 141483 - Web Inspector: console.log does not always work with filters enabled
Summary: Web Inspector: console.log does not always work with filters enabled
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2015-02-11 12:55 PST by Brian Burg
Modified: 2016-06-10 14:07 PDT (History)
8 users (show)

See Also:

Attachments
[Animated GIF] Current behavior (86.16 KB, image/gif)
2016-06-10 12:09 PDT, Nikita Vasilyev 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Burg 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.
Comment 1 Radar WebKit Bug Importer 2015-02-11 12:55:46 PST 
<rdar://problem/19801162>
Comment 2 Joseph Pecoraro 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.
Comment 3 Brian Burg 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.
Comment 4 Joseph Pecoraro 2015-02-12 18:26:14 PST 
Not specific to Symbol. Can reproduce equally well with a string.
Comment 5 Nikita Vasilyev 2016-06-10 12:09:16 PDT 
Created attachment 281027 [details]
[Animated GIF] Current behavior

Looks like "works as expected" to me.
Comment 6 BJ Burg 2016-06-10 14:07:22 PDT 
Agree, looks fixed.