Opened 9 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 reporter-feedback |
Focuses: | ui | Cc: |
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)
Change History (12)
#1
@
9 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
This ticket was mentioned in Slack in #core-customize by celloexpressions. View the logs.
9 years ago
#6
@
8 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.
#8
follow-up:
↓ 9
@
8 years ago
@helen Would you mind following up here, RE the comment that prompted this ticket: 34:ticket:31794? :-)
#9
in reply to:
↑ 8
@
8 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.
#10
@
4 years ago
- Keywords reporter-feedback added
I think this is no longer an issue, maybe since the customizer theme UI was updated in [41648]. I've tested on an iPad & iPhone, and the nav is visible as expected (not like the screenshot above), and only needs a single tap to the buttons. I think we can close this, but I'm tagging @helen for reporter feedback just in case.
#11
@
3 years ago
The theme modal part actually didn't change much with [41648] but since this was a device/browser-specific issue when originally reported, I would guess that changes in iOS have since resolved the issue. I don't have iOS but if anyone else with it can confirm this is now fixed, then this ticket can probably be closed.
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.