Make WordPress Core

Opened 9 years ago

Closed 8 years ago

#33555 closed defect (bug) (invalid)

Customizer backward indicator always visible

Reported by: alvarogois's profile alvarogois Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.3
Component: Customize Keywords: reporter-feedback close
Focuses: ui Cc:

Description

When you're using some part of the Customizer, the backward indicator (“<”), below the close indicator (“x”), should probably be always visible, instead of only when hovered. That way, when someone is editing higher levels of a Customizer item, the way back is always evident, which, IMHO, would enhance the UX, even more when you're customizing a lot of items.

Attachments (1)

customizer-glitch-non_reproducible.png (12.9 KB) - added by alvarogois 9 years ago.
Customizer glitch (non reproducible)

Download all attachments as: .zip

Change History (7)

#1 @westonruter
9 years ago

@alvarogois Please upload your screenshot to the ticket. The Dropbox link is erroring. Thanks!

@alvarogois
9 years ago

Customizer glitch (non reproducible)

#2 @alvarogois
9 years ago

Thank you @westonruter. I couldn't reproduce the glitch with other themes, I suppose it's a theme specific (Bldr) glitch. Nevertheless, I'm attaching the screenshot, to document it.

#3 @westonruter
9 years ago

@alvarogois Can you check to see if the theme is enqueueing a stylesheet into the Customizer that is causing the problem? If so, please close the ticket :-)

#4 @celloexpressions
8 years ago

  • Keywords reporter-feedback added
  • Type changed from enhancement to defect (bug)

IS this confirmed to be a theme bug? I don't think there's a core issue here.

#5 @alvarogois
8 years ago

  • Keywords close added

I didn't spot it with other themes. It must be specific to Bldr. I cannot reproduce it right now.

Last edited 8 years ago by alvarogois (previous) (diff)

#6 @celloexpressions
8 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Okay, thanks for the report. Please reopen if you see it again in a reproducible way.

Note: See TracTickets for help on using tickets.