Bug 13653 - Text overlaps on Get a Mac TV Ads page
Summary: Text overlaps on Get a Mac TV Ads page
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Evangelism (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac OS X 10.4
: P1 Normal
Assignee: Nobody
URL: http://www.apple.com/getamac/ads/
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-09 22:38 PDT by William Lynch
Modified: 2007-05-20 06:58 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Lynch 2007-05-09 22:38:22 PDT 
I didn't look too far into this one, but I'm going to assume that apple's website code should run in safari / webkit...

If you goto http://www.apple.com/getamac/ads/ and then scroll to the bottom. There are the four dots above the list of videos, click on the second, third, fourth, and then the first. The text below the videos will now be overlapping.
Comment 1 Matt Lilek 2007-05-11 08:40:41 PDT 
I can reproduce this in shipping Safari, ToT, Firefox and Opera which really makes me think this is a bug in the page itself, not a browser.
Comment 2 David Kilzer (:ddkilzer) 2007-05-12 16:39:27 PDT 
This bug needs a Radar, but it should probably be assigned to the web group if it's a web site issue.

Someone should test MSIE 6/7 to see how it behaves (just in case the bug doesn't appear there).

Bumping to P1 to raise profile of the bug.

Confirmed with a local debug build of WebKit r21274 with Safari 2.0.4 (419.3) on Mac OS X 10.4.9 (8P135).
Comment 3 David Kilzer (:ddkilzer) 2007-05-12 18:15:07 PDT 
See Bug 13702 for a different bug on the same page.
Comment 4 Matt Lilek 2007-05-12 18:39:49 PDT 
(In reply to comment #2)
> Someone should test MSIE 6/7 to see how it behaves (just in case the bug
> doesn't appear there).
> 

IE 7 behaves the same
Comment 5 David Kilzer (:ddkilzer) 2007-05-20 06:58:13 PDT 
Since this isn't a WebKit bug, I'm going to close it as RESOLVED/INVALID which is our standard procedure for closing bugs that can't be fixed in WebKit.  (See Bug 13702.)

Please note that the proper group has been notified of this issue.  Thanks!