News for hackers. Stuff that matters.

A comment on Why I’m done with Chrome. Parent comment

Re:Why I’m done with Chrome by sweetp on Monday September 24, 2018 @02:38AM (#18055502)
the new extensions model is ridiculously useless... You need to build your extension in Xcode now, and for anything other than content blocking, the APIs are non existent... for instance, you can't even close tabs!

I made an extremely simple extension using the new model around 2months - before I try migrating an older "actually useful" extension. But theres just no way its possible to migrate.

Apple doesn't care about browser extensions now, it seems they want everyone to move to the new model, so they can collect revenue on sales on ad blockers.

:(

[ Parent | on HN ]
Re:Why I’m done with Chrome by akvadrako on Monday September 24, 2018 @04:02AM (#18055824)
This is wrong - you can inject arbitrary scripts and styles:

https://developer.apple.com/documentation/safariservices/saf...

[ Parent | on HN ]
Re:Why I’m done with Chrome by wild_preference on Monday September 24, 2018 @10:08AM (#18057756)
You didn’t reply to or contradict anything they said. You need Xcode to build extensions and Safari has a super limited API. Executing JS and CSS don’t address either.
[ Parent | on HN ]
Re:Why I’m done with Chrome by akvadrako on Monday September 24, 2018 @12:44PM (#18059148)
He didn’t say limited, he said nonexistent.

More specifically, if you can inject scripts I don’t see why you couldn’t call window.close()

[ Parent | on HN ]
Re:Why I’m done with Chrome by tgragnato on Monday September 24, 2018 @03:53AM (#18055789)
> Apple doesn't care about browser extensions now, it seems they want everyone to move to the new model, so they can collect revenue on sales on ad blockers.

The web is terrible without a serious adblocker and the available alternatives (paid or not) are unable to take away the same amount of junk. People will simply start using another browser.

[ Parent | on HN ]