Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#24118 closed defect (bug) (invalid)

Twenty Thirteen: Footer Margin top in Safari 6.0.4

Reported by: RDall Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.6
Component: Bundled Theme Keywords:
Focuses: Cc:


Running the latest release of Safari Version 6.0.4 and WordPress 3.6-beta1-24023 Twenty Thirteen shows a margin-top: 3221px in footer. This pushes the footer down in the page.

See Screenshot http://cl.ly/image/1y1n030P1m1t

This space only affects the Safari as in FF and Chrome there is overlay of the sidebar on top of the footer. See Screenshot for FF 20.0 http://cl.ly/image/0L0Q3e0M2517

Should be noted I also didn't see this issue in the previous version of Safari but didn't see the issue pre beta1-24023 either… So not sure which could cause the issue. 

Change History (6)

#1 @lancewillett
5 years ago

  • Milestone changed from Awaiting Review to 3.6

Can you be more specific in how to repeat this? With widgets in footer or sidebar, no sidebar widgets, all screen sizes?

#2 @RDall
5 years ago

Widgets in footer. I am also using the Monster Widget in the right sidebar… 

This only happens in Safari on my 17" iMac with a resolution of 1680 x 1050 and on my 15" Windows7 with a screen resolution of 1366 x 768. There is no problem on my 27" iMac with 2560 x 1440 resolution.

I here is and annotated screenshot of the full page: http://cl.ly/image/2t1k2O3x1A41

It might be best to download this one and zoom for detail.

#3 @obenland
5 years ago

I can't repeat it in Safari 6.0.3.

#4 @lancewillett
5 years ago

@RDall can you reproduce on more than one Twenty Thirteen-themed blog? Like not just your sandbox, but other demos or test sites? Like http://themebuster.wordpress.net/?

#5 @RDall
5 years ago

Can't look till later… But I will check themebuster.wordpress.net for both trac tickets and reply… 

Version 0, edited 5 years ago by RDall (next)

#6 @lancewillett
5 years ago

  • Keywords needs-patch removed
  • Milestone 3.6 deleted
  • Resolution set to invalid
  • Status changed from new to closed

Pretty certain this is a local thing with RDall only. Closing as invalid.

Note: See TracTickets for help on using tickets.