My understanding of how scopes work is similar to layers of transparencies; when something isn't addressed by the most specific scope, HTTPSB should look through the blank spots to what's underneath.

An example on https://plus.google.com: On the * scope I have previously whitelisted YouTube so that embedded videos play everywhere:

Now I switch to the *.google.com scope to whitelist cookies, but look what happened: I've lost the whitelisting of YouTube:

Now I switch to the plus.google.com scope to blacklist talkgadget because it slows Google+ too much, but now I've lost the cookies AND YouTube. It also shows 7 changes were made to this scope, rather than 1.

What am I not understanding? I expect YouTube to be whitelisted on all scopes of google.com because it's whitelisted on *, and the more specific scopes for Google don't overwrite that. I expect plus.google.com to also be transparent to the lower levels and allow cookies and YouTube because they weren't overwritten either.

Thanks for the great extension!