Compatibility Issues with Ext JS 4.0 and Sencha Touch 2.0 in iOS 18.2 Beta – Legacy JavaScript Support and Rendering Problems

Hello, I am encountering compatibility issues with older JavaScript frameworks, specifically Ext JS 4.0 and Sencha Touch 2.0, after upgrading to iOS 18.2 Beta. My application, which was working fine on previous versions of iOS, is now experiencing rendering issues, broken touch events, and performance degradation on WebKit in iOS 18.2. The issues I’m seeing include:

Sencha Touch 2.0: The UI elements (like fields, and lists) are not interactive or showing their content properly. There also seems to be a delay in rendering touch events. This seem to no longer work as expected with the updated WebKit engine in iOS 18.2 Beta. My Questions: Are there any known issues with legacy JavaScript frameworks like Ext JS 4.0 and Sencha Touch 2.0 on iOS 18.2 Beta? Specifically, do these frameworks rely on older DOM methods or JavaScript features that might be deprecated in the latest WebKit engine? Has Apple officially deprecated any JavaScript features or DOM methods in WebKit that might be causing these issues? If so, are there recommended workarounds or updates to ensure compatibility with iOS 18.2? Is there a way to enable legacy JavaScript features or fallback modes in iOS 18.2 ? I would appreciate any guidance on this, as we are facing significant issues with our app’s performance and UI since upgrading to iOS 18.2. Thank you!

We are also facing the same problem, Appreciate if you find any help and solution

We also realised issue in displaying scroll bar for list or ext picker in sencha touch .

We are facing the same problem. The rota in our web application, which is based on Sencha Touch 2.0, is no longer displayed correctly. It works perfectly in Chrome.

same issue with our app, much appreciated if anyone can assist on this.

same issue in our app with any sort of picker not rendering the values correctly. What is interesting is, that even tough the values are not being rendered, they are present when "picked". Any resolution or workaround on this would be greatly appreciated.

Running into the same issue with our application.

Appears that specific JS events that extJS and Sencha leverage are not firing, leading to components not being initialized correctly.

Has anyone found any workarounds?

Same here. Man this is frustrating.

Hey all. We faced this too and we had about 3 screens broken in different ways, and we came up with some code bandaids

We investigated and found that something was misfiring (such as an event after requestAnimationFrame was not being fired or was timed differently) and the sizes of components and panels were not properly being set within the javascript context, and so things like animations would not complete properly, leaving components off screen or containers not interactable

We worked around this by adding a deferred call to refresh sizes when necessary, into the afterRender or initialize block of the component affected, or the parent component

For example, panels were not scrollable, and we found the scroller was never obtaining the size of the container properly, and so the scroller panel was size 0, preventing scrolling

We added an afterRender block (deprecated but initialize should do it too) in Container which defers a call to refresh() on the scroller, which appears to have worked around the issue on two screens

We also applied a similar fix to another animated card layout component

I mentioned requestAnimationFrame because I understand that iOS 18.2 beta enabled some support for 120hz for requestAnimationFrame specifically, so I wonder if this change caused this somehow.

We're facing this problem as well: Since Updating to iOS18.2, some data isn't displayed anymore and the date picker shows nothing selectable.

Please, could you give me an example code?

Compatibility Issues with Ext JS 4.0 and Sencha Touch 2.0 in iOS 18.2 Beta – Legacy JavaScript Support and Rendering Problems
 
 
Q