21–30 of 176 posts
Apple's been taking a number of steps over the last few months to show that they take Safari/WebKit development seriously. This is another positive step in the right direction. While I never agreed with the nonsensical "Safari is the New IE" meme that was going around, I did fear that Apple's tendency to develop things in a vacuum would continue to harm WebKit relative to Blink, Gecko, etc. But all signs are pointing…
Earlier quoted context omitted.
So a particular website goofing something up is Safari's fault? (Incidentally, just went to Booking.com on iOS Safari. Works fine here.)
You haven't been following the news lately I see. Yes, it is.
Bummed to not see WebRTC on here though.
Apple's been taking a number of steps over the last few months to show that they take Safari/WebKit development seriously. This is another positive step in the right direction. While I never agreed with the nonsensical "Safari is the New IE" meme that was going around, I did fear that Apple's tendency to develop things in a vacuum would continue to harm WebKit relative to Blink, Gecko, etc. But all signs are pointing…
I'll take them seriously when they release something that runs on Windows.
Chrome was using WebKit a long time, Blink is a WebKit fork. Both run on Windows.
I love that they are supporting Shadow DOMs, but until the other browsers support it, the feature is dead in the water. I mean, it's a feature that you'd build a whole app around, but if IE and Firefox don't support it, I can't really do that.
Edge(nee IE) and Firefox are committed to support and active in the standards discussions, and I believe allocating people to work on it, if not working on it already. Support across all the major browsers will arrive before we know it.
We also have polyfills for Shadow DOM and the other Web Components standards, and are updating them for the v1 spec: https://github.com/webcomponents/webcomponentsjs
The Shadow DOM polyfill is a bit slow, but soon it'll only be necessary on older browsers, so some properties might be able to adopt full Shadow DOM within the year.
If you use Polymer, we have a fast Shadow DOM-like shim called Shadey DOM, and you can pretty seamlessly opt-in to full Shadow DOM where available.
That's nice, but no iOS release? Edit: As it is now, it doesn't look very different from what already existed as OSX-side-loadable Webkit Nightlies https://webkit.org/nightly/ or building from source (which even supports iOS simulator!) https://webkit.org/building-webkit/
Apple's been taking a number of steps over the last few months to show that they take Safari/WebKit development seriously. This is another positive step in the right direction. While I never agreed with the nonsensical "Safari is the New IE" meme that was going around, I did fear that Apple's tendency to develop things in a vacuum would continue to harm WebKit relative to Blink, Gecko, etc. But all signs are pointing…
I'll take them seriously when they release something that runs on Windows.
Nice to have more visibility into which features are coming to WebKit, especially since they don't release to consumers very often. Bummed to not see WebRTC on here though.