framework: Many aurelia libraries are broken in iOS 16
I’m submitting a bug report
- Library Version: aurelia-bootstrapper: 2.3.3
Please tell us about your environment:
-
Operating System: OSX 16
-
Node Version: 14.16.0
- NPM Version: 6.14.11
- Aurelia CLI OR JSPM OR Webpack AND Version CLI 1.3.1 | webpack 4.46.0
-
Browser: iOS 16 Safari
-
Language: all
Current behavior: After the new IOS 16, Safari has a weird behavior in Aurelia, causing many libraries to fail at the detached event. After some searching I found that the ownerdocument of the element is an empty one (about:blank) and many libraries that do cleanup at the detached event are getting errors. More details can be found here .
There is also a repro on the issue 808 of aurelia-kendoui-bridge aurelia-ui-toolkits/aurelia-kendoui-bridge#808
Expected/desired behavior:
Be compatible with Safari.
- What is the motivation / use case for changing the behavior? Can we do something to be compatible again with the new Safari?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 47 (26 by maintainers)
good news, it’s being revised https://bugs.webkit.org/show_bug.cgi?id=246899
PR is up, so I guess we’ll have some good updates for our customers/users soon. https://github.com/WebKit/WebKit/pull/11347
@bigopon pls close it 😃
Also, it’s little bit unusual for DOM spec to introduce a breaking change.
If this is right, then if we change to
importNode, we must change the remove process too. As it is now (and if I understand it correctly), it’s adding the removed elements back to template fragment again. If ‘importNode’ is not removing them from the beginning then we must change the remove process too.I’m still thinking about this. I found this relevant commit in webkit on July and if I followed the discussion correctly, they did this to be compatible with the standard (see the 3rd rule here)
Safari is the first major browser that supports that rule.
It look’s like that this is not a bug of Safari, but a feature and we must adapt to overcome the problems.
On the other hand I remember that I tested the detach event of aurelia-kendoui-bridge without navigating to other page and it didn’t have the same problem. I’m still searching on this…