Downgrade minSdkVersion, adding babel & polyfilling support, css polifilling, engine routine modification #5
No reviewers
Labels
No labels
bug
confirmed
bug
critical
bug
new
community
suggestion
community
support
develop
WIP
feature
content
feature
documentation
feature
enhancement
feature
mechanism
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
UmaERA/ere-app!5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This merge request attempts to lower sdkVersion to:
It also polyfills missing JavaScript functions using core-js and compiles ECMAScript6 syntax to ECMAScript5, including:
However, due to the outdated WebView bundled with Android 5.1 (Chromium 39.0.0) which doesn't support many features, and also behaves very differently from modern browser, there is currently impossible to run such project on Android 5.1 unless an webview implementation (i.e. Chromium, Firefox, etc.) is bundled with app.
For browsers that doesn't support css property
color-scheme, a polyfill is provided in main.js by detecting ifwindow.getComputedStyle(document.querySelector("body"))['color-scheme']isundefinedor notNote: The old merge request is trashed. This merge request will no longer call @babel/cli for compiling bundled resources, but uses @vitejs/plugin-legacy to auto compile when bundling.
Engine Routine This merge requests changes the behaviour of engine when the game is going to quit. Now, the engine shall no longer raise
new Error("quit");. instead the engine shall raisenew QuitException();, such changes can prevent any arbitery error class with content "quit" being accidentally raised, and the engine captures hence treated as quit request.Now, engine catchs such error would lead to an instant termination of the app. In order to have a mild solution,
App.exitApp();could be changed intowindow.location.reload();requested review from @SLeader
Pull request closed