{"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,"title":"Norton  toolbar conflict again. Firefox 5  / Firefox 6 / NIS Toolbar 2011 / Request Policy 0.5.22b2","created_at":"2011-12-22T04:15:35Z","labels":[{"name":"extension","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/labels/extension","color":"ededed"}],"state":"open","updated_at":"2011-12-22T04:15:44Z","id":2633193,"closed_at":null,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/RequestPolicy/requestpolicy/issues/235","number":235,"body":"Upgrading Firefox 3 to Firefox 5 causes Request Policy 0.5.21 to break the display in the Norton Toolbar version 5.6. (Norton Engine version 18.6.0.29). The icons and boxes are missing although clicking the blank spaces brings up drop down menus.\r\nThe workaround is exactly the same as described in ticket 57 (closed). In RequestPolicy preferences enable 'Temporarily Allow All Requests' when browser starts. However I cannot see the point of having this startup mode. It is not much better than having RequestPolicy disabled completely.\r\nIn the RequestPolicy latest version 0.5.21 Components / Request Policy Service there is a reference to the Norton Safe Web Lite Toolbar IDArray {203FB6B2-2E1E-4474-863B-4C483ECCE78E}.\r\nThe actual toolbar is Toolbar 5.6 in NIS 2011 with engine version 18.6.0.29 (in Programs) and has the IDArray {0C55C096-0F1D-4F28-AAA2-85EF591126E7} for the toolbar in All Users / Application Data (version 18.5.0.125). Why the different versions I have no idea. \r\nPerhaps the reason for the conflict, RequestPolicy is trying to make the Add-on compatible with an outdated toolbar.","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/235","comments":4,"assignee":null},"comment":{"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"},"created_at":"2011-12-22T04:15:44Z","updated_at":"2011-12-22T04:15:44Z","id":3244168,"body":"[davemab2287] Hi Justin.\r\n'''RequestPolicy 0.5.22b1'''\r\nUnfortunately your patch has not resolved the issue.\r\nIn RequestPolicy preferences I still have to enable 'Temporarily Allow All Requests' when browser starts to allow Norton's toolbar to display correctly.\r\nToday Norton updated their toolbar from version 5.6 to version 2011.7.0.8 but I do not know if this makes any difference to the patch you added in RequestPolicy.\r\nI checked in RequestPolicy 0.5.22b1 under Components / Request Policy Service and I see the toolbar ID {0C55C096-0F1D-4F28-AAA2-85EF591126E7} line that you have added. That ID has remained within C:\\Documents and Settings\\All Users\\Application Data\\Norton\\{0C55C096-0F1D-4F28-AAA2-85EF591126E7} after Norton updated their toolbar in Firefox.\r\nAs well as reloading Firefox I have also reloaded the computer but that has had no effect.\r\n\r\n'''eibwen'''\r\nI wasn't quite sure what eibwen had in mind ....\r\n'we should expose chrome requests to the user and let the user decide their own policy'.\r\nI would be quite capable of changing the toolbar ID within RequestPolicy Components / Request Policy Service when Norton changes this ID and whist I could figure out how to add new code I do not feel that it would be responsible for the user to do so.\r\nIf the add-on had options included within the interface I could see some advantage.","url":"https://api.github.com/repos/RequestPolicy/requestpolicy/issues/comments/3244168"},"action":"created"}