These are very old news (I’m sure), but I’ve just stumbled upon two useful keyboard shortcuts for Firefox.
- ⌘ + L — jump to and select (ready for overtyping) the contents of the location box.
- ⌘ + K — jump to and select (ready for overtyping) the contents of the search box.
In other words, you don’t need to reach for the mouse when typing a new URL or searching for something. I’m sure everyone’s been using these for ages, but they’re a revelation to me…
Update: Thanks to Mark for pointing out that ⌘ + L also works in Safari — but ⌘ + K doesn’t…
The WordPress 2.7 bug makes the Safari 4 beta useless to me, but if you’re a Safari fan who wants to stick with it, but don’t care for the cosmetic changes, head to the Random Genius blog. It has a whole list of hidden preferences for Apple’s new web browser, including one to put the tab bar back where it should be. It’s all done via Terminal commands, so they only work on Mac OS, though.
Or if you think Safari 4 is a pile of shit that you want to jettison from your Mac immediately, Mark Wheadon explains how to do it. Windows users just use Add/Remove Programs (or whatever passes for this option in Windows Vista), of course.
The new Safari 4 beta is pretty good, as long as you’re happy with a browser that lacks most of the features that have been standard on the competition for some years (ad-blocking and saved sessions, to name but two). It is a beta though, so it’s bound to be buggy — and I’ve just hit a big one.
When editing a post in the WordPress 2.7 back-end, clicking the Insert Link button causes the Ajax ‘Insert Link’ dialog box to ghost-out along with the rest of the page. As a result, both the dialog box and everything else on the page are inaccessible, and you have to open a new tab to do anything else (this only affects the current tab and not the browser session).
Actually, it is still possible to paste text into the URL box with a right-click, but won’t respond to any other mouse or keyboard command.
Given that WordPress has more than a few users, you might think that the Safari dev team might have tested this, but evidently not. Of course it may be a WordPress template issue, but a quick Google reveals that I’m not the only person to encounter this bug. The problem affects both Mac OS and Windows versions of Safari 4 beta, too. Silly Apple.