Adding Browser component to the stack freeze LC.

If you find an issue in LiveCode but are having difficulty pinning down a reliable recipe or want to sanity-check your findings with others, this is the place.

Please have one thread per issue, and try to summarize the issue concisely in the thread title so others can find related issues here.

Moderator: Klaus

Post Reply
liveme
Posts: 240
Joined: Thu Aug 27, 2015 5:22 pm

Adding Browser component to the stack freeze LC.

Post by liveme » Fri Feb 19, 2021 7:13 pm

HI,
Running Livecode 9.6.1 indy

I have been trying to add the Browser Component on a fresh new stack with no success.
1rst time ever, never tried it before.

Problem is, as soon as I start draging the B component toward the stack. The whole LC ide falls into a "buggy" state.
- noticeable is :
1) most of surrounding components beside the original Browser location, becomes invisible (wiped out) only 3 icons
remains visible, those before it. The below components in the other section below, remain visible.
2) there is nomore dropping of the browser onto the stack.. The IDE falls into a frozen state...
3) there is no more control over the whole IDE, one can close the 2 main menu box...and the empty LC windows remains open..
n way to close it or escape...
To gain normal access to LC IDE again, only a rebooting is possible and restarting LC again. Rest of the Desktop apps keep runing ok.
No error message...just a frozen window.

*This happens on 2 dif distro of Linux, LinuxMint20 and Zorin 15.
Will post a shot right after another trial...

Please find pictures joined :
1 creating new app with 2 buttons and a field.jpg
1
3 Dropping the Browsing component on the stack.jpg
3
Last edited by liveme on Fri Feb 19, 2021 7:31 pm, edited 1 time in total.

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10045
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: Adding Browser component to the stack freeze LC.

Post by FourthWorld » Fri Feb 19, 2021 7:28 pm

This is a known issue. There is currently no functioning browser widget for the LiveCode engine on Linux. Given the limitations of the CEF browser engine it's based on, it's not currently clear when or even if that functionality can be made to work on Linux.

Prompted by your post, I've reviewed the Release Notes, and though there's a warning about limitations with the browser window on Linux it's far from complete. I just filed a bug report suggesting the Release Notes clarify that the browser widget isn't currently available for Linux.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

liveme
Posts: 240
Joined: Thu Aug 27, 2015 5:22 pm

Re: Adding Browser component to the stack freeze LC.

Post by liveme » Fri Feb 19, 2021 7:33 pm

ouch, bummer...
and adding that it will freeze your IDE session too !

So Its not planned to be solved with the 6.2 or next versions ?
:roll:

could one load an installed browser such as firefox, and use that to display results then ?

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10045
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: Adding Browser component to the stack freeze LC.

Post by FourthWorld » Fri Feb 19, 2021 7:42 pm

liveme wrote:
Fri Feb 19, 2021 7:33 pm
ouch, bummer...
and adding that it will freeze your IDE session too !
Yes, I mentioned that in my report.
So Its not planned to be solved with the 6.2 or next versions ?
There is of course much interest among us Linux folk to see this done, but it turns out that CEF is a weird project, at least in terms of expecting a general-purpose embeddable browser engine. CEF maintainers keep it going only for more specialized use cases. If we can find another embeddable engine I'm sure the team would be happy to consider it. In the meantime, CEF has proven troublesome for our needs.
could one load an installed browser such as firefox, and use that to display results then ?
Yes, that's what I'm doing for now, using the user's default browser as a helper app rather than embedding. Nextcloud does that with their auth sequence, so at least I'm in good company.

For some designs it's not optimal, but for many uses it can be better than embedded, so the user not only gets reliable rendering but it happens in their own choice of browser, where they can interact with it just as they're accustomed to with any web site.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

Post Reply