7.0.207

Better fix for toast bar and safe areas

This time tested with iOS and Android

https://github.com/codenameone/CodenameOne/issues/3952

7.0.206

fix: [3937] Fixed FAB respect safe areas (#3950)

7.0.205

Fix ImageViewer getCroppedImage() inconsistency after panning operati…

7.0.204

Full Changelog: 7.0.203...7.0.204

7.0.203

Full Changelog: 7.0.202...7.0.203

7.0.202

What's Changed

• Initial Accessibility support focusing on Android by @shai-almog in #3927
• Disable doclint to prevent Javadoc failures by @shai-almog in #3932
• Fix Javadoc links and escape HTML entities by @shai-almog in #3934

Full Changelog: 7.0.201...7.0.202

7.0.201

fix: Android safe areas should work when there are no cutouts (#3926)

This fixes https://github.com/codenameone/CodenameOne/issues/3925, where it was demonstrated that the Sheet was being cut off by the bottom navigation bar.
I found that the current code for updating the safe area would always return zero insets if the device didn't have a cutout.
Fixed it so that system bars would still be incorporated into the safe area even with there were no cutouts.

7.0.200

Signature verification logic (#3924)

7.0.199

fix: NullPointerException intermittently on launch (#3917)

7.0.198

fix: [3914] Fix safe area insets on android 34 (#3915)

* fix: [3914] Fix safe area insets on android 34

This fixes both safe area insets and form bottom padding editing on android 34.
By trial and error, I found that, with respect to immersive mode, android 34 behaves like
android 33 and earlier unless we explicitly enable it by calling WindowCompat.setDecorFitsSystemWindows(window, false),
which we don't do.  And it is not possible to detect whether this has been called.
This patch adjusts immersive heuristics to check for API 35+ instead of 34+ when determining if we are drawing
edge to edge on the screen.

This impacts the safe area insets implementation as well as form bottom padding editing.

As part of this, I have re-enabled the android.useSafeAreaInsets display property by default
so taht we use safe area insets by default.  This can be opted out.

The reason is that on API 35+ it needs this setting to work properly.

* fix extra bottom padding when ime is visible