News for hackers. Stuff that matters.
Re:Apple Pay JavaScript Framework by nickruby on Monday June 13, 2016 @07:42PM (#11898687)
has to be on safari? lol
Re:Apple Pay JavaScript Framework by avdempsey on Monday June 13, 2016 @07:49PM (#11898719)
That covers the vast majority of people browsing the web on their iPhones/iPads. Not sure what the browser share is on the Mac though.
Re:Apple Pay JavaScript Framework by pfooti on Monday June 13, 2016 @10:08PM (#11899291)
That covers everybody on an iDevice - the only browser on iOS is Mobile Safari. Chrome, Firefox, Opera are all skins on top of the Safari Webkit renderer.

Interestingly / Ironically / Whateverally, it doesn't cover a ton of other, non-iOS users. This may be a push to Desktop Safari usage, but I am really uninterested in supporting proprietary browser tech, especially when there are competing open standards, doubly-especially when (as the OP mentioned) Safari in particular doesn't seem interested in supporting other open, interesting APIs.

Re:Apple Pay JavaScript Framework by nothis on Monday June 13, 2016 @10:12PM (#11899300)
Since I never quite figured this out: Why are there no real other browsers on iOS? Is it policy or simply not feasible?
Re:Apple Pay JavaScript Framework by 0x0 on Monday June 13, 2016 @10:22PM (#11899334)
App Store policy requires any app rendering HTML/JS to use the safari/webkit-backed UI components.

See 2.5.6 here https://developer.apple.com/app-store/review/guidelines/

"2.5.6 Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript."

As for why this is, one can only speculate. There used to be an extremely strict "no interpreted code allowed", which was relaxed to "no interpreted downloaded code", which I think (with the addition of the JavaScriptCore framework and the lack of bans on bundling a LUA interpreter as many games do) has turned into a "no major functionality changes or additions in downloadable code". I guess their main concern was developers publishing app updates outside of the app store review team's oversight.

Re:Apple Pay JavaScript Framework by kitsunesoba on Monday June 13, 2016 @11:27PM (#11899538)
Allowing other browser engines would also mean there'd be a lot more room for vulnerabilities that Apple has no control over. That's not to say that Blink or Gecko or whatever aren't secure, but if either of these engines introduced any kind of severe holes the consequences could be disastrous (and worse, unpatchable for that segment of folks who disable auto update).

Besides that, both Firefox and Chrome on OS X are notorious for power usage issues. There's a very good likelyhood that'd be true under iOS as well and the last thing Apple wants is a bunch of users blaming their iDevices for poor battery performance when the issue is actually web engines that are bad at rationing energy.

Re:Apple Pay JavaScript Framework by 0x0 on Monday June 13, 2016 @11:59PM (#11899669)
Well, the horse's kinda already bolted out of the barn when they allow external scripts to be executed in game level updates or whatever. And any damage would be contained to the app in question... unless the iOS sandbox is a sieve... they do seem to have tightened it up fairly well recently though.

You're right about power usage though. Even if they did allow third party engines, they wouldn't allow third party JIT compilers (much bigger attack surface, W|X memory protection is gated behind an apple-only entitlement) so those browsers would be second class citizens battery- and performance-wise for sure.

Re:Apple Pay JavaScript Framework by knodi123 on Monday June 13, 2016 @10:07PM (#11899286)
shockingly low, if the 3 mac-using companies I've worked at are any indicator.
Re:Apple Pay JavaScript Framework by grangulius on Monday June 13, 2016 @08:31PM (#11898923)
If you have access to TouchID, you're going to be using Safari to browse the web.
Re:Apple Pay JavaScript Framework by tomphoolery on Monday June 13, 2016 @09:36PM (#11899170)
macOS Sierra will be capable of authenticating using TouchID (read from your iOS device)
Re:Apple Pay JavaScript Framework by pbreit on Monday June 13, 2016 @08:53PM (#11899015)
And could probably hack it with redirects otherwise.
Re:Apple Pay JavaScript Framework by untog on Monday June 13, 2016 @08:23PM (#11898885)
Even more disappointingly, there is an open W3C standard in progress for payments. Ah well, such is Apple.
Re:Apple Pay JavaScript Framework by paulirish on Monday June 13, 2016 @08:34PM (#11898933)
It appears there isn't too much of a gap with the Web Payments API. Today, the Safari team posted their intent to rectify the differences: https://lists.w3.org/Archives/Public/public-payments-wg/2016...
Re:Apple Pay JavaScript Framework by ihuman on Monday June 13, 2016 @08:28PM (#11898912)
Does anyone use that standard? This is the first time I've heard that there was a standard.
Re:Apple Pay JavaScript Framework by lern_too_spel on Monday June 13, 2016 @08:53PM (#11899017)
Google announced web payments integration for Android Pay using the Web Payments API last month. Just like Apple Pay for the web, nobody is using it now, but it's on the Chrome roadmap.
Re:Apple Pay JavaScript Framework by sjwright on Monday June 13, 2016 @09:20PM (#11899109)
So therefore it's a question of whether Google or Apple get to muscle their way to influencing the eventual W3C standard, by deploying a pre-standard implementation. Same difference in my view. Yet somehow Apple is smacked down for it?
Re:Apple Pay JavaScript Framework by Touche on Tuesday June 14, 2016 @08:21AM (#11901515)
If by same difference you mean "one is being developed in the open, with editors from Microsoft, Firefox, and Facebook and the other was developed in private and has the company's name in the API"... then yes, same difference.
Re:Apple Pay JavaScript Framework by cmdrfred on Monday June 13, 2016 @10:11PM (#11899296)
Too bad this space is so heavy regulated. I'd like to see a free and open source implementation pushing the standard.
Re:Apple Pay JavaScript Framework by lern_too_spel on Monday June 13, 2016 @10:39PM (#11899406)
Both the Firefox and Chromium implementations of the payments api are free and open source.