Bug 245959

It appears Safari iOS16 is no longer propagating the '_apple_ar_quicklook_button_tapped' ARQL 'message' event to the originating anchor element when the anchor is not attached to the DOM.

It is possible to use JavaScript to create an 'a' element, set the appropriate 'rel' and 'href' attributes and invoke the 'click()' method to initialise an ARQL session.

The originating anchor element can listen for a 'message' event with payload of '_apple_ar_quicklook_button_tapped' to indicate the user tapped the banner displayed in the ARQL session and respond appropriately.

Prior to iOS16, that anchor element did not need to be attached to the DOM to receive the ARQL 'message' event notification.

In iOS16, a detached anchor will no longer receive the ARQL 'message' event.

The solution is to attach the anchor element to the DOM, and then in iOS16 it will once again receive the ARQL 'message' event.

Demo:
https://ios16-arql-banner-issue.glitch.me/

First example: the anchor element is defined on the page. Interaction with ARQL banner is captured through message event listener. This works in iOS16 fine.

Second example: the 'Launch Default' button triggers the click() method of the default anchor. ARQL opens. Interaction with banner is captured. Works fine in iOS16.

Third example: the 'Launch Detached' button uses JavaScript to create a new anchor element, assigns necessary attributes, and triggers click() method, without attaching element to the DOM. In iOS16, ARQL opens, banner is displayed, but clicks on banner do not propagate the message event to the detached element. This used to (and still does) work fine in iOS15, but not in iOS16.

Fourth example; The 'Launch Attached' button uses JavaScript to create a new anchor element, but also attaches it to the DOM by appending to body. ARQL opens, the banner displays, and banner clicks do indeed get propagated to the anchor's event listener and can respond appropriately. This now works in iOS16.


This could potentially have broken many sites utilising ARQL with banners.

There is a work-around.

But was this intentional or an oversight?