Open
Bug 1525221
Opened 6 years ago
Updated 2 years ago
Add a way to nicely indicate the user that a new warning message was added into an existing, out-of-viewport, group
Categories
(DevTools :: Console, enhancement, P3)
DevTools
Console
Tracking
(Not tracked)
NEW
People
(Reporter: nchevobbe, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
289.73 KB,
image/png
|
Details |
In Bug 1524276, we'll group the anti-tracking warnings messages.
Even if we don't have the full details of it at the moment, we are probably going to group them from the 1 message location.
Let's take an example.
Here's a view of the console when the first warning message comes in
--------------------------------------------
10:00:00 Request to access cookie or storage
on https://cdn.livefyre.com/livefyre.min.js
was blocked because it came from a tracker
and content blocking is enabled.
--------------------------------------------
then let's say we have 10, unrelated logs coming in.
--------------------------------------------
10:00:00 Request to access cookie or storage
on https://cdn.livefyre.com/livefyre.min.js
was blocked because it came from a tracker
and content blocking is enabled.
--------------------------------------------
10:00:01 log #1
--------------------------------------------
10:00:02 log #2
--------------------------------------------
10:00:03 log #3
--------------------------------------------
10:00:04 log #4
--------------------------------------------
10:00:05 log #5
--------------------------------------------
10:00:06 log #6
--------------------------------------------
10:00:07 log #7
--------------------------------------------
10:00:08 log #8
--------------------------------------------
10:00:09 log #9
--------------------------------------------
10:00:10 log #10
--------------------------------------------
Okay. So now let's say a new anti-tracking message is added. We create a group and put our 2 messages in.
--------------------------------------------
10:00:00 ▶︎ Request to access cookie or
storage was blocked ❷
--------------------------------------------
10:00:01 log #1
--------------------------------------------
10:00:02 log #2
--------------------------------------------
10:00:03 log #3
--------------------------------------------
10:00:04 log #4
--------------------------------------------
10:00:05 log #5
--------------------------------------------
10:00:06 log #6
--------------------------------------------
10:00:07 log #7
--------------------------------------------
10:00:08 log #8
--------------------------------------------
10:00:09 log #9
--------------------------------------------
10:00:10 log #10
--------------------------------------------
In the case the 10 log messages were tall enough to push the first warning messages out of the viewport, the user might miss that a new warning messages came in, which could be an issue.
We discussed a few options with Harald to still notify the user, without being to noisy (see attachment).
Reporter | ||
Updated•6 years ago
|
Whiteboard: [console-unclutter]
Updated•6 years ago
|
Whiteboard: [console-unclutter] → [console-grouping]
Updated•6 years ago
|
Updated•6 years ago
|
Priority: P2 → P3
Updated•6 years ago
|
Whiteboard: [console-grouping]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•