Back to Home directly in WKWebView - ios

I'm working with a WKWebView that shows a WebSite.
In the WebSite I have embedded some Google Slide but the full screen mode doesn't works on iOS (known bug from years but I can't find a solution yet) so I have to redirect at the Google Slide URL (outside of my WebSite).
The issue is that if a slide has 50 pages, and I'm at last of these, when I have to go back I'm at slide 49 and I have to go back 49 times for return to the home (every slide has a different URL).
If the slide is not in full screen and I'm at slide 50 when I go back I'm directly at the home.
How can I improve this situation? Is possible to return directly at the home also if I'm in full screen? Thanks in advance

Related

the last page in the stack Route will pop in Flutter web in ios(open issue on github)

I have a flutter web app, when I open my web app in my iphone 7 , the starting html page is still behind the Route stack pages, I mean when I swipe horizontally(popping the pages in iphone => I mean like backbutton in android but swiping horizontally from left to right in iphone) the white screen(the started html page) shows and the web app rebuild itself and after that when I swipe horizontally again, it seems that the white screen is gone and everything works fine, but everytime that I close the web app and reopen it again, this senario repeats.
here is the video of what I mean:
https://www.dropbox.com/s/bo332qjlawsbe4a/RPReplay_Final1646636021.mov?dl=0.
be careful, I don't mean that I want to omit the first white screen,my problem will be from the first screen(orange screen) and this senatio is not happening in android devices and browsers.
thanks a lot.

Script to Prevent Google Slides from Opening New Tab When Touched vs. Clicked

I created a digital Pop It in Google Slides with about 120 slides, which is Published to the Web from the File menu. Each slide has a transparent image overlaying it that is linked to Next Slide. When the user clicks with their mouse on the transparent image, it proceeds to the next slide, and works as it is expected to.
However, when the user has a touch screen, and then presses on the screen to advance it to the next slide, it opens up a new tab and stays on the same slide, and does not advance to the next slide.
Does anyone know of a script that can turn this off so that if a user is pressing on the screen to advance the slide, it will actually work? Or is this a bug?
Thanks for your help!
FYI: the slide may take a little while to load.
You can view the slide here.
I tested it out and apparently it might be a bug. I removed the transparent image with the link to the next slide and the issue is the same.
I recommend you to report it on:
https://issuetracker.google.com/issues/new?component=191598&template=824111
And describe the issue.
As a workaround, if you open the Google Slides app, it works as intended.

How does iOS 13 Safari link preview work?

In iOS 13 Safari, when you long press on a link, you see a preview of the linked page, along with some menu items. If you tap the preview, you navigate to that page.
Now, I see how to intervene in the long-press-and-preview process. This used to be peek-and-pop, but in iOS 13 that's deprecated and we're supposed to use func webView(_:contextMenuConfigurationForElement:) and so forth. Fine, but how would I imitate what Safari does?
The problem is that as my preview provider I have to supply a view controller. So I'm going to need a different view controller with a web view showing the linked page. Okay, I can do that. But then when the user taps the preview to dismiss it, I want to respond by loading the same linked page into my real web view.
But that's the problem. That loading takes time. In Safari, by contrast, when you tap the preview, boom, there's the same page already loaded. How do they do that? How would I do the same thing? How can I load the page into a different view controller, cache it, and communicate that cached page back to my real web view?

Full-screen display on iPad / Display as web app [duplicate]

This question already has answers here:
How do you keep an iPhone/iPad web app in full screen mode?
(6 answers)
Closed 8 years ago.
I'm trying to figure out the most efficient approach to tackle an issue. I have wonderful WP themed website that I want to show full-screen on my iPad. Here's how it currently operates:
Once a user has saved the website to their iPad via ‘Add to Home Screen’, the site will launch full-screen (absent any Safari interface) when that icon is pressed. However, a new tab is created with Safari interface items visible once the user clicks on any menu item. I want to keep the full-screen experience (without tabs) while the user remains within the site. I only need this to work when launched from home screen icon in the latest iOS.
1) What is causing the site to launch a new tab? Default mobile safari action due to lack of full-screen code, the way the nav URLs are coded, or other?
2) Is it just a matter of adding some header code to the remaining pages (via child theme or directly to the theme templates)?
Here is the website: http://www.sofla360.com
I've dabbled with the iOS full-screen code previously, but nothing very complicated nor with a WP theme. Figured I'd start here in case anyone had some insight on this topic.
Thanks!
The code I found here works with 99% of my WP-themed website. I created a child theme and placed the code in the head section of the header.php file.

Two Page Curl Effect in iPad

I am using the Leaves project to move from one pdf page to another it is working fine. Now the page curl is from left to right and from right to left like a note book. Now the effect was to turn a single page but i want to turn the two pages .one page has to display in left side and another page has to display in right side.
You should probably use UIPageViewController, unless you're trying to support iOS 4. UIPageViewController supports having the spine in the middle of the screen so you can see two pages at once. I don't know if Leaves is relevant anymore since there's a better solution built right into iOS 5 and up.

Resources