125234 - add an alert to "save page as" dialog

Status: RESOLVED INCOMPLETE

(Firefox :: File Handling, defect)

Description

[marlon bishop]

Need to add an alert to the Save As dialog warning users about potential
changing of HTML data when saving in the default format. see <a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=116008">116008</a> for rationale.

also related to: <a
href="http://bugzilla.mozilla.org/show_bug.cgi?id=124996">124996</a>

Comment 1

[marlon bishop]

changing component ->

Comment 2

[Jeremy M. Dolan]

The dialog also needs to mention all dynamic DOM modifications will become fixed.

I suggest the dialog appear before "save page as" is shown, because poping up
both the save dialog and an alert together can be disorienting. So first...

+-------------------------------------+
| [i] There are now two ways to save  |
| a file, blah blah blah.             |
|                                     |
|  [X] Don't show me this again       |
|                                     |
|              [ OK ]                 |
+-------------------------------------+

With don't show again checked by default, then after you click OK, save page as
pops up.

Changing summary from save as to "save page as", because this doesn't apply to
the "save link as" dialog. Although there's likely an RFE on letting you save
complete pages via 'save link as'.

Comment 3

[Peter Trudelle]

nsbeta1+ per ADT triage team.  Marlon, will you supply a dialog mockup?

Comment 4

[Jaime Rodriguez, Jr.]

Why is this dataloss?

Comment 5

[marlon bishop]

this is dataloss because the user in the default save format will not get an
HTML document as it was actually served from the site - we localize all of their
HTML links for them.  therefore we need a dialog which alerts them before they

peter - i can't provide a dialog mockup atm, but we should contact Jatin or docs
to write something which sounds easy to understand yet informative for the
experienced user.  

Comment 6

[Nathanael C. Nerode]

The format-to-save-in option in the Save As dialog box is about the last place
I'd have thought of looking, when webpages saved improperly (with altered URLs),
because I'm used to that actually referring to the file format, and there's only
the one MIME type for HTML.

So I agree that something needs to be done to avoid this; it behaves in an
unexpected manner (to me), and it's not obvious where to look to fix it.  If it
were obvious where to look, I'd be happy. :-)

Comment 7

[Jatin Billimoria]

My suggested wording carried over from Bug 116008:

You are saving this page using the "Web Page, complete" option. Saving a page
using this option allows you to view it as originally shown with pictures, but
may not keep the link structure of the original page. To save an HTML page in its
original format without pictures, please select "Web Page, HTML only" from the
"Save As" dialog box.

Comment 8

[Peter Trudelle]

ADT2

Comment 9

[Peter Trudelle]

ADT3

Comment 10

[Peter Trudelle]

Mass moving nsbeta1+/adt3 bugs assigned to Navigator team engineers out to
target milestone 1.0.1.  Please confine your attentions to driving down our list
of TM 1.0 bugs for beta.  Better to help, debug, or test one of them than fix
one of these.

Comment 11

[scottputterman]

Changing nsbeta1+ [adt3] bugs to nsbeta1- on behalf of the adt.  If you have any
questions about this, please email [e-mail].  You can search for
"changing adt3 bugs" to quickly find and delete these bug mails.

Comment 12

[scottputterman]

Changing nsbeta1+ [adt3] bugs to nsbeta1- on behalf of the adt.  If you have any
questions about this, please email [e-mail].  You can search for
"changing adt3 bugs" to quickly find and delete these bug mails.

Comment 13

[Brant Gurganus]

By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity.  Only changing open bugs to
minimize unnecessary spam.  Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.

Comment 14

[Vedran Miletic]

retargeting

Comment 15

[timeless]

.

Comment 16

[Andrei Purice]

Is this issue still occurring or can it be closed?

Comment 17

[Andrei Purice]

Marking this as Resolved > Incomplete due to the lack of info.
If anyone is able to reproduce this issue re-open it or file a new bug.