For one, the Clear Browsing Data dialog/page should have a separate checkbox for flash if flash is detected. It shouldn't be lumped in with the delete cookies choice.
Since there is no guarantee what URL Adobe will use for its Flash settings panel in some future day, in all practicality, the Flash URL can't be hard-coded into a browser to 'skip' deleting its 'cookie' when all the other Flash cookies are deleted by a user for privacy protection.
Currently it's the macromedia.com entry in the pepper data folder that contains the settings.sol for the global settings set on the linked page, right?
If so, it sounds like it's definitely doable to provide a sub-checkbox *option* to control whether it gets saved or not when checking the clear flash checkbox.
Since there is no guarantee what URL Adobe will use for its Flash settings panel in some future day, in all practicality, the Flash URL can't be hard-coded into a browser to 'skip' deleting its 'cookie' when all the other Flash cookies are deleted by a user for privacy protection. What would you suggest a browser do under those circumstance?
Sounds like the domain should live in a file that can be remotely updated if the domain changes. Or, it should be provided by the plug-in in some way (where you update the plug-in if the domain changes).
I definitely thinks there's something that could be done, even if it requires cooperation with Adobe and or Google (PPAPI improvement if necessary).
Too bad there's not an extension to save the flash security settings and then auto-apply them (after you clear flash cookies) by visiting the macromedia.com page(s) and auto-submitting the changes.
Though, in the OP's case, if there was a separate delete flash data checkbox, the OP could just uncheck it when deleting browsing data and manually (or with script etc.) clear flash data while excluding the main settings. I assume there might be a little database handling though, which would make that more difficult.
Anyway, definitely sounds like a legit problem. I never adjust the flash settings on that page though, so the problem doesn't personally affect me.
