Closed
Bug 1044215
Opened 10 years ago
Closed 10 years ago
extend nsIWebProgressListener with tracking protection status
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: geko1702+bugzilla, Assigned: geko1702+bugzilla)
References
Details
Attachments
(1 file, 6 obsolete files)
(deleted),
patch
|
smaug
:
review+
|
Details | Diff | Splinter Review |
nsIWebProgressListener should contain status flags to indicate that tracking content has been detected and blocked or detected and loaded anyway. Element loaders should utilize those flags to emit corresponding security events.
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → gkontaxis
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8462785 -
Attachment is obsolete: true
Assignee | ||
Comment 3•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8462933 -
Attachment is obsolete: true
Comment 4•10 years ago
|
||
Comment on attachment 8462935 [details] [diff] [review]
extended nsIWebProgressListener with tracking protection events, modified script, image, object and frame loaders to emit such events
Review of attachment 8462935 [details] [diff] [review]:
-----------------------------------------------------------------
::: content/base/src/nsImageLoadingContent.cpp
@@ +176,2 @@
> /* Handle image not loading error because source was a tracking URL.
> * (Safebrowinsg) We make a note of this image node by including it
delete Safebrowsing
::: content/base/src/nsScriptLoader.cpp
@@ +1410,3 @@
> /*
> * Handle script not loading error because source was a tracking URL.
> * (Safebrowinsg) We make a note of this script node by including it
spelling Safebrowsing
Just get rid of Safebrowsing
Assignee | ||
Comment 5•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8462935 -
Attachment is obsolete: true
Assignee | ||
Comment 6•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8463654 -
Attachment is obsolete: true
Assignee | ||
Comment 7•10 years ago
|
||
Comment 8•10 years ago
|
||
Comment on attachment 8467480 [details] [diff] [review]
extended nsIWebProgressListener with tracking protection events and modified script, image, object, style and frame loaders to emit such events
Review of attachment 8467480 [details] [diff] [review]:
-----------------------------------------------------------------
::: content/base/src/nsImageLoadingContent.cpp
@@ +184,5 @@
> nsIDocument *doc = GetOurOwnerDoc();
> doc->AddBlockedTrackingNode(thisNode);
>
> doc->SetHasTrackingContentBlocked(true);
> +
Should this happen in nsChannelClassifier, similar to https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=1047705&attachment=8467901? That would allow you to avoid touching the loaders and consolidate adding STATE_BLOCKED_TRACKING_CONTENT to the docshell state in a single place.
Assignee | ||
Comment 9•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8467480 -
Attachment is obsolete: true
Assignee | ||
Comment 10•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Attachment #8469371 -
Attachment is obsolete: true
Assignee | ||
Comment 11•10 years ago
|
||
Comment on attachment 8469428 [details] [diff] [review]
extended nsIWebProgressListener with tracking protection events
We need to introduce tracking protection events in the progress listener so we can notify the UI (previously mixed content doorhanger)
Attachment #8469428 -
Flags: review?(bugs)
Comment 12•10 years ago
|
||
Comment on attachment 8469428 [details] [diff] [review]
extended nsIWebProgressListener with tracking protection events
But I'd like see (not necessarily really review) the patch using these flags.
Attachment #8469428 -
Flags: review?(bugs) → review+
Assignee | ||
Comment 13•10 years ago
|
||
Assignee | ||
Comment 14•10 years ago
|
||
Comment 15•10 years ago
|
||
Comment 16•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in
before you can comment on or make changes to this bug.
Description
•