BUGS: 1.9.4.x Dev
Posted: Sun Jun 14, 2009 4:21 am
Giorgio,
There are several issues that I think you need to look into for this build:
1. Any time I add a site to the whitelist, checking the list, the file:// is added as well and I certainly didn't do it. I have managed to get that to happen in 7 sites out of 18 that I tried. So just about 50% of the time. Not sure if the way the site is designed contributes to this bug but for me this would be a biggie.
Edit: ITS NOW PERSISTENT and file:// WILL NOT go away from the whitelist, for me this is a HUGE problem.
2. When you whitelist a site (forbid active content on trusted is not checked) it will not show the flash or active content until you restart Fx and then go back to that page again. This is a huge problem as you can imagine, having to reboot the browser each time trusted decisions are made defeats the purpose, no?
3. After you whitelist a site, the performance on that site is degraded and there is a huge lag in mouse movements and typing while in the "canvas" area of Fx for that site (the display) and the only way to get it to stop so far has been to disable NS or close the tab and reload again from URL bar.
Let me know if you need anything else but clean profile with NS or reset did nothing for these issues either. Hope that helps you out but I have no choice but to rollback right now. Also, can you tell me how NS is build with regards to permissions processing; namely what authority is exerted first? ABE asserts first or regular untrusted settings?
Case example: I don't want to allow googleapis.com or yahooapis.com and will place them on the untrusted list. However, there might be selective sites that I DO want to give access, I can setup ABE to allow them access but the question remains will those selective permissions be honored or will they be ignored because the domain is marked untrusted?
There are several issues that I think you need to look into for this build:
1. Any time I add a site to the whitelist, checking the list, the file:// is added as well and I certainly didn't do it. I have managed to get that to happen in 7 sites out of 18 that I tried. So just about 50% of the time. Not sure if the way the site is designed contributes to this bug but for me this would be a biggie.
Edit: ITS NOW PERSISTENT and file:// WILL NOT go away from the whitelist, for me this is a HUGE problem.
2. When you whitelist a site (forbid active content on trusted is not checked) it will not show the flash or active content until you restart Fx and then go back to that page again. This is a huge problem as you can imagine, having to reboot the browser each time trusted decisions are made defeats the purpose, no?
3. After you whitelist a site, the performance on that site is degraded and there is a huge lag in mouse movements and typing while in the "canvas" area of Fx for that site (the display) and the only way to get it to stop so far has been to disable NS or close the tab and reload again from URL bar.
Let me know if you need anything else but clean profile with NS or reset did nothing for these issues either. Hope that helps you out but I have no choice but to rollback right now. Also, can you tell me how NS is build with regards to permissions processing; namely what authority is exerted first? ABE asserts first or regular untrusted settings?
Case example: I don't want to allow googleapis.com or yahooapis.com and will place them on the untrusted list. However, there might be selective sites that I DO want to give access, I can setup ABE to allow them access but the question remains will those selective permissions be honored or will they be ignored because the domain is marked untrusted?
.)
.