Odd. It might be a refresh problem. I'm assuming there's nothing obvious in
the JavaScript console. Right?
On Monday, August 10, 2020 at 9:28:07 PM UTC+3 P5music wrote:
> I think this could be an issue for the CEF BrowserComponent so I report it.
> My app has this BrowserComponent for text
Does this happen for a generic website? E.g. if you open Google.com?
Do you see something while debugging on chrome?
On Monday, August 10, 2020 at 9:14:01 PM UTC+3 P5music wrote:
> My app has a BrowserComponent as a mean for the user to edit some text. I
> am testing the new CEF
If it's in the center it takes up the whole set of available space. You can
see this using the component inspector tool.
I explained to you in your previous post how you can use TableLayout with
BrowserComponent. You just need to disable form scrolling and make sure to
define a height/width
I've filed an issue on this at
https://github.com/codenameone/CodenameOne/issues/3213
On Mon, Aug 10, 2020 at 11:39 AM 'P5music' via CodenameOne Discussions <
codenameone-discussions@googlegroups.com> wrote:
> There is a serious issue in the CEF BrowserComponent.
> My app has a text editing
There is a serious issue in the CEF BrowserComponent.
My app has a text editing field in the webview. If I right click the text
area, a huge (as it was magnified) pop-up menu appears and the entire
system crashes.
I think this is the way the issue appears. I do not know if other cases are
I think this could be an issue for the CEF BrowserComponent so I report it.
My app has this BrowserComponent for text editing. There is some
functionality that encompasses creating an image in text, at certain offset.
I can easily do that but the BC behaviour changes accordingly to the offset
or
My app has a BrowserComponent as a mean for the user to edit some text. I
am testing the new CEF BrowserComponent.
I noticed that when I enter the field to edit the text (there is some
default text) and press just the CTRL key, a word disappears. If I press it
again another word disappears.
I've added this to the issue tracker so you can track the progress there.
https://github.com/codenameone/CodenameOne/issues/3212
On Mon, Aug 10, 2020 at 1:33 AM 'P5music' via CodenameOne Discussions <
codenameone-discussions@googlegroups.com> wrote:
> With your suggestions it worked.
> But
This is for all devices. While many of the names correspond to Android's
naming, this density reading should be accurate for all devices. You can
get exact conversion from MM to Pixels using CN.convertToPixels().
On Mon, Aug 10, 2020 at 2:05 AM 'P5music' via CodenameOne Discussions <
I've opened an issue for this in the issuetracker so you can follow its
progress there.
https://github.com/codenameone/CodenameOne/issues/3211
On Mon, Aug 10, 2020 at 5:40 AM Steve Hannah
wrote:
> Currently the browser component in the simulator doesn't fully incorporate
> the skin DPI
Currently the browser component in the simulator doesn't fully incorporate
the skin DPI settings. It sets itself to the DPI of the display, not the
skin. This is an improvement over the way the JavaFX webview dealt with
HiDPI, but it is still something on my list to improve. When using the
My app has a layout with a BrowserComponent inside.
It has text and images inside:
setPage("" +
""+
"This text can be edited by the
user.","");
I am able to encode some images and put them on the page, with:
public String createIconImageUri(Image iconImage)
I am using the new CEF BrowserComponent.
I put it inside a BorderLayout, at the center, so it takes the space
according to the content (the surrounding form/container have been set
correctly to allow this layout to happen).
I need to set the height to a certain size, like 200px, or 4 lines of
I am using the simulator with iPad3 skin.
If I call Display.getInstance().getDeviceDensity(), the result corresponds
to hdpi Android device, that is not for Apple devices too.
Is it right?
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions"
With your suggestions it worked.
But there's no mean to disable the scrollbars.
webView.setNativeScrollingEnabled(false);
webView.setScrollableX(false);
webView.setScrollableY(false);
are useless.
Furthermore a strange behaviour of the BrowserComponent happens: when you
use the scollbars, it
15 matches
Mail list logo
