It often wrecks the layout, but I tend to print to PDF rather than deal with saved html files.

Regarding the .webarchive, I think IE supports another type of "web archive", with a .mht ending.

No fucking excuse.

Too used to G+ which fails in this case.

I agree with you that websites shouldn't override useful browser behavior, but I'm OK with websites restoring CTRL+S to it's rightful meaning of saving my work.

Ctrl-S says to your browser "I want to save this".

But.

It pains me to say this: what else would you want to have happen when a user presses Ctrl+S?

Are they really wrong, here? Wouldn't a user expect a "save blog" on Ctrl+S? How would I explain to a non-tech user why Ctrl+S works in Word, Excel, Powerpoint, but not in Medium?

1) I'm old enough that I've programmed the computers with the front panel switches bit by bit, but I've never used "Ctrl-S" as the "fast save" when writing documents. I don't know actually anybody who does. Autosave in Word functions as it should (not needing any user action) since at least 1998. My code editors and IDEs all do autosave too before compiling. What's the auctual benefit of ever using Ctrl-S in the middle of writing?

It becomes a mental tic, an "I've finished the paragraph" instinct. And I'm very glad medium handles it.

Can you explain this? Is it common to use an IDE that autocompiles every time it autosaves?

My first reaction: How else do you save?! You mean you actually take your hands off the keyboard, and click the floppy icon in a toolbar? Or even.. click on File > Save? Seriously?

I think this assumption as a very strong population bias.

With the people I work with.. it's all about keyboard shortcuts. If you don't know your basic keyboard shortcuts, you're too slow. But then again, I work around people with super customized Vim and EMacs configs and people who live in Photoshop/Illustrator all day. You just can't be productive in those environments without keyboard shortcuts.

For me, users who don't do "Ctrl-S" to save are certainly a minority.

I, for one, used to have this habit. The notion of "not knowing anyone who uses Ctrl + S" is a bit funny - are you really aware whether people around you do this or not? How does it come up?

[Dr. Watson's voice] He does that thing again!

For this particular default I see no problem in overriding it. I'm sure there's only a minority that routinely uses ctrl-S to save a lot, but essentially nobody uses ctrl-S to save a web page that contains a document they're in the middle of editing, given how esoteric that is and how unlikely it is to produce a useful result.

That's not to say that overriding defaults is good in general. But there's no need to be consistent about it. Overriding ctrl-S is totally different from overriding the arrow keys, for example.

I ought to keep a shortcut to that on my desktop.

In-browser WYSIWYG or markdown editing is not good UX design. Period. Full stop. It's never been better than an offline text editor, and when you try to present a cross-browser experience, this is what inevitably happens.

Worst of all, I can't seem to find a way to alter the keybinds, or (more importantly) the mouse-5-means-go-back gesture.

And not to mention google plus, that swallows Ctrl+PgDown and Ctrl+PgUp, which happen to be shortcuts to move through tabs. So you are moving through tabs, then you suddenly stop, and you have to reach for the mouse.

But what's really silly is that the browser actually allows a webpage to override such a basic shortcut like F5.