[codenameone-discussions] Re: CEF BrowserComponent (simulator) does not always update immediately after inserting images in text with Javascript.

[Shai Almog]

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 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 sometimes in erratic fashion.
> Here's what happens. When the offset is 0 or the last position the image 
> does not appear just after inserting in the DOM as expected, instead I have 
> to enter the editing field again to see it (and the size of the BC changes 
> at this time, not before, so it is updated at this time and not before). 
> This happens every time for those offset positions, but sometimes it 
> happens in intermediate positions.
> No matter whether I call focus() or other methods on the element (in 
> Javascript), or other workarounds, the behaviour is solid, like it is an 
> issue.
> Thanks in advance
>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/ce98f649-1d84-44a4-a883-d27b81539bc6n%40googlegroups.com.

[codenameone-discussions] Re: CTRL key deletes words in CEF BrowserComponent with text editing

[Shai Almog]

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 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.
> Maybe this is a bug, I do not know.
> Thanks in advance
>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/9ffbc44b-e243-454a-ad1a-71d59789b78dn%40googlegroups.com.

[codenameone-discussions] Re: Setting the size of the new CEF BrowserComponent programmatically

[Shai Almog]

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 constraint to the cell.

On Monday, August 10, 2020 at 12:12:03 PM UTC+3 P5music wrote:

> 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 
> text, for example.
> If I set the page to an HTML string with text inside, I see the text and 
> no scrollbars (that instead appear in other cases), so it seems that the 
> size is not as tall as the remaining space. It is good for my layout but I 
> need to set the height exactly before there is text inside, and It has not 
> to resize automatically.
> The setHeight method does not work, not even after the onload event.
> Thanks in advance
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/80926126-0137-48c3-8c7b-e588a91cb5cbn%40googlegroups.com.

Re: [codenameone-discussions] CEF BrowserComponent (simulator) crashes my PC when right-clicking in text editing field

[Steve Hannah]

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 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 possible, for example with a normal web page.
> Thanks in advance
>
> IntelliJ IDEA 2020.2 (Community Edition)
> Build #IC-202.6397.94, built on July 27, 2020
> Runtime version: 11.0.7+10-b944.20 amd64
> VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
> Linux 5.4.0-42-generic
> GC: ParNew, ConcurrentMarkSweep
> Memory: 949M
> Cores: 4
> Non-Bundled Plugins: com.codename1.plugin.intellij
> Current Desktop: ubuntu:GNOME
>
> --
> You received this message because you are subscribed to the Google Groups
> "CodenameOne Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to codenameone-discussions+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/codenameone-discussions/9b7793fa-687c-4f07-8c20-8e461889f18do%40googlegroups.com
> 
> .
>


-- 
Steve Hannah
Software Developer
Codename One
http://www.codenameone.com

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKWFy-DbsiNaWgjy-z92M-prmCUYx7x5uRRQ2uj39SqP8Q%40mail.gmail.com.

[codenameone-discussions] CEF BrowserComponent (simulator) crashes my PC when right-clicking in text editing field

['P5music' via CodenameOne Discussions]

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 
possible, for example with a normal web page.
Thanks in advance

IntelliJ IDEA 2020.2 (Community Edition)
Build #IC-202.6397.94, built on July 27, 2020
Runtime version: 11.0.7+10-b944.20 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.4.0-42-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 949M
Cores: 4
Non-Bundled Plugins: com.codename1.plugin.intellij
Current Desktop: ubuntu:GNOME

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/9b7793fa-687c-4f07-8c20-8e461889f18do%40googlegroups.com.

[codenameone-discussions] CEF BrowserComponent (simulator) does not always update immediately after inserting images in text with Javascript.

['P5music' via CodenameOne Discussions]

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 sometimes in erratic fashion.
Here's what happens. When the offset is 0 or the last position the image 
does not appear just after inserting in the DOM as expected, instead I have 
to enter the editing field again to see it (and the size of the BC changes 
at this time, not before, so it is updated at this time and not before). 
This happens every time for those offset positions, but sometimes it 
happens in intermediate positions.
No matter whether I call focus() or other methods on the element (in 
Javascript), or other workarounds, the behaviour is solid, like it is an 
issue.
Thanks in advance

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/7ecfacfc-d56a-46bc-9fa6-11dda8b6eee9o%40googlegroups.com.

[codenameone-discussions] CTRL key deletes words in CEF BrowserComponent with text editing

['P5music' via CodenameOne Discussions]

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.
Maybe this is a bug, I do not know.
Thanks in advance

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/641df5c3-f90e-42c4-8641-0345118231f5o%40googlegroups.com.

Re: [codenameone-discussions] CEF BrowserComponent - Exception in thread "AWT-EventQueue-0"

[Steve Hannah]

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 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 scrolls, then the mouse is catched by the BC and when
> it is inside the control it is like it is scolling, not pointing, so the
> content scrolls in a erratic way.
>
> Il giorno lunedì 10 agosto 2020 07:12:15 UTC+2, Shai Almog ha scritto:
>>
>> Make sure to disable scrolling on the parent form. Also make sure to give
>> the table layout the right amount of height constraint.
>> You would have run into this issue on devices with the FX browser so it's
>> good the CEF browser behaves the same way.
>>
>> The core of the issue is this: browser component can't tell us its
>> preferred size during layout since this requires parsing all the HTML which
>> might not even be available and is happening on a separate thread to begin
>> with. So preferred size is small/zero and the layout correctly places it as
>> a small sliver.
>>
>> The second problem is scrolling which lays out things differently. It can
>> also collide with the native scrolling within the browser itself so nesting
>> scrollables is a big problem here and contributes to janky UI.
>>
>> BorderLayout center on the form solves this in two ways. It implicitly
>> disables the scrolling on the form (Form is the only container that's
>> scrollable by default). The second feature is that the CENTER constraint
>> ignores the preferred size of the component and grants it available space.
>> That way the browser takes up the remaining space regardless of the rest of
>> the content. You can achieve that with TableLayout if you disable scrolling
>> manually and set the width/height percentage via a constraint.
>>
>> On Sunday, August 9, 2020 at 2:34:42 PM UTC+3 P5music wrote:
>>
>>> The browser component just expands when in a BL inside a form.
>>> My layout is made of a TableLayout that reproduces a master/detail
>>> layout. The TL is in the main form.
>>> No matter what combination of Container and BorderLayout axis I create,
>>> the effect is that the BrowserComponent starts just as a tiny spot (some
>>> pixels wide), then if I touch it, it becomes...less tiny, with scrollbars
>>> as previously shown.
>>> Furthermore I experienced instable layout when putting the
>>> BrowserComponent in a real layout, in certain cases the other components
>>> disappeared after interacting with the BC and only the BC remained.
>>> Another case: I put the other components in LEFT, and the BC in RIGHT, I
>>> could see the BC at same vertical size of the other layout stuff on left,
>>> but horizontally speaking in fact the BC covered the other things on the
>>> left of some amount,
>>>
>>>
>>> Il giorno sabato 8 agosto 2020 06:12:17 UTC+2, Shai Almog ha scritto:

 Is the browser in the center of a border layout in the parent form?
 It looks like the browser component itself isn't getting enough space
 on the layout. Notice that the form needs to be in border layout and the
 browser component should be in the center of that so it will take up
 available space.

 On Friday, August 7, 2020 at 11:44:00 AM UTC+3 P5music wrote:

> It is the same with setNativeScrollingEnabled(false), scrollbars are
> there yet. And the BrowserComponent is tiny, it seems empty but in Chrome 
> I
> see the content in a very tiny window.
>
>
> Il giorno venerdì 7 agosto 2020 04:52:03 UTC+2, Shai Almog ha scritto:
>>
>> Did you try setNativeScrollingEnabled(false) on the browser component?
>>
>> On Thursday, August 6, 2020 at 11:46:05 AM UTC+3 insig...@libero.it
>> wrote:
>>
>>> In Chrome I see that control in a very big size but it is tiny in
>>> fact, with just the scrollbars, but the editor is inside, I see some 
>>> little
>>> area of it. The BrowserComponent has not expanded like in JavaFX. Please
>>> see the attached image.
>>> In general I would like to know how to set the size of a component
>>> to "wrap_content" or "match_parent", unless I am missing something 
>>> obvious,
>>> my fault.
>>> Thanks in advance
>>>
>>>
>>> Il giorno mercoledì 5 agosto 2020 20:47:39 UTC+2, Steve Hannah ha
>>> scritto:
>>>
 While your app is open, you can debug the web view in Chrome by
 going to http://localhost:8088

 That might offer you some clues as to what is going wrong.



 On Wed, Aug 5, 2020 at 11:28 AM 'Angelo Maci' via CodenameOne
 

Re: [codenameone-discussions] Simulator: iPad3 skin dpi is like Android hdpi device

[Steve Hannah]

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 <
codenameone-discussions@googlegroups.com> wrote:

> 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" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to codenameone-discussions+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/codenameone-discussions/a74b3b8c-6b89-4855-ac16-84346062662bo%40googlegroups.com
> 
> .
>


-- 
Steve Hannah
Software Developer
Codename One
http://www.codenameone.com

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKWxUxq--QTUP6hUip91%2B0GYq_ikmW8Qh29b908x9sddTA%40mail.gmail.com.

Re: [codenameone-discussions] CEF BrowserComponent dpi

[Steve Hannah]

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 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
> desktop skin you'll get good results.  For other themes, you'll probably
> need to size the simulator window appropriately to approximate the relative
> size for now.
>
> On Mon, Aug 10, 2020 at 2:19 AM 'P5music' via CodenameOne Discussions <
> codenameone-discussions@googlegroups.com> wrote:
>
>> My app has a layout with a BrowserComponent inside.
>> It has text and images inside:
>>
>> setPage("" +
>> ""+
>> "> contenteditable=\"true\">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)
>> {
>> EncodedImage em = EncodedImage.createFromImage(iconImage, false);
>> byte[] data = em.getImageData();
>> String iconUri=BrowserComponent.createDataURI(data,"image/png");
>> return iconUri;
>> }
>>
>> I see that the text and the image size does not match what is in the
>> layout external to the BrowserComponent, like they are doubled in the BC.
>> There is some dpi question here. Note that the simulator skin is iPad3
>> and dpi=240 (wrong? see my other thread) and the size of the images on the
>> layout is 72.
>> What can be said about the viewport of the CEF BrowserComponent or
>> similar adjustments?
>> Thanks in advance
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "CodenameOne Discussions" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to codenameone-discussions+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/codenameone-discussions/56f03163-428c-4df1-a360-bbf0d9cccf19o%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Steve Hannah
> Software Developer
> Codename One
> http://www.codenameone.com
>


-- 
Steve Hannah
Software Developer
Codename One
http://www.codenameone.com

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKXU0gbXkkB8nt%3D25Rq%3DxSkxpsg7uOjjNGDk%3D1HDaLtRKg%40mail.gmail.com.

Re: [codenameone-discussions] CEF BrowserComponent dpi

[Steve Hannah]

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
desktop skin you'll get good results.  For other themes, you'll probably
need to size the simulator window appropriately to approximate the relative
size for now.

On Mon, Aug 10, 2020 at 2:19 AM 'P5music' via CodenameOne Discussions <
codenameone-discussions@googlegroups.com> wrote:

> My app has a layout with a BrowserComponent inside.
> It has text and images inside:
>
> setPage("" +
> ""+
> " contenteditable=\"true\">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)
> {
> EncodedImage em = EncodedImage.createFromImage(iconImage, false);
> byte[] data = em.getImageData();
> String iconUri=BrowserComponent.createDataURI(data,"image/png");
> return iconUri;
> }
>
> I see that the text and the image size does not match what is in the
> layout external to the BrowserComponent, like they are doubled in the BC.
> There is some dpi question here. Note that the simulator skin is iPad3 and
> dpi=240 (wrong? see my other thread) and the size of the images on the
> layout is 72.
> What can be said about the viewport of the CEF BrowserComponent or similar
> adjustments?
> Thanks in advance
>
> --
> You received this message because you are subscribed to the Google Groups
> "CodenameOne Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to codenameone-discussions+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/codenameone-discussions/56f03163-428c-4df1-a360-bbf0d9cccf19o%40googlegroups.com
> 
> .
>


-- 
Steve Hannah
Software Developer
Codename One
http://www.codenameone.com

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/CAGOYrKXV9-qvf4QYq%3D1Vk9MHSy10q0i%2BfaegFaNkraPgk3L%2BQw%40mail.gmail.com.

[codenameone-discussions] CEF BrowserComponent dpi

['P5music' via CodenameOne Discussions]

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)
{
EncodedImage em = EncodedImage.createFromImage(iconImage, false);
byte[] data = em.getImageData();
String iconUri=BrowserComponent.createDataURI(data,"image/png");
return iconUri;
}

I see that the text and the image size does not match what is in the layout 
external to the BrowserComponent, like they are doubled in the BC.
There is some dpi question here. Note that the simulator skin is iPad3 and 
dpi=240 (wrong? see my other thread) and the size of the images on the 
layout is 72.
What can be said about the viewport of the CEF BrowserComponent or similar 
adjustments?
Thanks in advance

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/56f03163-428c-4df1-a360-bbf0d9cccf19o%40googlegroups.com.

[codenameone-discussions] Setting the size of the new CEF BrowserComponent programmatically

['P5music' via CodenameOne Discussions]

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 text, 
for example.
If I set the page to an HTML string with text inside, I see the text and no 
scrollbars (that instead appear in other cases), so it seems that the size 
is not as tall as the remaining space. It is good for my layout but I need 
to set the height exactly before there is text inside, and It has not to 
resize automatically.
The setHeight method does not work, not even after the onload event.
Thanks in advance


-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/4de06cf4-456d-4f9f-b983-9962f03aa6a6o%40googlegroups.com.

[codenameone-discussions] Simulator: iPad3 skin dpi is like Android hdpi device

['P5music' via CodenameOne Discussions]

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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to codenameone-discussions+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/a74b3b8c-6b89-4855-ac16-84346062662bo%40googlegroups.com.

Re: [codenameone-discussions] CEF BrowserComponent - Exception in thread "AWT-EventQueue-0"

['P5music' via 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 scrolls, then the mouse is catched by the BC and when 
it is inside the control it is like it is scolling, not pointing, so the 
content scrolls in a erratic way.

Il giorno lunedì 10 agosto 2020 07:12:15 UTC+2, Shai Almog ha scritto:
>
> Make sure to disable scrolling on the parent form. Also make sure to give 
> the table layout the right amount of height constraint. 
> You would have run into this issue on devices with the FX browser so it's 
> good the CEF browser behaves the same way.
>
> The core of the issue is this: browser component can't tell us its 
> preferred size during layout since this requires parsing all the HTML which 
> might not even be available and is happening on a separate thread to begin 
> with. So preferred size is small/zero and the layout correctly places it as 
> a small sliver. 
>
> The second problem is scrolling which lays out things differently. It can 
> also collide with the native scrolling within the browser itself so nesting 
> scrollables is a big problem here and contributes to janky UI.
>
> BorderLayout center on the form solves this in two ways. It implicitly 
> disables the scrolling on the form (Form is the only container that's 
> scrollable by default). The second feature is that the CENTER constraint 
> ignores the preferred size of the component and grants it available space. 
> That way the browser takes up the remaining space regardless of the rest of 
> the content. You can achieve that with TableLayout if you disable scrolling 
> manually and set the width/height percentage via a constraint.
>
> On Sunday, August 9, 2020 at 2:34:42 PM UTC+3 P5music wrote:
>
>> The browser component just expands when in a BL inside a form.
>> My layout is made of a TableLayout that reproduces a master/detail 
>> layout. The TL is in the main form.
>> No matter what combination of Container and BorderLayout axis I create, 
>> the effect is that the BrowserComponent starts just as a tiny spot (some 
>> pixels wide), then if I touch it, it becomes...less tiny, with scrollbars 
>> as previously shown.
>> Furthermore I experienced instable layout when putting the 
>> BrowserComponent in a real layout, in certain cases the other components 
>> disappeared after interacting with the BC and only the BC remained.
>> Another case: I put the other components in LEFT, and the BC in RIGHT, I 
>> could see the BC at same vertical size of the other layout stuff on left, 
>> but horizontally speaking in fact the BC covered the other things on the 
>> left of some amount,
>>
>>
>> Il giorno sabato 8 agosto 2020 06:12:17 UTC+2, Shai Almog ha scritto:
>>>
>>> Is the browser in the center of a border layout in the parent form?
>>> It looks like the browser component itself isn't getting enough space on 
>>> the layout. Notice that the form needs to be in border layout and the 
>>> browser component should be in the center of that so it will take up 
>>> available space.
>>>
>>> On Friday, August 7, 2020 at 11:44:00 AM UTC+3 P5music wrote:
>>>
 It is the same with setNativeScrollingEnabled(false), scrollbars are 
 there yet. And the BrowserComponent is tiny, it seems empty but in Chrome 
 I 
 see the content in a very tiny window.
  

 Il giorno venerdì 7 agosto 2020 04:52:03 UTC+2, Shai Almog ha scritto:
>
> Did you try setNativeScrollingEnabled(false) on the browser component?
>
> On Thursday, August 6, 2020 at 11:46:05 AM UTC+3 insig...@libero.it 
> wrote:
>
>> In Chrome I see that control in a very big size but it is tiny in 
>> fact, with just the scrollbars, but the editor is inside, I see some 
>> little 
>> area of it. The BrowserComponent has not expanded like in JavaFX. Please 
>> see the attached image.
>> In general I would like to know how to set the size of a component to 
>> "wrap_content" or "match_parent", unless I am missing something obvious, 
>> my 
>> fault.
>> Thanks in advance
>>
>>
>> Il giorno mercoledì 5 agosto 2020 20:47:39 UTC+2, Steve Hannah ha 
>> scritto:
>>
>>> While your app is open, you can debug the web view in Chrome by 
>>> going to http://localhost:8088 
>>>
>>> That might offer you some clues as to what is going wrong.
>>>
>>>
>>>
>>> On Wed, Aug 5, 2020 at 11:28 AM 'Angelo Maci' via CodenameOne 
>>> Discussions  wrote:
>>>
>> My Codename app has a BrowserComponent with a text editor inside. 
 When JavaFX was used the editor was displayed but had some issues.
 Now I am running the same code with CEF support. I had to copy the 
 .idea-IC-201.7223.91/jbr/lib/libjawt.so file into the