Ant wrote:
> Interesting that MS disabled that ^S hotkey by default. :(
Actually the default, I believe, is to have shortcut keys enabled
(probly the Outlook.com shortcut key set). It was *me* that went into
my
outlook.com account's config to disable that option. It's been too
long for me to remember why I didn't want any key shortcuts enabled.
> I think this is the problem [changing focus away from compose pane]
> since he easily get confused by reopening the same e-mails in his
> folders like drafts. :(
Users have been complaining for 10 months about Microsoft fucking up the
webmail client's GUI of not opening a new window (new browser instance
or a floating frame) when composing a new message. It is so damn easy
to click somewhere else in the webmail client while composing a new
message. For example, maybe you need to go check something in another
e-mail when writing up the new message.
In Comcast's webmail client, starting a new message opens a new "tab"
(not within the web browser but within their webmail client). You can
bounce around those in-client tabs without losing the Compose tab.
Gmail opens a new frame that you cannot move can make disappear (by
clicking on its title bar), so you can look in other folders without
losing that new draft. Every local e-mail client I've used let me
compose in a new window, so I could navigate around inside the local
client looking up other info.
Only Microsoft, after changing to their new GUI back around Nov 2017,
stopped protecting the compose pane. The "open in new window" option
disappeared to keep the new-message dialog open. Click somewhere else
that change focus away from that pane and it disappears along with any
changes you made since the prior auto-save. They changed the GUI again
(
https://www.theverge.com/2018/3/14/17121032/microsoft-outlook-web-redesign-features),
so I have to get used to that one now. There was a Beta toggle to let
me go back to the legacy GUI but no longer. "Resistance is futile" (the
collective Borg multi-voice mantra). Microsoft keeps adding fluff but
not substance.
> doesn't Outlook prompt user that the e-mail wasn't saved?
^^^^^^^
Please use
outlook.com when referring to the webmail client. Saying
just Outlook means the local client ran as a program/app on a local
host. Outlook will warn you. Outlook.com cannot, especially with the
loss of opening the compose dialog in its own window or object.
If the web browser is exited, how can any script run in the page no
longer loaded to warn the user about discarding unsaved changes?
Actually, it might be possible by using Javascript's onunload event;
however, that's been so abused that web browsers no longer let the page
present its own content and instead present a standard warning about
navigating away from the web page. That only works when unloading that
document (page) in that tab. Does nothing when you switch tabs, and
might not trigger when you close the web browser or it crashes or you
kill its process.
> I wonder if he accidently deleted it by highlighting before the
> autosave?
The Send and Discard buttons in
outlook.com's (webmail client's) compose
pane are right next to each other; however, when using the Discard
button, there is a prompt about losing unsaved changes.
I just did another test with the compose pane. I created a new message,
added some content, and clicked on one of the folders. My changes,
without prompt, got saved in the copy in the Drafts folder. I did this
several times where I added content and immediately clicked somewhere
else hoping to avoid the auto-save timer. The changes got saved without
prompt.
I then added new content and tried to close the tab to deliberately lose
any changes before an auto-save. The web browser's dialog appeared
asking if I wanted to leave the page, so their webmail client is using
Javascript's onunload event to prevent accidentally leaving the page and
losing changed content. Hmm, now I'm not sure how I managed before to
lose changes. Clicking somewhere else makes the compose pane disappear
but my changes got saved. There's auto-save (perhaps to protect losing
all changes due to the web browser crashing or getting killed). When I
try to unload the tab after making changes in the compose tab, I get the
unload event trigging a prompt asking if I really want to leave the
page. If I make changes and try to exit the web browser, that unload
event triggers again asking if I want to actually leave the site (which
means changes wouldn't get saved).
Obviously if the web browser crashed then it cannot run the Javascript
triggered by the unload event. Adblockers work by corrupting web pages,
so it's possible the OP is using an adblocker or other content blocker
that obviates the Javascripted protections in that webmail client. When
I try to leave the page (unload its tab or exit the web browser) and get
the unload alert, there is an option to "Prevent this page from creating
additional dialogs". That might later allow leaving the changed page
without the warning. I never enable that option. I suspect if the user
enables the option, it becomes a site preferences which means having to
delete that site's stored preferences in the web browser to get the
popup alert the next time you leave (unload) the page with unsaved
changes.
Seems a bit difficult to accidentally lose the changes with the timed
auto-save, change-of-focus auto-save, and page unload alert. You need
to find out what the user did that "lost" his changes. Maybe the user
thinks the web browser is a local e-mail client.
> Too bad Outloook.com doesn't have a history of autosaves.
Draft history (versioning) is a feature in the local e-mail client (MS
Outlook), not in their webmail client (
outlook.com) whether free or
paid. Hotmail had previous versions of drafts. Yet another feature
missing in Microsoft's new GUIs (along with loss of option to open a
draft in its own window).
With auto-save at 1-minute intervals, there could be a hell of a lot of
draft versions. The longer the draft was open in the compose pane, and
with any little change, like just 1 character, the auto-save would
result in yet another version of the draft. Drafts are synchronized to
the local e-mail client (MS Outlook when using Exchange) but all that
versioning would require lots of traffic albeit small. While they give
a generous disk quota, they don't want to be storing all that draft
history along with every version of a draft.
In their webmail client, when a draft gets saved, it overwrites any
existing one. There is only one copy of the draft. No versioning. For
example, a user could cut out a huge section of their long e-mail,
realize they need it back, but auto-save (timed or changing focus)
already save the modified copy with all the omitted content. When
cutting out a big section of content from a draft currently being
edited, use Shift+Del instead of Del. Shift+Del will copy the
highlighting content into the clipboard before cutting it from the
document.
However, if you paste something else into the Windows clipboard then you
lose the clipboard's prior contents. That's why I use a clipboard
manager with history (e.g., Clipmate although there are free ones and
other paid ones). In fact, history is what makes it possible for me to
save multiple input fields in a page before clicking on Submit or moving
off and going back to that page: all the content I had put into those
fields can be retrieved from the clipboard manager's history.