Handling mVisibility Variables in Android Environments
Nobody has claimed this yet.
- Dominant language
- Objective-C++
- Stars
- 2.7k
- Forks
- 734
- Avg merge
- 11h 39m
- Merged PRs (30d)
- 1
Description
Android environment:
The Visibility variable is inconsistent when you bring up a native UI on your website (the application goes to the background).
Example of correction content:
https://github.com/manakamic/unity-webview/blob/fix/android_visibility_variable/plugins/WebViewObject.cs
https://github.com/manakamic/unity-webview/blob/fix/android_visibility_variable/plugins/WebViewObject.cs#L81
https://github.com/manakamic/unity-webview/blob/fix/android_visibility_variable/plugins/WebViewObject.cs#L492
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with plugins/WebViewObject.cs and compare the referenced correction branch, especially lines 81 and 492. Reproduce the Android case where a native UI sends the application to the background, then verify that the Visibility variable remains consistent when the web view returns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, unity
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100