WordPress.org

Make WordPress Core

Opened 5 years ago

Last modified 3 years ago

#31980 new defect (bug)

Customizer Theme Switcher Details Modal: previous/next/close buttons require double taps on IOS

Reported by: DrewAPicture Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: 4.2
Component: Customize Keywords: needs-patch
Focuses: ui Cc:
PR Number:

Description

Per comment:34:ticket:31794, there's an issue where double taps are required to trigger the previous/next/close buttons in the theme details modal.

Attachments (1)

IMG_8193.PNG (725.8 KB) - added by helen 3 years ago.

Download all attachments as: .zip

Change History (10)

#1 @helen
5 years ago

  • Summary changed from Theme Details Modal: previous/next/close buttons require double taps on IOS to Customizer Theme Switcher Details Modal: previous/next/close buttons require double taps on IOS

#2 @helen
5 years ago

  • Version set to trunk

This ticket was mentioned in Slack in #core-customize by celloexpressions. View the logs.


4 years ago

#4 @valendesigns
4 years ago

I can confirm this is still an issue, but it's not as bad as it sounds and it's only happening on an iPhone while the iPad works. What appears to be happening is that the modal needs to be focused before the click event will fire. So when you focus the modal by touching anywhere in it the navigation works as expected. It's really not a double tab on all click events, just the first one to focus the modal.

#5 @ocean90
4 years ago

Related: #33087

#6 @celloexpressions
3 years ago

Can someone with iOS check whether this is still an issue? #37661 reuses this same modal so the issue would persist with that fixed.

#7 @westonruter
3 years ago

  • Keywords reporter-feedback added

#8 follow-up: @DrewAPicture
3 years ago

@helen Would you mind following up here, RE the comment that prompted this ticket: 34:ticket:31794? :-)

@helen
3 years ago

#9 in reply to: ↑ 8 @helen
3 years ago

  • Keywords reporter-feedback removed

Replying to DrewAPicture:

@helen Would you mind following up here

Can't tell if it's still a problem because now the nav is covered up almost entirely, which seems to be a bug (and may exist as a ticket already, I did not search). See screenshot above.

Note: See TracTickets for help on using tickets.