Revision history [back]

Does this only apply on tjc or is it because I browse with the caret set to visible?

Does this only apply on tjc or is it because I browse with the caret set to visible?

Does this only apply on tjc or is it because I browse with the caret set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Does this only apply on tjc or is it because I browse with the caret set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Does this only apply on tjc or is it because I browse with the caret set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:configsettings without (without undo capability capability) mskes it moderately easy to make your browsing experience less than it could be.be. It is possible to edit userpref.js, though.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:configsettings (without undo capability) mskes it moderately easy to make your browsing experience less than it could be. It is possible to edit userpref.js, prefs.js, though.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:configsettings (without undo capability) mskes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, though.

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:configsettings (without undo capability) mskes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, though.though:

[nemo@Jolla ~]$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:configsettings (without undo capability) mskes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, though:

[nemo@Jolla `[nemo@Jolla ~]$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

... user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true); ... user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:configsettings (without undo capability) mskes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, though:

`[nemo@Jolla ~]$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

... ...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true); ... true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) mskes makes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, though:

`[nemo@Jolla ~]$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, though:

`[nemo@Jolla ~]$ $ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be. It is possible to edit or remove prefs.js, prefs.js, though:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing *Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

It is possible to edit or remove prefs.js, though:though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:*

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

A smarter thing to do migh be to keep a copy of prefs.js in git and update it after you fiddle with about:config. It would be even better if Sailfish automated git versioning of certain files like prefs.js and so implemented limited but useful Undo features.

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; *Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

*

It is possible to edit or remove remove# prefs.js, though. *though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:*occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

A smarter thing to do migh be to keep a copy of prefs.js in git and update it after you fiddle with about:config. It would be even better if Sailfish automated git versioning of certain files like prefs.js and so implemented limited but useful Undo features.

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; *Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be. *

It is possible to edit or remove# remove prefs.js, *though. though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

A smarter thing to do migh be to keep a copy of prefs.js in git and update it after you fiddle with about:config. It would be even better if Sailfish automated git versioning of certain files like prefs.js and so implemented limited but useful Undo features.

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; *Changing your Changing your about:config settings *settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be. *

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

A smarter thing to do migh be to keep a copy of prefs.js in git and update it after you fiddle with about:config. It would be even better if Sailfish automated git versioning of certain files like prefs.js and so implemented limited but useful Undo features.

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config *settings settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be. *be.

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

A smarter thing to do migh be to keep a copy of prefs.js in git and update it after you fiddle with about:config. It would be even better if Sailfish automated git versioning of certain files like prefs.js and so implemented limited but useful Undo features.

Original content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

A smarter thing to do migh Better though, is to up a git repository in an ancestory directory of prefs.js add git add $relative_path/prefs.js to enable undo revisions on that file for when you go a fiddle too far with changes to about:config.

Sailfish could be to keep a copy of prefs.js in git Otherly by taking take of such things for the user in an audit-friendly way, meaning the user has more control, and update it after you fiddle with about:config. It would be even better if Sailfish has their information and meta-information available to them in an obvious way - automated git versioning of certain editable files like prefs.js and so implemented limited but useful Undo features.prefs.js: git-audit, aka. collection of merainfo megabytes per month used by Google, etc's Javascripts to siphon about your life online, etc.

Original Some of the older content:

Does this only apply on tjc or is it because I browse on my Jolla phone with the caret configuration set to visible?

It means I cannot edit the ends of the title field of the bug entry form.

Likewise, I am not able to scroll with a form textarea. This is a problem when the text is more than the textarea can display all at once.

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Better though, is to up a git repository in an ancestory directory of prefs.js add git add $relative_path/prefs.js to enable undo revisions on that file for when you go a fiddle too far with changes to about:config.

Sailfish could be Otherly by taking take of such things for the user in an audit-friendly way, meaning the user has more control, and has their information and meta-information available to them in an obvious way - automated git versioning of editable files like prefs.js: git-audit, aka. collection of merainfo megabytes per month used by Google, etc's Javascripts to siphon about your life online, etc.

Some of the older content:

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Better though, is to up a git repository in an ancestory directory of prefs.js add git add $relative_path/prefs.js to enable undo revisions on that file for when you go a fiddle too far with changes to about:config.

Sailfish could be Otherly by taking take of such things for the user in an audit-friendly way, meaning the user has more control, and has their information and meta-information available to them in an obvious way - automated git versioning of editable files like prefs.js: git-audit, aka. collection of merainfo megabytes per month used by Google, etc's Javascripts to siphon about your life online, etc.

Some of the older content:

Filtering in the about:config dialog is of limited use as I don't know what I'm looking for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Better though, is to up a git repository in an ancestory ancestor directory of prefs.js add git add $relative_path/prefs.js to enable undo revisions on that file for when you go a fiddle too far with changes to about:config.

Sailfish could be Otherly by taking take of such things for the user in an audit-friendly way, meaning the user has more control, and has their information and meta-information available to them in an obvious way - automated git versioning of editable files like prefs.js: git-audit, aka. collection of merainfo megabytes per month used by Google, etc's Javascripts to siphon about your life online, etc.

Some of the older content:

Filtering Using the Filter input field in the about:config dialog is was of limited use as I don't know was unsure what I'm looking to look for.

tldr; Changing your about:config settings (without undo capability) makes it moderately easy to make your browsing experience less than it could be.

It is possible to edit or remove prefs.js, though. This command will undo all your changes to about:config and make your customisations a file whose preference customisations you can reintroduce incrementally to detect where problems occur:

$ mv /home/nemo/.mozilla/mozembed/prefs.js /home/nemo/.mozilla/mozembed/prefs.j_

...

user_pref("accessibility.mouse_focuses_formcontrol", true); user_pref("accessibility.typeaheadfind.linksonly", false); user_pref("accessibility.warn_on_browsewithcaret", false); user_pref("alerts.disableSlidingEffect", true);

...

user_pref("services.push.enabled", true); user_pref("svg.marker-improvements.enabled", true); user_pref("toolkit.osfile.log", true); user_pref("toolkit.telemetry.previousBuildID", "20130329080 257"); user_pref("ui.click_hold_context_menus", true); user_pref("ui.click_hold_context_menus.delay", 800); user_pref("ui.scrollToClick", 1); user_pref("ui.touch.radius.enabled", true); user_pref("ui.use_activity_cursor", true); user_pref("view_source.editor.path", "/bin/vi"); user_pref("view_source.wrap_long_lines", true); user_pref("webgl.min_capability_mode", true); user_pref("zoom.maxPercent", 6000); user_pref("zoom.minPercent", 300);

Better though, is to up a git repository in an ancestor directory of prefs.js add and do git add $relative_path/prefs.js to enable undo revisions on that file for when you go a fiddle too far with changes to about:config.

Sailfish could be Otherly by taking take of such things for the user in an audit-friendly way, meaning the user has more control, and has their information and meta-information available to them in an obvious way - automated git versioning of editable files like prefs.js: git-audit, aka. collection of merainfo megabytes per month used by Google, etc's Javascripts to siphon about your life online, etc.

Some of the older content:

Using the Filter input field in the about:config dialog was of limited use as I was unsure what to look for.