User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090307 Minefield/3.2a1pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090307 Minefield/3.2a1pre buildID: 20090307035349 when document contains img tags with onerror attr, [saving page/frame as complete] fires error event handler for each images, even though required images are existing there. [Saving as HTML only] does not fire error event. affect (not only, just example): web page creater can put onerror attr for img tags, to display alternate images other than alt-texts, when loading images got failed. in such a case, images, already displayed properly, would be replaced with alt-images unexpectedly after saving page. Reproducible: Always Steps to Reproduce: 1. enable JavaScript and make browser ready to load images. additionally on SeaMonkey, allow scripts to "Change images." 2. open testpage of URL. 3. confirm that two "Test images" and a "Alt image" are displayed. the last one is src-ed with dummy uri, so, has been replaced with "Alt image" by error handler scripts. it is expected behavior. 4. save page as complete. Actual Results: storing files is done properly. but after that, upper two images are replaced with "Alt images." also captions beside images are over-written to "error(number)." these changes are made by error handler scripts in document. Expected Results: nothing but related files are stored. extra error events fired on: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 buildID: 2009021910 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2 buildID: 20081201080242 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4pre) Gecko/20090308 SeaMonkey/2.0b1pre buildID: 20090308001413 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20090307 Minefield/3.2a1pre buildID: 20090307035349 work fine: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14 buildID: 2008120416 Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.20) Gecko/20081217 Firefox/2.0.0.20 buildID: 2008121709 this is happening to me always, but some says no. no other plat around of me, anyone try this ?

This bug seems to be caused by Bug 269125: http://bonsai.mozilla.org/cvsquery.cgi?module=PhoenixTinderbox&date=explicit&mindate=2005-08-17+00%3A00&maxdate=2005-08-17+22%3A00

Re-confirming because 4 months have gone since last comment. Re-confirmed on WinXP SP3 with: rv:1.9.1.1pre) Gecko/20090715 Shiretoko/3.5.1pre ID:20090715044728 rv:1.9.2a1pre) Gecko/20090715 SeaMonkey/2.1a1pre ID:20090715011709 rv:1.9.2a1pre) Gecko/20090715 Minefield/3.6a1pre ID:20090715043739 Also confirmed on Linux (Ubuntu 9.04 on VM Guest) with: rv:1.9.1.1pre) Gecko/20090715 Shiretoko/3.5.1pre ID:20090715031706 rv:1.9.2a1pre) Gecko/20090715 SeaMonkey/2.1a1pre ID:20090715060834 rv:1.9.2a1pre) Gecko/20090715 Minefield/3.6a1pre ID:20090715031745

Another 4 months have gone since last comment. This is still existing. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.3a1pre) Gecko/20091118 Minefield/3.7a1pre ID:20091118051933

This is still existing. Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100912 Firefox/4.0b6pre ID:20100912041924

This is still existing. Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:12.0a1) Gecko/20111222 Firefox/12.0a1 ID:20111222031055 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20111222 Firefox/12.0a1 SeaMonkey/2.9a1 ID:20111222003001 Mozilla/5.0 (X11; Linux i686; rv:12.0a1) Gecko/20111222 Firefox/12.0a1 ID:20111222150239 Mozilla/5.0 (X11; Linux i686; rv:12.0a1) Gecko/20111221 Firefox/12.0a1 SeaMonkey/2.9a1 ID:20111221003001