This bug should cover the UI changes needed to save related files. Robin--Charley will need a string to go next to the checkbox. What the checkbox will turn on/off is whether extra files (JS, CSS, images, etc.) are saved with the html document being edited when the file is saved for the first time or when saved to a new location (save as is triggered).

Is this new UI under Edit|Preferences|Composer|General:When Saving Files ? Or, does it relate specifically to publishing? Can you describe a typical example of when this would be used and also when you wouldn't want to use it? Thanks.

While this is essential for publishing, it does apply to the "Save As" command, right, Kathy? But doesn't that implementation have to be done by (or at least invovle) the browser team as it applies to all modules using "Save As"? They already have a bug on that issue, don't they?

Do we have a tracking bug for all publishing tasks?

moving milestone

It's unclear what level of support we can have for individual files, but we will at least let the user decide whether or not to upload all the associated files and what directory to put them in at the destination location.

We support letting the user designate one subdirectory within a site to place image an other associted files. Keeping this bug open to improve this in the future for individual file control.

readd nsbeta1+ and reset milestone back to 1.0 This bug is NOT related to publishing. This is a checkbox for prefs so the user will have the choice of getting related pieces (images, css, js, etc.) when saving a file that was remote to a local disk (or from one local disk to another local disk). Please re-read the original description.

Expanding this to cover the two simple prefs I need to implement for saving and publishing.

Forget the new strings in dtd file

Comment on attachment 76326 [details] [diff] [review] patch v2 Looks fine. I was a little confused about the code that brings up the dialog, not noticing that it was modal and therefore won't return from openDialog() until the user has dismissed the dialog. Might not hurt to comment that, but it's your choice. I haven't had a chance yet to try it on Unix and verify that the prefs panel looks okay, but I will. r=akkana

On the issue of: + // XXX This doesn't work!!! GetDocumentURI is in nsEditorShell.cpp, but not in IDL It was a simple problem. The call should be: var oldLocation = GetDocumentUrl(); and everything works fine.

Comment on attachment 76326 [details] [diff] [review] patch v2 sr=hewitt

Comment on attachment 76326 [details] [diff] [review] patch v2 a=asa (on behalf of drivers) for checkin to the 1.0 trunk

checked in

the prefs are in...verified in 3/27 build however, the Save pref does not work. I did a File | Edit Page on www.abcnews.com and then I did a Save As to my desktop...I got images everywhere... Charley confirms this and he's gonna file a bug..

Code to use the "saveAssociatedFiles" pref in ComposerCommands.js doesn't work right if pref is set false. Reopening.

Don't save associated files if "save_associated_files" pref is "false'

This patch has 2 versions: 2nd is identical fix, just uses -w to show just the lines changed, not indent changes.

Update: use IOService to create new URI object

One more simplification in if...else blocks per reviewer comments.

Comment on attachment 76630 [details] [diff] [review] Fix v3 r=brade

Comment on attachment 76630 [details] [diff] [review] Fix v3 sr=alecf

Comment on attachment 76630 [details] [diff] [review] Fix v3 a=asa (on behalf of drivers) for checkin to the 1.0 trunk

checked in

verified in 4/2 trunk build.