On 09/11/12 08:50, Jonas Sicking wrote:
> This is due to time constraints. It's much harder to implement in B2Gs
> security model since we essentially don't have any chrome JS code
> running other than what's part of gecko. In fact, we don't have any
> chrome code which displays UI at all.
But the settings app allows the changing of things which are prefs
underneath, right?
http://blog.astithas.com/2012/11/javascript-debugging-updates.html
suggests so.
Can't it just grow an extra facility where you input both the pref to
change and the value, instead of just a value? Even that would be a lot
better than having to reflash or reboot.
For bonus points, you could then "save" a pref name with a title, so
there was a screen of prefs that you'd said you wanted UI for - and it
would provide UI according to pref type.
For extra bonus points, remember previously-entered values for Text and
Number prefs and allow choosing between them.
But neither of the bonuses is essential.
> I agree. Though it's a bit trickier also since we want to make it hard
> to brick your device. With desktop Firefox you can at worst case blow
> away your profile. But if your phone isn't starting most people would
> be in trouble.
>
> But I agree this is something that we should try to figure out.
It is impossible to brick an Android device (to a similar degree) via
the UI, even using advanced settings and toggles?
Gerv