I wouldn't call this a "web" protocol, since it only works on iOS (and maybe OSX?)
I haven't read up on the iOS developer side of this, but I know that apps can register themselves with a protocol that redirects to an app. I work as a developer of a medical informatics web app. We have a companion iOS app that provides native imaging support on iOS. We allow our customers to customize image links, which can go to our iOS app or to another web app. If we recognize that they're running in iOS on the web (it's in the Safari user agent string), and they have the iOS link configured, we'll use that in place of other links. It becomes a clickable URL.
Point being, this is a deliberate "protocol" within iOS, and it does have legitimate uses.
However, I've seen the same ad behavior, and it is very irritating. It would be nice of Apple to restrict usage to user clicks/taps, and not accept these redirects from JavaScript.
I haven't read up on the iOS developer side of this, but I know that apps can register themselves with a protocol that redirects to an app. I work as a developer of a medical informatics web app. We have a companion iOS app that provides native imaging support on iOS. We allow our customers to customize image links, which can go to our iOS app or to another web app. If we recognize that they're running in iOS on the web (it's in the Safari user agent string), and they have the iOS link configured, we'll use that in place of other links. It becomes a clickable URL.
Point being, this is a deliberate "protocol" within iOS, and it does have legitimate uses.
However, I've seen the same ad behavior, and it is very irritating. It would be nice of Apple to restrict usage to user clicks/taps, and not accept these redirects from JavaScript.