Does anyone know the timeout times for Google Chrome, Mozilla Firefox, IE 9, and Safari?
Related
I need to make a web browser which should keep WkWebView's backFowardList even after app is closed so it really works like Safari, Google Chrome or like other proper browser apps.
However, WkWebView's property backFowardList is a readonly property.
How did Google Chrome, Opera or other proper browser apps replicate this function?
I am trying to debug my web based HLS player (with HTML5 tag) and would like to monitor the network request to fetch the segments of the stream. This works fine in all desktop browsers (safari, chrome, firefox), and works with the OSX Safari, as well.
But when I connect to a iOS Safari (Simulator or real iPhone), only the request of the m3u-file shows up in the network monitor, not the requests to the segments of the stream.
Is there a way to monitor those requests on iOS Safari?
The reason I want to do this is trying to avoid automatic loading of segments while the player is paused/stopped. This works fine with hls.js, but I am not sure how iOS Safari handles the preload=none attribute. Although here Apple says that "Safari on iOS never preloads", this does not seem to be true when pausing the player. (see https://developer.apple.com/documentation/webkitjs/htmlmediaelement/1633059-preload, too)
Thanks!
P.S.: I tried to get any information in Apple's forums before, unfortunately without any success (https://discussions.apple.com/message/32027089#32027089).
You can monitor these requests like any other. I recommend Fiddler... It works as a proxy server and can be used to monitor or edit traffic, even with HTTPS. For lower level debugging or cases where you can't use a proxy, use a packet sniffer like Wireshark.
We have a website in Wordpress, using a home-made theme. Some weeks ago, we noticed some page load time issues of our website, reported in Google Analytics. If we check the website using speed tests as Pingdom, Webpagetest and GTMetrix, we don’t see any performance issues. We checked the Analytics data, the main issues (average load time) are in iOS – Safari browsers (iPhone, iPad, in-app). If we check the specific data we find that, for example, one page could have 30 seconds page load time, but is not always and it happens for a single user using Safari 9 browser in Apple mobile device.
One more thing, we tested using those devices, but nothing weird happened.
Any idea what could be happening.
It's not just about the mobile device but the carrier also.
Apparently your carrier is better than the other(s).
The second biggest issue with mobile carriers is the number of simultaneous requests allowed. A desktop will download about 6 page resources simultaneously. Mobile, one, maybe two.
The biggest issue is the tower will often drop the radio signal between the phone and the tower between request.
so with mobile it is very important to minimize the number of requests per page.
I've a couple of questions and I can't find answers anywhere.
1- Does Google Chrome use UIWebView for rendering and showing web pages?
2- If yes (someone says chrome is just a UIWebView) why my web browser (I created a simple web browser with UIWebView) is not as fast (and stable) as Google Chrome. What is difference? What do they add for improving app performance?
3- When I open 10 tabs in chrome, does that mean there are 10 different UIWebView in background?
Chrome is faster because of their network layer implementation which does many optimisations/caching etc. E.g. DNS pre-resolve, TCP pre-connect,Resource prefetching, Page prerendering etc
Read about it more from here
I have a small iPhone app that consumes streaming video. With Apache on my Macbook, I have been able to get it working without any trouble. i.e., I've deployed the .m3u8 and .ts files and the server is correctly streaming the files and the phone app is displaying the video too.
Now I try to replicate this on an apache server running on a Windows Server, and can't get it to work. I've got the correct settings in mime.types for both content types.
Using the mediastreamvalidator locally returns verified ok status. Running it on the remote stream hangs it.
access.log shows the first five segments being requested and then nothing. If I try to access from Safari it shows the controls and the trackbar updates up to 8 seconds and then nothing. I have seen this question but that doesn't seem to be the problem.
In the browser, the GET statements for both local and remote return identical results.
Safari plays from the local URL, Firefox and Chrome don't and neither gives any errors.
Any help would be much appreciated!
Turns out you need to use the "-no-floating-point-duration" and "-iframe-index-file none" parameters to mediafilesegmenter. Still doesn't work in Firefox or Chrome. But that's not a problem for now.