Closed Bug 448022 Opened 16 years ago Closed 16 years ago

Image embedded into an HTML page using the img tag is not displayed if not already cached

Categories

(Core :: Graphics: ImageLib, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: brunogirin, Assigned: joe)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-GB; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-GB; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1

When loading the URL above, the image in figure 8 isn't displayed if it is not already cached by the browser.

Reproducible: Always

Steps to Reproduce:
1. Empty the browser cache: Firefox -> Preferences -> Privacy -> Clear Now; deselect everything except 'Cache' and click 'Clear Private Data Now'
2. Go to http://dev.w3.org/csswg/css3-background/#the-border-radius
3. Scroll down to figure 8
4. All images on the page are displayed normally except Figure 8: this one is not visible
5. Load the image in the figure explicitly by requesting http://dev.w3.org/csswg/css3-background/smooth-radius.png
6. Click the 'back' button on the browser or go back to http://dev.w3.org/csswg/css3-background/#the-border-radius
7. Figure 8 is now displayed properly
8. Close Firefox
9. Go back to http://dev.w3.org/csswg/css3-background/#the-border-radius
10. Figure 8 is displayed properly
11. Repeat the steps above, clearing the cache first and the figure will fail to display again
Actual Results:  
Step 4: the content of figure 8 (a PNG image) is not displayed.

Expected Results:  
Step 4: the content of figure 8 should be displayed when the page is loaded for the first time.

I have only tried on Mac OS-X Leopard so it may be limited to that platform. I cannot tell whether the image is actually loaded and just not displayed or if it is not loaded at all.
I saw only one time that the image failed to display (on Windows, using a new profile), but was not able to repeat it. Clearing cache didn't help to repeat it, here.
Ok, I see now that not Figure 8 is missing but Figure 7, so it is a All-All bug.
OS: Mac OS X → All
Product: Firefox → Core
QA Contact: general → general
Hardware: Macintosh → All
Version: unspecified → Trunk
(In reply to comment #2)
> Ok, I see now that not Figure 8 is missing but Figure 7, so it is a All-All
> bug.
> 

Ria: that's interesting, on my machine it is consistently figure 8 that is missing. Could it be related to threading? And in this case, is it significant that my machine is a dual-processor box? If that's any use, here is the hardware overview of my box:

  Model Name:	Power Mac G5
  Model Identifier:	PowerMac7,3
  Processor Name:	PowerPC G5  (3.1)
  Processor Speed:	2.7 GHz
  Number Of CPUs:	2
  L2 Cache (per CPU):	512 KB
  Memory:	8 GB
  Bus Speed:	1.35 GHz
  Boot ROM Version:	5.2.4f1
It appears to affect fast computers more than slow computers. I can be mistaken, but it seems related to the pref network.http.max-persistent-connections-per-server. The page becomes quite a mess with the current value 6, pictures are not on the right spot and when I change it back to the value 2 like it used to be the page is not broken anymore.
Component: General → HTML: Parser
QA Contact: general → parser
Flags: blocking1.9.1?
Joe, can you look into this? It sounds like this server is having issues, but confirming that, and maybe why would be awesome to know what's really going on here.
Status: UNCONFIRMED → NEW
Component: HTML: Parser → ImageLib
Ever confirmed: true
QA Contact: parser → imagelib
Assignee: nobody → joe
Marking blocking, pending investigation.
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P3
No matter what I do, I can't reproduce this. Maybe the server has been fixed?

Reporter, can you still reproduce this?
Haven't heard back in two months, so I'm marking this one incomplete. It was probably a server issue, but in case it wasn't, feel free to re-open.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.