Get value of fullscreen status in JavaScript

[krmanik]

Pull Request template

Purpose / Description

When adding some function / text eg. showAnswer(); then user have to turn on full screen.
But if user turn off full screen then for hiding that buttons / text, there is way to know if full screen or not in JavaScript.

Fixes

Fixes Link to the issues.

Approach

Using JavascriptInterface, passing Action Bar isShowing

How Has This Been Tested?

Tested on emulator

false when Action Bar showing

true when Action Bar not showing

Learning (optional, can help others)

Describe the research stage

Links to blog posts, patterns, libraries or addons used to solve this problem

Checklist

Please, go through these checks before submitting the PR.

• [ x ] You have not changed whitespace unnecessarily (it makes diffs hard to read)
• [ x ] You have a descriptive commit message with a short title (first line, max 50 chars).
• [ x ] Your code follows the style of the project (e.g. never omit braces in if statements)
• [ x ] You have commented your code, particularly in hard-to-understand areas
• [ x ] You have performed a self-review of your own code

[david-allison]

LGTM. Optional comment

[david-allison]

This is now used in 3 places - might be best to extract it to a method inside AbstractFlashcardViewer

[krmanik]

I tried to extract inside ocreate but AnkiDroid crash everytime.
Edit:
Extracted to a function, now working

[mikehardy]

most of the interesting stuff in AnkiDroid activities needs to be done in (or called from / after) onCollectionLoaded

[krmanik]

Understood, But now I have extracted it inside onCollectionLoaded but always getting false value.

So, may be extracting to function is good.

[mikehardy]

Nice!
I know you have a stack of related PRs @infinyte7 - bear with us while we go through them all, I continue to appreciate the real effort you have put in / are putting in for the JS API init stuff. I believe being an "anki template developer" is going to be a real thing after this, which is exciting to me as it will help us keep UI work (and associated complaints) down in the core so we can focus on the actual scheduling - a win/win