{"issue":{"user":{"id":1240282,"login":"jsamuel","url":"https://api.github.com/users/jsamuel","avatar_url":"https://secure.gravatar.com/avatar/bc1d195cedb959a3946572b08ce9e7c7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"bc1d195cedb959a3946572b08ce9e7c7"},"milestone":null,"created_at":"2011-12-22T06:07:11Z","title":"support mozilla.cfg defaultPref settings","updated_at":"2011-12-22T06:07:11Z","labels":[{"name":"extension","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/labels/extension","color":"ededed"}],"state":"open","id":2634533,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/RequestPolicy/requestpolicy/issues/282","closed_at":null,"number":282,"body":"User pocm [http://forums.mozillazine.org/viewtopic.php?p=11489117#p11489117 reports]:\r\n\r\n  I am experimenting with deploying !RequestPolicy site-wide, and am finding some strange behavior. Since the whitelists seem to be stored in config variables, I thought I'd try setting them in mozilla.cfg\r\n\r\n{{{\r\ndefaultPref(\"extensions.requestpolicy.allowedOrigins\",\"tinyurl.com\");\r\ndefaultPref(\"extensions.requestpolicy.allowedDestinations\",\"flickr.com\");\r\ndefaultPref(\"extensions.requestpolicy.allowedOriginsToDestinations\",\"google.com|gstatic.com\");\r\n}}}\r\n\r\n  This type of thing works for other extensions and their config rules (\"noscript.untrusted\", for example) but !RequestPolicy does not seem to recognize a \"defaultPref\" declaration at all. New profiles start up with empty whitelists. Why is that?\r\n\r\nI assume RP is doing something which is causing defaultPref functionality to be ignored.","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/282","comments":0,"assignee":null},"action":"opened"}