43 Folders

Back to Work

Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.

Join us via RSS, iTunes, or at 5by5.tv.

”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.

Tiger: New Safari tabs at your Command

As Mr. Gruber mentioned yesterday, 2.0 (Tiger) versions of Safari have added the ability to COMMAND-Return from within a web page’s form field in order to send the resulting page to a new tab (go ahead: try it in the 43F search field in the right column of this page). It also appears that you can COMMAND-Click most forms’ Submit buttons to similar effect. This builds on a feature available since (at least) the previous version of Safari in which you can COMMAND-Return in both the Address Bar and the Google Bar to generate a new, populated tab. (n.b: these also work in Safari 1.3 for Panther [Thanks, Roger.])

These may not seem revolutionary on the face of it, but as someone who’s already committed them to Safari muscle memory, I can assure you they’re wildly useful. A few random examples.

  • If you’re reviewing lots of form-based information, (set criteria; hit submit; look at results; repeat, repeat…), try COMMAND-Click-ing the form submit after you’ve set each new set of criteria, then reset your criteria and COMMAND-Click again. This is so much faster since you can generate all your pages/results at a pass, then move through the results, jogging between tabs at your leisure.
  • If you’re spending a lot of time on an interesting-looking site, you’ll often end up several directory layers deep. You want to pop all the interesting pages into new tabs, but you also don’t want to lose your place in the hierarchy/history. So, say you’re at http://example.com/fruit/apples/. Click in the Address Bar and COMMAND-Return to send the current deep-level apples page to a new tab. Now you can safely clip off “apples/” and truck your way back up the hierarchy by hitting plain old Return as usual. Sending the current page to a new tab becomes a little like hitting Save in your current web-surfing odyssey.
  • Many (um, lazy) developers overuse form submission when an HTML (or DHTML) link would be much more convenient for the user. Clicking a form button causes a page redraw and can easily make you lose your place on a very long page (ever try to quickly delete 10 items from you Amazon wish list?). COMMAND-Click-ing each of your many form buttons sends the superfluous results pages to their own new tabs. Click away, and when you’re finished, just “OPTION-COMMAND-W” to close all but the front tab. Done.
  • Hate those mystery meat “high-security” forms that make you fill out 50 fields of information then “forget” everything if there’s even one error on submission? If you find yourself on what feels like a death march form, COMMAND-Click to submit (or COMMAND-Return from within a field) to send the results to a new tab without losing your data. Flip over to the new tab to see if everything went okay, then head back to your safe copy in the previous tab if anything needs correction.

I’m probably leaving off a lot of good ideas, but I do encourage you to give this new feature a try. Unlocking the form submission functionality changes so much about how I use several sites each day—especially as tabbed browsing gets more deeply ingrained in my basic web behavior.

Edit 2005-05-10 07:16:17: At the risk of telling you something incredibly obvious that you’ve certainly known for months: you can also COMMAND-Click any HTML link to open it in a new tab. (You’d be amazed how many people don’t know that. Seriously.)

Tom Weir's picture

Regarding "Many (um, lazy) developers...

Regarding "Many (um, lazy) developers overuse form submission when an HTML (or DHTML) link would be much more convenient for the user. "

(D)HTML links are http GET requests which, strictly speaking, shouldn't change anything on the server. Form submisions are POST requests which by definition are meant to cause change on the server.

What happens when you allow GET requests to change state? Bad things: http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php http://www.instiki.org/revision/RollbackWars?rev=51




An Oblique Strategy:
Honor thy error as a hidden intention


Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed


Merlin used to crank. He’s not cranking any more.

This is an essay about family, priorities, and Shakey’s Pizza, and it’s probably the best thing he’s written. »

Scared Shitless

Merlin’s scared. You’re scared. Everybody is scared.

This is the video of Merlin’s keynote at Webstock 2011. The one where he cried. You should watch it. »