I really like FireFox 13+, it’s converging more and more towards Chrome(ium), with some neat details that will get into future versions of Chrome(ium).
Yet, there are two things I don’t like (just as I didn’t like them in Chrome) – the “new tab page” (“most visited”) and “smooth scrolling”.
“Smooth scroll” has been round for some time, but off by default. Now it’s on.
To get rid of both:
Open a new tab.
Type in about:config as URL. This will open FireFox’s geeky configuration. Accept responsibility for editing this stuff when opening for the first time.
Type newtabpage under “Search”, and double-click the “browser.newtabpage.enabled“; it will turn bold and it’s value (on the far right) will change to “false“. This will disable the “new tab page” – you can immediately check this by opening a new tab – it should be again charmingly empty.
Type smooth under “Search”, and double-click the “general.smoothScroll“; this will disable the smooth scrolling. Again, you can immediately check it out.
There are literally hundreds of settings under about:config that can change all of FireFox’s behaviour, up to breaking it inadvertently. Feel free to click around! 😉
Final rant – what the hell is going on with the version numbers? There are no more v4.5, or v4.5.2… FireFox and Chrome just switched to single digit versioning… AFAIC, they can call it “whatever is current version”, or just vInfinity…
IMO, it lowers the meaning of versioning per se – there is a reason for the minor (and subminor, …) versions – it means it’s essentially the same thing, with some improvements.
E.g. Chrome’s v16 – “multiple profiles on by default” is the major change… Or “style editor” in FireFox v11… that’s like saying that “cup holder made of aluminium instead of plastic” makes it a new model of a car!
To turn your box into a dev web server is pretty simple, yet I’ve seen people struggling with this over and over again, so here’s a simple TODO list.
I won’t go over the likes of Apache installation, VirtualHost setup, .htaccess settings, etc. as you can find these online very easily, and might be specific to the needs of your project.
Most of the time I see people using localhost:8080 and a myriad of other ports to work on several sites locally; but you might as well work on http://www.myproject.com locally in just 2 simple steps:
Create a VirtualHost in Apache which goes by “the name” http://www.myproject.com, by including the following within the definition:
# all the other options and definitions ...
“Register” the domain name locally – simply add the following line to your /etc/hosts file (on Windows, this file is typically located under [Windows]/System32/Drivers/etc):
Now enable the VHost in Apache, restart Apache, and open http://www.myproject.com in the browser, and you’re ready to code off!
Note: The VHost name need not be a valid domain name – feel free to use myproject as ServerName and in /etc/hosts; just beware that some browsers will try to search for “myproject” instead of opening the local site. In such case, type in the whole http://myproject.
So, you’ve got your shiny new certificate, and your good old server. You’ve installed the certificate, chain or intermediate certificate, and all is nice and clean in FireFox, Chrome, Chromium, etc.
Then, your boss opens up his IE, and gets Certificate Error – “not issued by trusted certificate authority” and/or “issued for a different website’s address”. Of course, that’s a major pain, as IE – however bad, buggy and crappy it is – still holds majority of browsers market, as most computer users are incapable of installing a better browser. Continue reading →
I’m not a big fan of FB (don’t even have an account), but needed this to be set…
They hid it quite well, both in settings, and in the help section, under a cryptic name “public search” (which makes sense once you know it, but until then…).
So, to make you profile visible even to people who do not have FB account and/or are not logged in, go to Edit Profile, and then Privacy Settings > Apps and Websites > Public search > Enable public search.