Discussion of features in Seamonkey
14 posts • Page 1 of 1
Lots of features in SeaMonkey are hidden behind about:config settings. For example, the browser only supports the new html5 <picture> element if you set the dom.image.picture.enabled setting to true.
Now my question is, is there a list somewhere of all settings like that? I want to be able to enable all the cutting edge features that I can.
My goal is to score as high as possible on the https://html5test.com/ website.
With a new profile, SeaMonkey 2.33.1 scores 431 points, but by setting a number of settings with "enabled" in their names to true, I managed to crank the score up to 499.
The problem, however, is that I don't know what the vast majority of these settings does, so I don't dare enable them in my main profile!
There is no definitive list since there is no centralized control. Developers working on a particular feature e.g. <picture> may want to hide their in-development code behind a pref until it's production ready. Or they may not. It's up to them modulo their managers/module owners.
Many of these things are working already; it's just a case of the browser being overly cautious and not enabling them by default.
For people who don't mind tinkering with their about:config a bit, here is a list. First, if you inherited the profile from an older version of the browser, it's possible that some settings have the previous values, which don't match those of a new profile. So check these first.
¹ Note that this enables websites to request your physical location, which may constitute a privacy risk. You are always asked for confirmation; the website can't retrieve your info without your permission. Then again, if Google or Facebook find out where you are, who knows where their knowledge might end up. Use with care.
² Gamepad control seems to exist only on some platforms; this scores 2 on some machines, while it doesn't on others (using the same SeaMonkey version), even hough none of the machines actually have game pads.
If you've done this (or if you have created a fresh profile), SeaMonkey 2.35 will score 467 on the html5 test site.
Then there are these settings you can enable, which will also increase the score, even if you might not need them during normal browsing.
bringing the score up to 477.
³ Speech Synthesis doesn't seem to work in all circumstances. Need some more testing.
And some settings that I don't know enough of to say if they are security or privacy hazards. If you want to use these, note that you do so at your own risk. I am not responsible for what happens to your computer.
⁴ Only on http://beta.html5test.com; not yet implemented on the main site
⁵ media.mediasource.youtubeonly and/or media.mediasource.whitelist (which may or may not both be present) need to be false in order for media.mediasource.enabled to be recognised on the html5test site.
The score will then be a whopping 505!
But like I said, the score seems to depend on the hardware used. In a virtual machine that doesn't have hardware 3D support, the score is only 412 by default and 485 at the highest. So your mileage may vary!
Last edited by Pim on September 5th, 2015, 5:15 am, edited 1 time in total.
it would be very good and very handfull to have a view, 2 colum side by side of the feature enabled, and the feature desable.
and (main need) a colum date header of activation (or desactivation).
so every user could have a super view of features history changes.
You mean the date the user last flipped switches, or the date the feature was added to SeaMonkey?
btw, shouldn't be "Speech Recognition" YES in html5test? i always get a NO.
Speech recognition once worked, at least according to HTML5test, but it no longer does. Apparently they're testing in a different way now.
There are other things that do work now though; maybe I should update this post.
i can't get over 516 points currently.
sure, it this is more a fun thing than anything else...
Are you using special extra software? Many of the items on that site seem to require stuff such as specialised video drivers installed.
OK. Now two years after my first posting, lots of things have changed. Some features are enabled by default, while some other features turn out to have been disabled by default, and now require a setting set to true to re-enable them.
So here's a new list of about:config settings. Note that with the number of different versions of SeaMonkey available now, it's difficult to make one list that is applicable to all. So some settings will not exist on your copy, others will have no effect - the feature may be always-on by the time you read this, or it may work only in the newer Nightly builds, or it may have unwanted side effects; I cannot test on all platforms. Sorry. Again, use at your own risk!
¹ This feature seems to depend on the hardware and/or software platform; it scores points on some machines, but not on others using the same SeaMonkey version. The why is not clear yet.
² media.mediasource.youtubeonly and/or media.mediasource.whitelist (which may or may not both be present) need to be false in order for media.mediasource.enabled to be recognised on the html5test site.
³ Before rv:53 (SM 2.50) use webgl.enable-prototype-webgl2 instead
The bad news is that at this moment, the maximum score will only be 495 on the latest SeaMonkey release, 2.46. Not sure why that is lower than the 505 I found two years ago. Have things been disabled in the browser that were enabled then, or has the calculation used on the html5test site been changed?
Anyway, on the latest nightly build (2.52) I can get up to 519. But naturally that may change at any moment.
not sure about SeaMonkey, but in Firefox some settings don't make sense when enabling them manually.
is an example. you'll get the score in (currrent) Firefox v52, but in fact it does NOT work, it simply isn't fully finished.
SeaMonkey has the same backend as Firefox. Stuff like that should generally be the same in both browsers.
*Always* check the changelogs BEFORE updating that important software!
Input type="datetime" is only supported in Gecko version 54 and up, sorry. So that would be the Firefox Developer Edition.
See CanIUse. For some reason, the MDN page isn't updating.
Also, I don't know why the setting is spread out over four separate about:config settings (dom.experimental_forms, dom.forms.datetime, dom.forms.datetime.others and dom.forms.datetime.timepicker), but you do have to set all four of them to true before they will work properly.
14 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest