Open Bug 194267 Opened 23 years ago Updated 4 years ago

Performance degradation in rendering frames in Sun javadoc

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

x86
Linux
defect

Tracking

()

People

(Reporter: DomIncollingo, Unassigned)

References

()

Details

(Keywords: perf)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030219 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030219 When Mozilla (build 2003021905) renders Sun's javadoc api index at http://java.sun.com/j2se/1.4.1/docs/api/, there is a 1 - 2 second lag between the time when the main frame is rendered and the time when the frame on the bottom left (All Classes) is rendered. Mozilla 1.0.2 renders all three frames on this page at the same time. Reproducible: Always Steps to Reproduce: 1.Navigate to http://java.sun.com/j2se/1.4.1/docs/api/ 2.Notice that when this page renders, there is a 1 - 2 second lag between the time when the main frame (marked 'Java Platform Standard Edition, v 1.4.1') renders and the time when the frame on the bottom left (marked 'All Classes') renders. 3.Use the Mozilla Back button to return to the previous page. 4.Use the Mozilla Forward button to redisplay the page at java.sun.com/j2se/1.4.1/docs/api from cache. 5.There is still a 1 - 2 second delay between the rendering of the various frames when this page is redisplayed from cache. When the above steps are repeated using Mozilla 1.0.2, there is no noticeable delay between the time when the various frames on this page are rendered. In particular, if step #4 (above) is repeated using Mozilla 1.0.2, all three frames on this page appear to render simultaneously when the page is redisplayed from cache (using the Forward button).
I see this with linux trunk 20030220, but I also see it with 1.0.2
Keywords: perf
Assignee: layout.html-frames → nobody
QA Contact: madhur → layout.html-frames
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.