Thanks for the fast and accurate reply, Henry!
In message <[EMAIL PROTECTED]> - [EMAIL PROTECTED] (Henry Sobotka)23 Oct
2001 16:23:06 GMT writes:
:>
:>Derek J Decker wrote:
:>>
:>> In message <[EMAIL PROTECTED]> - Felix Miata
:>> <[EMAIL PROTECTED]> writes:
:>>
:>> :>Why is there still no pref to turn off CSS?
:>
:>Try:
:>pref("css.allow", false);
This will probably make Felix Happy - I'd rather see this in the prefs, or,
better yet, have buttons on the toolbar for enable/disable CSS, enable/disable
javascript, enable/disable plugins, enable/disable animations. That way Evil
websites could be quickly countered and made usable/readable.
(Of course, as all of the mozilla UI is scripted, I supposed that if
sufficiently
motivated, I could do that myself. I'll have to see how big that if gets)
:>> Supposedly, user-side stylesheets can correct this kinda stuff, and they're
:>> supported by Mozilla - but who has the time/expertise to hack out a
:>> user-side stylesheet?
:>
:>CSS syntax is really quite simple:
:>[comma-separated list of HTML tags]{[semicolon-separated list of
:>applicable style 'property:value' pairs between braces]}
:>
:>For example, a one-line user.css along the lines of:
:>
:>body,h1,h2,h3,h4,div,p,span { background-color: white; color: black;
:>font: 12pt Courier }
:>
:>should (no time to test right now) render all pages in very plain
:>typewriter style.
Yeah, I've been doing this for a while here- mentioned the possibility
for folks like Felix (Somewhere out there there's a full-up CSS of
browser defaults - making that the user stylesheet should fix a lotta
problems. If there's interest I'll hunt it up for y'all).
Really, though, this facility, useful and powerful though it may be, will
remain beyond the ken of the vast majority of users until there's a Happy
Fun User-side CSS Wizard (damn I hate those things)for creating the bloody
things.
:>> There should also be a pref that makes the url entry field solely a url
:>> entry field. I don't want magical and inexplicable keyword expansion.
:>
:>pref("browser.urlbar.autocomplete.enabled", false);
Which can be changed via the preferences dialog, which is good.
:>> I don't want to be whisked off to some search site based on some criteria
:>> that I can't predict. If I want to use Google, I'll go there myself.
:>
:>Various search prefs to play with:
:>
<some deleted>
I've found that setting browser.search.defaultengine to a null string,
as follows:
user_pref("browser.search.defaultengine", "");
produces the desired behaviour. My point is that this should be available
in the preferences dialog - where you choose a search engine, "None" should
be one of the choices (along with a short explanation of the consequences
of choosing 'none' - ie, your browser will behave more predictably and in a
less annoying fashion.)
:>pref("browser.search.mode", 0);
:>pref("browser.search.powermode", 0);
:>
:>No idea what mode or powermode are and do.
I (and many others) would really like to see a complete documentation of
what the can go in prefs.js, and what it all does. The Customizing
page at mozilla.org <http://mozilla.org/unix/customizing.html> makes a
valiant stab at this, but it's not complete.
Thanks again for the help, Henry!
-Derek
+--------------------------------------------------------------------------+
| Derek J Decker [EMAIL PROTECTED] Decker Automation |
| |
| http://www.iglou.com/DeckerAutomation |
+--------------------------------------------------------------------------+
