July 21, 2015 at 9:15 pm #476728
Quirky issue here. I have a team member box with a custom “Learn More” icon link that uses the ?iframe=true query to open a separate page in a lightbox, appended with a # anchor to scroll to the portion of that page that pertains to that specific team member. This works fine in most browsers/devices, but it’s not working in safari on iphone (only device I’ve tested safari on with this problem).
From googling, I found that following anchors in links is a common problem in Safari usually fixed by changing “domain.com/page#anchor” to “domain.com/page/#anchor” but this doesn’t solve the problem in this situation, and I’m guessing it has something to do with the java for the lightbox.
Any ideas on how to fix this?July 23, 2015 at 5:14 am #477479
It’s working fine on my end using both ipad mini and iphone 4 with latest version of Safari, the only difference from desktop is that you have to click twice, once to show the Learn More and once more to actually open the lightbox.
RikardJuly 23, 2015 at 5:39 am #477486
Yes the iframe loads on iPhone when you tap twice, my problem is that the iframe doesn’t scroll to the appropriate anchor. Clicking on the “learn more” link for Sean shows the info for Bruce on iPhone instead of scrolling to the anchor for Sean, but only on iPhone. I appreciate any help!July 25, 2015 at 6:33 pm #478674July 30, 2015 at 8:23 am #480545
Just checking in again on this, the problem still exists for ios. I think your previous reply didn’t really understand the issue. To clarify, I don’t have an issue opening an iframe lightbox in ios safari, my issue is that opening a link with an appended # anchor does not scroll to the appropriate anchor on the page that is opened in the iframe lightbox. But only in ios safari. Works fine everywhere else, but I need a solution to this and appreciate your help!August 1, 2015 at 11:27 pm #481721
Seems to be a Safari mobile restriction with anchors in iframed content, not exactly related to the theme or the lightbox script, i’ve made a test here you can check – http://output.jsbin.com/qohixikoxa/
One workaround you could try is to create a singular blank-page for each team member, or for the ones who will have a read more section.
- You must be logged in to reply to this topic.