Fix iOS 14~17 EXC_BAD_ACCESS crash when evaluateJavaScript on windowID WebViews

[studiogaram]

Connection with issue(s)

Resolve issue #2600

Testing and Review Notes

Steps to reproduce the crash (before fix):

1. Create a parent WebView with javaScriptCanOpenWindowsAutomatically: true and supportMultipleWindows: true
2. Trigger window.open() or click a link with target="_blank" to open a popup window
3. Create a child WebView with the windowId from onCreateWindow
4. Call evaluateJavascript() on the child WebView
5. Result: App crashes with EXC_BAD_ACCESS (code=1, address=0x0) on iOS 14~17

Steps to verify the fix:

1. Repeat the same steps above
2. Expected Result: evaluateJavascript() works without crash on iOS 14~17
3. Note: iOS 18+ uses the original behavior with contentWorld parameter

Root Cause:

• WindowId WebViews reuse WKWebView from parent and share WKWebViewConfiguration
• They skip custom WKUserContentController initialization
• When evaluateJavaScript is called with contentWorld parameter, the internal content world state is not properly
  initialized for popup WebViews

Workaround Applied:

• On iOS < 18: Use non-contentWorld version of evaluateJavaScript for windowId WebViews
• On iOS 18+: Use original behavior (Apple may have fixed this issue)

To Do

• double check the original issue to confirm it is fully satisfied
• add testing notes and screenshots in PR description to help guide reviewers
• request the "UX" team perform a design review (if/when applicable)