This repository has been archived by the owner on Dec 3, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Non-blocking: consider nuanced background price polling when PBM tabs exist #177
Milestone
Comments
I like these enhancements a lot. We might even be able to simplify/combine them |
Osmose
added
the
[ENG]: Triage
Work the team needs to review to determine if it will be included as part of the next milestone.
label
Oct 18, 2018
This is my favorite part of the issue |
What can I say? I'm a crowd-pleaser. |
muccimoz
added
reserve-November milestone
and removed
[ENG]: Triage
Work the team needs to review to determine if it will be included as part of the next milestone.
labels
Oct 18, 2018
1 task
biancadanforth
added a commit
to biancadanforth/price-tracker
that referenced
this issue
Nov 14, 2018
Previously, price polling (a.k.a. background price updates) was disabled when Do Not Track, Tracking Protection or certain cookie settings ('reject_third_party' and 'reject_all') were enabled. Now, price polling occurs in these situations. This leaves the `shouldUpdatePrices` function in `privacy.js` kind of useless, but I left it there instead of removing it entirely in order to add the Private Browsing check that is part of mozilla#177.
@muccimoz how disruptive would it be to bring this in to the post-launch milestone? |
muccimoz
added
the
[ENG]: Triage
Work the team needs to review to determine if it will be included as part of the next milestone.
label
Nov 15, 2018
Hi Chuck. We can review this issue during triage at the team meeting today. |
muccimoz
removed
the
[ENG]: Triage
Work the team needs to review to determine if it will be included as part of the next milestone.
label
Nov 15, 2018
Hi Chuck. This has been added to the milestone. |
biancadanforth
added a commit
to biancadanforth/price-tracker
that referenced
this issue
Nov 15, 2018
Previously, price polling (a.k.a. background price updates) was disabled when Do Not Track, Tracking Protection or certain cookie settings ('reject_third_party' and 'reject_all') were enabled. Now, price polling occurs in these situations. This leaves the `shouldUpdatePrices` function in `privacy.js` kind of useless, but I left it there instead of removing it entirely in order to add the Private Browsing check that is part of mozilla#177.
biancadanforth
added a commit
to biancadanforth/price-tracker
that referenced
this issue
Nov 16, 2018
Update `shouldUpdatePrices` with a check for whether or not the active window is a private window. I did not add a check for `isActiveWindowPrivate` in `shouldExtract` in `./src/privacy.js`, despite the fact that `browser.extension.inIncognitoContext` returns the "wrong" value for background extraction, because background extraction is gated by the `shouldUpdatePrices` check.
biancadanforth
added a commit
to biancadanforth/price-tracker
that referenced
this issue
Nov 20, 2018
Update `shouldUpdatePrices` with a check for whether or not the active window is a private window. I did not add a check for `isActiveWindowPrivate` in `shouldExtract` in `./src/privacy.js`, despite the fact that `browser.extension.inIncognitoContext` returns the "wrong" value for background extraction, because background extraction is gated by the `shouldUpdatePrices` check.
biancadanforth
added a commit
that referenced
this issue
Nov 21, 2018
Fix #177: Disable price polling in Private Browsing windows
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This does not need to block release
#168 went a long way to addressing #72.
As discussed in the PR, there may be some additional (non-blocking) enhancements to make for PBM ...
The text was updated successfully, but these errors were encountered: