Posts Tagged ‘firefox’

General

Firefox tab position redux

FirefoxI heart Firefox. It’s quick, has a slew of add-ons that make my browsing a breeze and I’ve got it set-up just how I like it. But those crazy developer types think they know better and in the last 3.6 update, they decided that new tabs opened from a link should appear directly to the right of the parent tab instead of at the end of the list as in the past. Pretty logical but grumpy old me can’t get on with this change.

For a start, it’s not consistent. Opening a previous or next page in a new tab (by middle-clicking on the back or forward buttons) doesn’t follow the new to-the-right pattern but instead opens the new tab in the old place, right at the end of your current tab list. Also, if you open a child tab, click to view it and then close it, you’ll now be viewing the page to the right of the parent tab rather than the parent itself. It’s a small annoyance but one that doesn’t gel with my ‘how it should work’ world view. So rather than put up with these (admittedly tiny) niggles, I figured I’d just switch back to the old system.

After a little searching, I found the fix. Open a new tab and put this in the address bar…

about:config

…and tap <return>. Click past the “I promise not to go in like a bull in a china shop!” warning and you’ll be presented with a loonnngggg list of settings. This is basically all the stuff you can tweak in Firefox but the devs would rather you didn’t in case you bugger something up. Simply scroll down the list until you spot…

browser.tabs.insertRelatedAfterCurrent

It’ll be set to ‘true’. Right click the entry and select toggle so it reads ‘false’. You can close that tab and now, when you open a new child tab, Firefox will respond as it used to. Of course, if you get sick of trawling to the end of your tabs for new pages then simply open the config again and toggle it back.

And… if you’re still using that ramshackle stack of bugs commonly known as Internet Explorer, then please (insert stream of insults veiled as a recommendation to switch to another browser, here).

General

Bleaurgh… IE

Pretty much just a follow-up to one of my earlier posts (‘Skoardy v3.0‘) where I unveiled/announced my revamp of the Skoardy.com theme. I was pretty happy with the results as I’d almost managed to achieve everything I set out to with the new look and also added some elements I’d overlooked the first time I switched everything over to WordPress.

Of course, I have little-to-no faith in my skills with CSS, hence the comments about not coughing. It’s a rickety set of stairs, the outer shell of Skoardy.com, and give it too much of a hammering and it’s likely to fall apart. But, it looked okay and everything was where it should be… or so I thought.

In comes Microsoft’s Internet Explorer with it’s size 9 clod-hoppers and its own unique take on what things should look like. Normally, I use Firefox as my default browser. It’s small, fast and best of all, with the right add-ons, you’ll never need to see another advert again. It looked fine on that. I even tried the site with Google’s Chrome – the new kid of the block that’s also small/fast. Also, looked fine. And with IE? Yeah…um, well, it was borked on IE.

I don’t usually like booting IE up. These days it seems there’s always some kind of new exploit being reported and death from within for anyone foolish enough to take it for a spin on the intahwebs. Eventually, I worked up the nerve to have a look. Things were misplaced, oddly positioned and some bizarre gaps were appearing. One by one, I managed correct the flaws, writing in more specific code so that even IE couldn’t get creative with my instructions. Everything was fixed, except for some gaps in the sidebar. I know IE users take up the market share of web tourists (seriously guys, switch to a new browser already!) so I wanted to fix it but nothing I tried could get rid.

So every few days I’d get a new idea and try it out with the hope that it’d fix the problem without breaking the site for other browsers. Every time, same result. Nada.

Tonight, however, the new fix worked and everything fell into place. Better still, it’s something that other browsers appear to care little about. Of course, this is just with version 7 of IE. If it’s broken on older versions, screw you. Upgrade… or better still, switch to a new browser already!