RESOLVED DUPLICATE of bug 42230 42838
Masthead of yahoo.com disappears
https://bugs.webkit.org/show_bug.cgi?id=42838
Summary Masthead of yahoo.com disappears
Nicholas C. Zakas
Reported 2010-07-22 11:04:26 PDT
Created attachment 62316 [details] Masthead disappearing on yahoo.com Hi, this is Nicholas from yahoo.com. Our QA noted that in Safari 5 on Mac OS X 10.6 only, the masthead of yahoo.com disappears. Repro steps: 1. Go to www.yahoo.com 2. Move your mouse over "Mail" on the left rail. 3. Click the "Open Quickview" button. 4. Note that the masthead disappears. Some other important things to note: * The layer that pops up does have a Flash ad on the right side. * The layer pops up over another Flash ad that's already on the page. * Our engineers narrowed the problem down to the combination of Safari 5 + Mac OS X 10.6 + Flash player 10,1,53,64. Masthead disappears with this user-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-us) AppleWebKit/533.16 (KHTML, like Gecko) Version/5.0 Safari/533.16 Masthead is fine with this user-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_8; en-us) AppleWebKit/533.16 (KHTML, like Gecko) Version/5.0 Safari/533.16 We've been unable to come up with a workaround for this bug and we're particularly troubled (clearly, since Search is a huge part of our user experience). It seems like there are a couple of others expressing similar problems: https://bugs.webkit.org/show_bug.cgi?id=41701, but there doesn't appear to be any movement on this. Please help. :)
Attachments
Masthead disappearing on yahoo.com (165.11 KB, image/png)
2010-07-22 11:04 PDT, Nicholas C. Zakas
no flags
Nicholas C. Zakas
Comment 1 2010-07-22 12:12:17 PDT
After testing on Webkit nightly (6533.16, r63404), issue appears to be resolved. Any idea when this will get pushed out as part of a Safari update?
Mark Rowe (bdash)
Comment 2 2010-07-27 18:31:12 PDT
This was fixed in r63283, which makes this the same underlying issue as bug 42230. *** This bug has been marked as a duplicate of bug 42230 ***
Note You need to log in before you can comment on or make changes to this bug.