I'd love the health-report web page to suggest remediations for performance-sucking issues. But I'm afraid of allowing remote content (albeit 'secured' using HTTPS) to actually trigger this behaviour. I'm much more confident in the pattern that the code stays in the browser in contrast to being highly volatile.
A one-shot "optimize performance" button that calls a list of hard-coded procedures (e.g. disable_known_performance_killers(), reset_experimental_settings_that_are_for_power_users_only(), ...) would be pretty cool though :) Even if more automation is desired, I'd go for the in-browser solution. _______________________________________________ dev-security mailing list dev-security@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security
