A Small Safari Request
To view a document's source in Mozilla, Camino, or Internet Explorer for OS X, the keyboard shortcut is Command-E. The shortcut, to a Mac web developer, is as universal as typing Command-S to save a document. But in Safari, the view source shortcut - for whatever reason - is a clunky triple key press of Command-Option-V.
But Command-E must already be assigned to something else, right? Surprisingly, no. Which leaves the question - why intentionally break consistency and assign a proprietary set of keys?
If the vast majority of users who actually use the view source feature are web developers, then you can also assume they work with multiple browsers and are already accustomed to mashing Command-E from their years of work before Safari came on the scene. So why change the "standard," especially if you haven't assigned it to anything else?
Admittedly, a nit-picky request, but change for the sake of change is rarely a good idea, especially when there isn't a clear reason.
Comments
I agree command-option-v is bizarrely arbitrary. Even outside Safari the only vaguely standard behavior for command-e is eject and we already have another key for that.
As always, a per-person solution could be to edit the NIB file or use Unsanity's Menu Master to change the keyboard equivalent.
Posted by: Paul McGrane at May 6, 2003 2:27 PM
Go to Unsanity and download "Menu Master". The haxie allows you to change shortcuts in nearly every application. I personally haven't tried it, but I'm sure it will solve your problem. :)
Posted by: Jeff at May 6, 2003 2:35 PM
Well, I can see that having V in the shortcut might make more sense from a logical standpoint - what does the E stand for that it ties with View Source? (like Command-S to Save or Command-P to Print) Perhaps with their nonstandard assignment, they're trying to set a trend of logical ties between shortcuts and the actions they represent. Just a thought. :)
Posted by: ste at May 6, 2003 2:38 PM
Hmmm, in all my versions of Mozilla it's the 'U' not the 'E' for 'View Source' - 'E' opens the current url in Composer. 'E' is for Edit.
More info: http://www.mozilla.org/docs/end-user/moz_shortcuts.html
Posted by: pete at May 6, 2003 2:47 PM
I also would like for them to switch back the key command for view source. I don't know how many times I hit command-E and say "what the!!" when nothing pops up.
As long as we're on the subject of making concessions for web developers. I wish that they would adopt either the viewing of the image size when you send it to another window, or a get info about this image dialog. Something so that I don't have to copy and paste an image into photoshop just to figure out its dimensions.
Posted by: steven at May 6, 2003 2:53 PM
Steven - very good point on the "get info" request. I have longed for this functionality as well.
Posted by: Todd Dominey at May 6, 2003 3:01 PM
With dragthing and this applescript you can not only have cmd + E view source in Safari, you can have the source viewed in your text editor of choice! I use this applescript to view source in BBedit.
Posted by: Nate at May 6, 2003 3:02 PM
cmg + opt + v is admittedly clunky, esp. on my microsoft natural keyboard pro, but one more thing along a similar line (OS X) is how come cmd + shift + h takes me home, cmd + shift + a opens my applications folder, but cmd + shift + d doesn't open my documents folder?
Posted by: JBennett at May 6, 2003 3:19 PM
2 things i like in IE win:
1. right click an image to get its width/height/filesize properties
2. ctrl+n opens the contents of the current window in a new window. if i'm in some fixed size, featureless popup, ctrl+n will spawn the same window with full browser chrome so i have access to all browser tools.
Posted by: nathan at May 6, 2003 3:40 PM
yeah,
what about just assigning view source to a function key or sommat? f12 views source. man, if everyone'd do that, we'd be set.
-mathew
Posted by: mathew at May 6, 2003 5:42 PM
Two words: Cocoa Gestures.
I hold down the command key while drawing a box and it views source in both Safari and Camino. It's addicting.
Posted by: Jim at May 6, 2003 6:08 PM
Here's another thing I would like to see in Safari: when copying text from Safari and pasting it in another program -- notably BBEdit -- there's always a junk character pasted at the very beginning of that text. Yeah, I'd like to see that go.
Posted by: Khoi Vinh at May 6, 2003 10:48 PM
Pete is correct concerning Mozilla's use of Control/Command-U to view source, which appears to be an even less obvious keystroke. For Windows users (like myself) this is however far easier than the Internet Explorer alternative which requires a two-stage Alt-V, C combination.
For those who are interested it may be worth noting that Netscape 4 (and possibly earlier versions too?) on Windows also uses Control-U to view source. Yet another example of early web browser hangovers affecting modern UI design?
As a sidenote, for all the haranguing Apple gets for its more recent UI design decisions, I can't understand why people think Command-Option-V is so proprietary or inconsistent. Command-V is obviously already Paste (although lets not get started on why) but (some combination)+V for View Source seems perfectly Logical to me.
Perhaps it would make sense to ask why Command-E has been seized upon by Camino and Internet Explorer (for the Mac) as the View Source shortcut?
Posted by: Ben Darlow at May 7, 2003 3:56 AM
You could use iKey, does specifically key assignment unlike dragthing, to assign command-E in all browsers to run the view source applescripts and then you can even have it open the source up in BBEdit, yummy syntax highlighting.
Posted by: Voodoo Tiki God at May 7, 2003 9:29 AM
...or you can use a two - three button mouse, right click and select "view source". Easy livin'
geof
Posted by: geof harries at May 7, 2003 11:40 AM
Here's why I like COMMAND OPTION V and hope Safari will stick with it.
As y'all know, in OS X we lost the ability to view source in BBEdit, PageSpinner, Dreamweaver, etc. by manipulating a browser preference.
The workaround, as Nate mentioned in an earlier comment, is to install any of several good View Source AppleScripts and trigger them via DragThing, assigning Command-E or any other key sequence you choose.
Trouble is, the scripts I've used are not application sensitive. That is to say, once installed, Command-E always means "Open BBEdit/tool of choice and view frontmost document in IE/Safari/browser of choice."
Under this scheme, Command-E no longer ejects disks. Even if you are working in the Finder, and even if you have no browser and no web editor open, Command E will look for the frontmost window of your (non-open) browser and try to display its source in your non-open editor. The result: an AppleScript error instead of the desired functionality.
By avoiding the Finder's Command-E and using a different key sequence, Safari guides power users toward using a different key sequence for their DragThing/AppleScript view source combo. Thus it helps us avoid a completely futile situation in OS X.
The ideal of course would be for Safari and other OS X browsers to allow us to view source in our tool of choice without requiring AppleScript and third-party tools, and this may happen when Safari and Camino are fully released products rather than betas.
The most frustrating of all is IE5/Mac, which was a fine little standards-compliant browser in OS 9 but is buggy in OS X and in which "View source using ...", while still available in the Preferences, does not work at all. In fact, once you've set it up, you cannot view source at all in IE5/Mac ... not even internally.
Posted by: zeldman at May 8, 2003 10:34 AM
I know someone who works on the Safari team. I'll mention mention this thread to her. btw, nice site!
Posted by: adam at May 24, 2003 3:16 AM
To me, this is a matter of simple ergonomics and workflow. The Safari combination is HARD. The Mozilla combination isn't easy. The IE combination is a piece of cake, utilizing only one hand and requiring no wrist motion (like Cmd-Q, Cmd-S, Cmd-A, Cmd-Z, and the rest of the important ones -- and their proximity suggests that ye developers of legacy understood that Cmd-L isn't something you want to do often).
Posted by: Brandon at May 25, 2003 9:28 PM
