This seems like a bug and you can report it directly to apple at https://feedbackassistant.apple.com
You could also first check if it is still in the latest version of Xcode (4.3), as it might already be fixed.
Thanks for the reply, and for the link to the forum FAQ!
I actually wasn't aware that this forum had a FAQ and at least when I gave it a quick try right now, I wasn't able to find it from the forum's homepage... Probably I am just looking in the wrong place, but thought it might still be usable feedback for the Apple Forum UI/UX people. ;-)
I also didn't find any questions about this issue in the forum (actually used search first), which seems a bit odd given it's a FAQ. Again, maybe I could have tried harder, but maybe there is also a way to improve this in the forum at some point ;D
Post not yet marked as solved
Thank you so much for this reply! That's the information I was hoping for and helps me plan the future development and transition much better 🙂My main concern with moving everything over to JavaScript was that the (sometimes complex) DOM manipulations the app does require full undo/redo support and that seemed somewhat unstable if I had to pipe it through JS. Will give it another try though and, once I have more concrete experience, file enhancement requests as you recommended.
Post not yet marked as solved
Well, I guess my question is:Will macOS Apps using the WebView (not UIWebView) be allowed in the AppStore after December 2020?My understanding of "depricated" is that the API should no longer be used in newly developed software, not that it should be replaced immediately. It does not imply that the API would no longer be available. The news-post on the other hand says that the UIWebView will no longer be available and so I wondered if that would also be the case for the WebKit or not.
