Checked caniuse.com but I couldn't find anything regarding support for picture element in Chrome on iOS. What's the current support status and where can I find some more info?
http://caniuse.com/#search=picture
Chrome on iOS uses WkWebView which is WebKit. From your link it looks like Safari iOS supports it so Chrome on iOS should too.
Related
We set up universal links that work on android but don’t work on iOS when using Safari as the main browser. However, when we tested on Chrome it did work. Is this a known issue
Sometimes i check browser support features on Can I Use website. Now i looked at touch events compatibility and realised that iOS Safari support this feature, but Safari doesn't. What is the difference between Safari and iOS Safari on caniuse.com? As far as i know Safari browser is tied to the iOS and is not supported on Windows/Linux, so it should point to same browser. Maybe it's divided to mobile and desktop versions? I couldn't find any answer on their website and on other sites as well.
I enclose an image as well (support may change in the future):
Safari refers to desktop Safari on a Mac, whereas iOS Safari is Safari on an iOS device.
I have a URL that is working fine with Safari on iOS11 (Beta) Audio/Video is working fine.
But when I load this URL with WKWebView it gives me an error "Incompatible Browser" and when I check my browser version in WebKit it shows "WebKit based browser on iOS 11"
So the question really is, has Apple included this change in the WKWebview webkit (which should be the same as Safari) for the developer BETA of iOS 11?
Update: WebRTC Support is coming in iOS14.3 (Beta) 🎉
Learn more here: https://webkit.org/blog/11353/mediarecorder-api/
From iOS11+ :
WebRTC is partially supported in WKWebView, and fully supported in the Safari App browser.
Explained:
WebRTC has three main JavaScript APIs:
MediaStream (aka getUserMedia)
RTCPeerConnection
RTCDataChannel
For apps running inside Safari App, iOS11+, all WebRTC APIs are supported. That includes getUserMedia. Be sure to use adapter.js library for best compatibility, since each browser - including Safari - uses a different name for its implementation. For example, in Safari it's navigator.mediaDevices.getUserMedia().
But, when using WKWebView or SFSafariViewController, it's a different story:
Both RTCPeerConnection and RTCDataChannel are supported and working.
getUserMedia is not supported yet, for "security reasons". It most probably won't be available before the next major OS release, which would be iOS 12 in September 2018.
You can still stream video & audio from local storage or consume live media captured by a peer. Hopefully in iOS 12 we'll see some progress...
I did a bit of digging in the WebKit sources last night, and it looks like the WebRTC/MediaCapture stuff is all gated behind a preference that's only accessible via a private API. There was also a commit that mentioned something about apps needing to handle all the setup for A/V permissions.
In any case, the result is that getUserMedia doesn't work in WKWebView, even on iOS11 (beta 4, at least) :(
I've filed a radar (rdar://33571214 and http://www.openradar.me/33571214) and encourage everyone else to do the same.
I have done some tests with iOS Beta 4 and it seems that even WKWebview nor UIWebview don't support getUserMedia as a WebRTC API.
Can someone confirm this?
When using my dev tools it shows perfectly for mobile but on my actual mobile my apps do not show correctly. Is this a bug with the iphone 6?
My meta tags
https://github.com/jwlindsey/jwlindsey.github.io
if you want to look at the index file or css. I am pretty sure I have it correct though.
Same problem encountered.
I read their documentation https://getbootstrap.com
Browser support
• Dropped IE8, IE9, and iOS 6 support. v4 is now only IE10+ and iOS 7+. For sites needing either of those, use v3.
• Added official support for Android v5.0 Lollipop’s Browser and WebView. Earlier versions of the Android Browser and WebView remain only unofficially supported.
We have an offline-enabled web app that up until now has worked in both Chrome and Firefox on iOS (but not Safari).
We just tested with a new, up-to-date iPad and found that while Safari still has issues with incomplete indexedDB support Chrome and Firefox now don't operate offline at all.
Versions are iOS 9.2.1, Chrome 48.0.2564.104.
This thread seems to suggest that Chrome at least is now using WKWebView which doesn't support Application Cache.
https://bugs.chromium.org/p/chromium/issues/detail?id=582192&q=label%3AOS-iOS&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified
Can anyone confirm that my understanding of this is correct, ie that it's a fact that Chrome/Firefox on iOS just don't support Application Cache at all anymore, and that only Apple could change this?
Any suggestions on what we can do about it? The only thing I can think of right now is that we'll need to get the app working in Safari by using something other than indexedDB.
As you mentioned both Chrome and Firefox on iOS has issue with appCache, because both are WebKit based.
• The related bug is reported here: https://bugs.webkit.org/show_bug.cgi?id=152490
“Application cache is not supported by WKWebView, but window.applicationCache object exists! so web pages cann’t distinguish if applicationCache is not supported or it is not loaded yet.”
• http://arstechnica.com/apple/2016/01/new-chrome-for-ios-is-finally-as-fast-and-stable-as-safari/
"Chrome 48 on iOS will be as fast as Safari on iOS for the first time ever thanks to a switch from iOS ’UIWebView’ rendering engine to the ‘WKWebView’ engine”
Chrome iOS ver 48.x.x.x release date was 2016-01-27
• This version uses WKWebView, the latest rendering engine from Apple.
Instead of IndexDB you try to use localStorage to keep your data, just one of the possible suggestions.