On Nov 14, 2012 4:07 AM, "Gervase Markham" <[email protected]> wrote: > > On 13/11/12 11:46, Jonas Sicking wrote: >> >> It would indeed be possible to add an API exposed to the settings app >> which allowed it to modify arbitrary Gecko preferences. What I was >> referring to was running about:config or other chrome-privileged >> pages. >> >> However, see below. > > > OK. Could we add such an API, and then have a (regexp-based, perhaps) whitelist of preferences the app would pass through to be set, or blacklist of stuff that couldn't be changed?
I'd say we're already within the realm of things that we don't have time to do for v1. Especially once you add UI and QA for these features to the equation. > I'm trying to figure out how we can restore some hackability without opening the possibility of bricking. Hackability is to me quite different from being able to set prefs. Ability to install custom high privileged apps is IMO much more important and we already have that. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
