29272 - Need a warning dialog for non-matching charset in save as text

Status: NEW

(Core :: DOM: Editor, defect, P5)

Description

[Frank Tang]

If we decide to save page as text from editor and there are some text cannot be 
save into that charset, we should have a warning as in bug 28908

Comment 1

[nhottanscp]

I wonder if this is needed for editor saveas. Unlike mail (28908), the file is 
saved locally and the user can always save as a different file and different 
charset.
Also, even if a character is out of charset range, it still can be saved as NCR 
and that is viewable by seamonkey and MS browser.
Adding akkana to cc, since we need to ask editor group for implementation once 
we decide to do this.

Comment 2

[Akkana Peck]

Adding cmanske since he's the editor dialog guru.

Comment 3

[nhottanscp]

I found this is in the internal editor i18n UE spec which is going to be 
published soon. We can decide whether do this feature during the review of that 
document. Quoting from the spec.

>Warn that the selected choice is not the best choice for the input data and 
>may lead to documents being unreadable by some browsers. Cancel: 
>Ask to cancel and save in the most natural charset for the input data 
>(if this info is available to the Editor) or UTF-8. or OK: 
>save  in the chosen charset but with the use of NCR's where necessary. 

Comment 4

[Charles Manske]

It is very easy to put up a dialog once you know you need one. 
The EditorShell has methods for that -- all you need is a string in the 
from a string bundle for the message and call ConfirmWithCancel if you want
a Yes/No/Cancel type of dialog, or Confirm if you want just Yes/No.

Comment 5

[nhottanscp]

Moving to M18, we are not sure if this warning is needed for HTML save as.

Comment 6

[Frank Tang]

remove futre and add intl. Keep P3 and move to yokoyama since this composer feature

Comment 7

[Roy Yokoyama]

Updating the target milestone.

Comment 8

[Frank Tang]

I think both roy and me are off mozilla for more than 2 years. If these bugs are
still here now, I think the real stauts is 'won't fix'. If you want to reopen
it, please find a new owner for it first. 

Comment 9

[Travis Chase]

Mass Reassign Please excuse the spam

Comment 10

[Travis Chase]

Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all
the spam is his fault feel free to tar and feather him

Comment 11

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority and severity.

If you have reason to believe this is wrong, please write a comment and ni :jstutte.