Alexei

I am using [this fixture](https://cdn.rawgit.com/ghostwords/9fc6900566a2f93edd8e4a1e48bbaa28/raw/741627c60ca53be69bc11bf21d6d1d0b42edb52a/privacy-badger-navigator-donottrack-fixture.html) for testing. It comes with an inline script that prints the value of `navigator.doNotTrack`. Since it's a tiny inline script, anything asynchronous fails to run...

Filed [crbug.com/838242](https://bugs.chromium.org/p/chromium/issues/detail?id=838242) to get help with a related issue where some requests come with unknown-to-Privacy Badger frame IDs.

Filed https://bugzilla.mozilla.org/show_bug.cgi?id=1470537 to get help with the same unknown frame ID issue from Mozilla.

This is probably a blocker for issues like #1514 (any issue where we want to do something to **all** third-party requests).

By the way, I see "database storage" being used by `api.solvemedia.com` but I have trouble getting Chrome dev tools to show me the contents. ...

[Subdomains of yellowlisted domains should end up getting "cookieblocked".](https://github.com/EFForg/privacybadger/pull/1508#issuecomment-316165956) Agreed, we should add tests for the various scenarios of adding domains to the yellowlist and what effect that has on...

@cowlicks Should we yellowlist `solvemedia.com` even though it sets database storage?

Opened a crbug re inability to inspect IndexedDB contents in Chrome settings/dev tools: https://bugs.chromium.org/p/chromium/issues/detail?id=930773

Previously: #616.

Reopening as #219 has since been removed from Privacy Badger (as part of #951, I think). From a recent AMO user review: >[...] disables logging in with google, facebook and...