Closed Bug 299431 Opened 19 years ago Closed 19 years ago

Top frame of frameset not painted when opened in tab

Categories

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

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 283959

People

(Reporter: pledman, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050701 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050701 When doing image searching with images.google.com (also seen on A9.com and elsewhere), when opening an image link in a new tab in the background, the resulting frameset does not paint properly. The first time you view that tab, the top frame, which is from Google, shows bleed-through from whatever frame you were last in. The bottom frame, which is from the originating site, shows properly. When you click back to another tab and then click into the problem tab, the top frame is then painted properly. Reproducible: Always Steps to Reproduce: 1.search for an image on images.google.com 2.command-click on a resulting image to open the "Google Image Result" frameset in a background tab 3. Watch the top of your screen. Actual Results: When you click into the new tab, the top of the display window shows the pixels from the previous tab being viewed, while the bottom part of the display window shows (correctly) the source site of the image you're viewing. Expected Results: Top frame should have shown the Google image information, "see full-size image" and so on. The workaround is ok, but the problem is very ugly. I can provide screen shots on request.
Whiteboard: DUPEME
Also dupe of 284258 *** This bug has been marked as a duplicate of 283959 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
Product: Core → Core Graveyard
Component: Layout: HTML Frames → Layout: Images
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.