Mozilla/5.0 (Android; Linux armv7l; rv:2.0b13pre) Gecko/20110307 Firefox/4.0b13pre Fennec/4.0b6pre This is a weird edge case perhaps not a bug but not sure. On visiting the new mobile AMO and selecting to install an add-on , I am prompted with a dialog in Fennec that it wants to install the add-on with Install and Cancel buttons. On dismiss of this dialog (Cancel), I then proceeded to Clear Private Data in the browser through prefs. Upon tapping Add to Firefox again on this add-on, Fennec prompts me with the xpinstall prompt warning that "Fennec prevented this site (AMO) from asking you to install software on your computer".  Tapping Allow, and tapping Add to Firefox again redisplays this prompt. Why isn't this prompt visible prior to clearing my private data? Why is it visible aftwards?  https://addons.mozilla.org/en-US/mobile/addon/twitterbar/  http://mxr.mozilla.org/mobile-browser/source/locales/en-US/chrome/browser.properties#124
Forgot to mention, this was reproducible with a new profile on a Nexus One
Created attachment 517518 [details] screenshot Screenshot shows the xpinstall dialog which is only triggered on AMO after clearing private data and then attempting to install the add-on again.
Matt, is this a site pref that gets wiped out in sanitizer.sanitize()? http://mxr.mozilla.org/mobile-browser/source/chrome/content/sanitize.js#145 Would it make sense to re-add this pref value if so? http://mxr.mozilla.org/mobile-browser/source/app/mobile.js#195
Happens in Firefox too, moving bug
Component: General → Bookmarks & History
Product: Fennec → Firefox
QA Contact: general → bookmarks
Component: Bookmarks & History → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: bookmarks → add-ons.manager
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: a month ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.