On 03/05/17 22:51, Rob Lemley wrote: > I had no problems getting the html client to run in an iframe. I > preferred that method over trying to get it in a modal because I > didn't want the different javascript libraries to interfere with each > other by accident. Ah, right. You're talking about a modal browser window. (and I was thinking of modal native windows..)
> Antoine, One thing I have been meaning to ask, I'd like the ability to > pass the websocket URL in as an option to the Client() constructor. Is > that something you'd be willing to add? My use case is getting an Xpra > client to run in another web application that uses its own websockets > on other URLs and it would be nice to have Xpra follow the same > pattern. The client takes many options, including "host", "port" and the "ssl" flag. A path could easily be added to that. Feel free to make a ticket for it, it really shouldn't take long to implement. Cheers Antoine > > Thanks! > > -Rob > > On Wed, May 3, 2017 at 2:25 AM, Antoine Martin via shifter-users > <[email protected]> wrote: >> On 03/05/17 12:32, Titusi Forum via shifter-users wrote: >>> I got a quick question: >>> >>> If I try to open xpra html5 client inside a modal window/iframe or a frame >>> ... do you foresee any issues? >> The window attributes should only affect how the client's window manager >> handles it, not the contents of the window itself. >> (i)frames are also no different from regular windows, as far as the HTML >> and Javascript code running within them is concerned. (by design) >> >> It should be trivial to try it out. >> But maybe I am misunderstanding your question? >> >> Cheers >> Antoine >> >>> >>> Thanks in advance! >> _______________________________________________ >> shifter-users mailing list >> [email protected] >> http://lists.devloop.org.uk/mailman/listinfo/shifter-users _______________________________________________ shifter-users mailing list [email protected] http://lists.devloop.org.uk/mailman/listinfo/shifter-users
