Make WordPress Core

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#23535 closed defect (bug) (wontfix)

Twenty Thirteen: Title overlaps expanded search box in narrow layouts

Reported by: johnbillion's profile johnbillion Owned by: lancewillett's profile lancewillett
Milestone: Priority: normal
Severity: normal Version: 3.6
Component: Bundled Theme Keywords:
Focuses: Cc:


See attached screenshot.

Attachments (1)

2013-02-19 17.05.46.png (86.2 KB) - added by johnbillion 11 years ago.

Download all attachments as: .zip

Change History (10)

#1 @lancewillett
11 years ago

  • Keywords needs-patch added
  • Milestone changed from Awaiting Review to 3.6

#2 @johnbillion
11 years ago

  • Summary changed from Twenty Thirteen: Expanded search box overlaps title in narrowest layout to Twenty Thirteen: Title overlaps expanded search box in narrow layouts

#3 @obenland
11 years ago

I suggest wontfix for that. It is simply not possible. :(

The container around the search field has z-index 2, the title z-index 3. Based on that, the title will always be displayed over anything else in that container. Giving the search field a higher z-index value won't help either.

It might get fixed if we end up deciding to exchange the title with a collapsed version of the menu. But that is for a different ticket.

#4 @DrewAPicture
11 years ago

As-is, this is pretty lame. @obenland has a point about rearranging z-indexes not solving the problem.

That said, we need to figure out an alternative for this whether that means swapping out the site title for the menu or rearranging the way the elements are grouped so a z-index override is possible.

#5 @SergeyBiryukov
11 years ago

#23615 was marked as a duplicate.

#6 @lancewillett
11 years ago

  • Owner set to lancewillett
  • Resolution set to fixed
  • Status changed from new to closed

In 23533:

Twenty Thirteen: disable fixed navbar on small screens. Props obenland, fixes #23647.

Also closes #23526, #23535, and #23566

#7 @lancewillett
11 years ago

  • Keywords needs-patch removed
  • Milestone 3.6 deleted

#8 @SergeyBiryukov
11 years ago

  • Milestone set to 3.6

If the resolution is "fixed", milestone should stay.

#9 @lancewillett
11 years ago

  • Milestone 3.6 deleted
  • Resolution changed from fixed to wontfix

My fault, I closed with a commit message.

Note: See TracTickets for help on using tickets.