iOS 7 Safari & New Web Platform Features

http://blogs.adobe.com/webplatform/2013/09/18/ios-7-safari-new-web-platform-features/

by DanielRibeiro • 13 years ago

38 12 13 years ago

blogs.adobe.com

kevingadd2• 13 years ago

Why would you write a whole post about a bunch of new features, and then include demos that only work in one browser on a new mobile OS release? Why not include screenshots?

Still, neat to see that Apple is shipping some of Adobe's new prototype css/canvas features. They seem pretty useful.

digitalengineer• 13 years ago

Agreed. I have my iPhone with iOS7 next to me, but right now I'm reading HN on my Mac. Demo video would be nice...

melling• 13 years ago

Well, if I had to guess, I'd say Adobe is moving into html5 in a big way.

1) They want to show they are a leader.

2) They want to encourage iOS app developers to use these features now, instead of, or along with native code. After all, Apple will have 85-90% of its devices upgraded in 6 months. You can make an ios7 only app and ship today. 50 million people are using it.

3) They want to encourage further browser adoption.

lookingsideways• 13 years ago

I was pleased to find they all work in Safari 6.1. In Chrome it's only the regions example that isn't working.

nimbupani• 13 years ago

A few of them work across many browsers actually. For example, if you enable the right tags you would get Regions in Chrome. Clip paths, canvas paths should work by default, while canvas blend modes should work on Canary and most of these should also work on WebKit Nightlies. Canvas Blend Modes should work in Firefox too.

I could have posted a screenshot but I thought it was nice to have people play with the demo within the browseer, probably will stick to screenshots next time.

kevingadd2• 13 years ago

Well, the point is how do you even tell whether some of them are working? Supposedly Canvas Blend Modes are working in my copy of Firefox, but how can I tell? What's it supposed to look like?

coob• 13 years ago

Glad to see Adobe's input into CSS - can't wait for CSS shaders to make their mainstream debut.

untog2• 13 years ago

Still waiting for Safari to report scroll events correctly. Still waiting...

mmariani• 13 years ago

Don't wait. File a bug report.

http://bugreporter.apple.com

http://www.openradar.me

jamesmoss• 13 years ago

If you're talking about scroll events only firing when you release your finger from the screen I can't see this being changed any time soon.

Apple want to keep scrolling responsive at all costs and definitely wouldn't let those pesky JS developers make Mobile Safari appear slow and laggy.

untog2• 13 years ago

That's what I'm talking about, yes. And I really don't get the logic of it- it'll fire scroll events while the user's finger is down, but then immediately stop as soon as they raise their finger - so I can't see how responsiveness would lead you do that.

evadne• 13 years ago

Probably not going to happen as interaction happens on the main thread with the run loop in event tracking mode, and the JavaScript functions might be queued for a different mode on the main thread or on another thread. (I develop for iOS but am not that familiar with Nitro or WebKit internals.)

The WebKit folks were playing with position: sticky [1] a while earlier. This might be pretty close to what you need.

There’s another solution I’ve used in production — for touch UI, do your own gesture handling and do your own scrolling. This can be done thru Zynga’s Scroller [2] which works very nicely on an iPad 3 — the device I last tested an app with it on.

Summary: in Cocoa, common things are easily and other things are doable. If something is not easy in Cocoa, it might be difficult to get right anyway.

[1] http://updates.html5rocks.com/2012/08/Stick-your-landings-po...

[2] https://github.com/zynga/scroller

iOS 7 Safari & New Web Platform Features

Related Stories