Great reply Bob. You summed up why save and save as are separate perfectly. The one specific time I use the save as crutch is when I open an mp3 file in the browser and quicktime plug-in plays the content. If I like the song I am listening to my muscle memory is to hit Ctrl + S which maps to nothing in chrome. Hopefully we will see someone make a better plugin than quicktime for playing audio and we will see the mp3 playing options like we see in gmail today (making save as source option not require a 'pro account').
On Sep 7, 8:10 am, Bob Oliver Bigellow XLII <[EMAIL PROTECTED]> wrote: > The OP specifically said "Save As" which is an option available in > Chrome. Just "Save" isn't an option available in Chrome, as it > shouldn't be. > > In computer programs, "Save" means to save the file in the current > file path with the current file name. If a file path or file name has > not yet been set, the user is prompted. "Save As," however, will > always prompt for a file path or file name, even if one has already > been set. > > In a web browser, every bit of content that gets pulled down to the > browser already exists... it exists in both a read-only path (on the > web server) and in a potentially read/write file (in the cache)... > however, the browser is designed for viewing, not editing. So, if you > can not make changes to the HTML using the browser, there is no point > in a "Save" choice. That would imply that you are either trying to > save your changes to the web server (not really possible)... or to the > temporary cache (where the file now physically exists at that point.) > > Therefore, the only logical option for a web browser to have is "Save > As" (which implies that you want to save another copy of the file that > is in the computer's cache, but you want to save it to a more > permanent and easily accessible location for later retrieval)... which > is the option Chrome has. > > When other browsers implemented such functionality, it was usually a > crutch which broke the standards in order to get people to make the > transition from applications to websites. However, Chrome is not > meant to be merely a "web browser"... it is meant to provide an > interface (with as little chrome as possible, and with as few features > as possible) to web applications. > > In fact, I'm willing to bet that with time, more buttons and options > will be REMOVED from Chrome than necessarily ADDED to Chrome. The > goal was to get away from browser bloat... and put the attention, once > again, on the features of the web applications being used. > > On Sep 7, 3:09 am, Wild Thing <[EMAIL PROTECTED]> wrote: > > > The OP is talking about "Save". Ctrl + S in chrome does nothing. > > > On Sep 7, 9:37 am, Bob Oliver Bigellow XLII <[EMAIL PROTECTED]> wrote: > > > > CTRL-S is the standard for just Save, not for Save As... If Chrome > > > implemented CTRL-S for Save As, it would go against standards. > > > > On Sep 6, 10:09 pm, Bryon <[EMAIL PROTECTED]> wrote: > > > > > Why isn't the standard Ctrl+S shortcut for Save As.. implemented in > > > > chromium? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
