135365 - context-menu : 2nd action taken on an image fails

Status: VERIFIED WORKSFORME

(SeaMonkey :: UI Design, defect)

Description

[Bjarne D Mathiesen]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.9+) Gecko/20020402
BuildID:    2002040208

If you save an image and then need to save it a second time, you get an error
message (see attachment). This error message only happens if the image in
question is of a certain (big) size. Some of the preview-images also display
this behaviour, but it a sure thing for the images themselves.

Reproducible: Always
Steps to Reproduce:
1. go to one of the galleries in the URL given
   you'll need to register (free)
   sorry - but I don't have an example website that doesn't need registering
2. save an image
3. save the same image again immediately after

Actual Results:
you get an error message (see attachment)

Expected Results:
you ought to be able to save the same image as many times as you want

Additional information:
I think this might be related to the disk-cache

Comment 1

[Bjarne D Mathiesen]

Attachment: error message after step 3

Comment 2

[Paul Wyskoczka]

qa -->  [e-mail]

Comment 3

[Bruce Tomlin]

Same here.  I noticed it with a nightly build last week, then downloaded OS X
Carbon build 2002041216.  Just now it happened again when trying to save the
main image from http://www.megatokyo.com/.  Clearing the memory and disk caches
does NOT make the problem go away.  You must quit and re-launch Mozilla.

For extra fun, try File->Save Page As, click Cancel (that's right, you don't
actually need to save the page!), then hit reload.  It will now say "The file /
cannot be found.  Please check the location and try again."  So this is may not
solely be a problem with images.

And when the image was messed up to where it would not save, I could still hit
reload and see the image on the page.

Comment 4

[Bruce Tomlin]

More experimentation.

Just tried it on http://www.cnn.com/.  Did right-click-"Save Image As", then
Cancel.  Hit reload and image did not show up.  So it is not consistent whether
the image shows up on reload or not.  Then I did File->Save Page As and hit
Cancel.  Hitting reload said that "/ could not be found".

Went to http://www.foxnews.com/ and tried it again.  Problem did not show up
when trying to save images repeatedly, but Save Page As problem did show up. 
After trying a few other web sites, it seems that even though images may
successfully save twice, I can always seem to get a page to fail to save twice.

Comment 5

[Bruce Tomlin]

I did some regression testing, and this bug seems to appear between Mac OS X
Carbon builds 2002-03-26-08 and 2002-03-28-08.  I will try to see if this
appears in the Win32 build when I have time.

And to reiterate, this is not an images-only problem.  It shows up most easily
by doing File->Save Page As; Cancel; File->Save Page As.  It also does not seem
to be a caching problem, as clearing the caches does not make the problem go away.

This is a really annoying bug, and I think it should be a 1.0.0 blocker.

Comment 6

[Bruce Tomlin]

I identified the regression build number last week.  So what does it take to get
this bug marked as confirmed already?

And FWIW, this bug seems not to affect Win32 builds (verified with 2002041011).
 I have not verified this with the OS 9 version, but the original submitter
marked this as an OS 9 bug.  I myself have encountered it as an easily
reproducible bug with the OS X build.

Comment 7

[Bjarne D Mathiesen]

I've changed the summary - !!!NOT!!! related only to "Save Image"

1) context-menu: "View Background Image"
   context-menu: "Save Image" -> fails

2) context-menu: "Save Image"
   context-menu: "View Image" -> fails - also in reverse order

3) in you have a series of images like 
   http://[site]/[folder]/image1.jpg ... image9.jpg
   and you manually edit the URL-bar to get to all of them
   when having gotten to an image do context-menu : "Save Image"
   now, the "Back"-button fails on any of the images

Comment 8

[Bjarne D Mathiesen]

seems to be implicitly fixed in build 20020626 for MacOS X
but this is a 1.1a build
now, we-ll have to see if this resolution migrates into 1.0.1

Comment 9

[Bjarne D Mathiesen]

ought to be resolved as WFM - issue hasn't been seen for a looooong time
can somebody please do it for me ???
I've changed email account and haven't got the old code to login anymore

Comment 10

[sairuh (rarely reading bugmail)]

yep, w4m with recent trunk bits on OS X.

Comment 11

[sairuh (rarely reading bugmail)]

and vrfy.