Re: GNOME Shell browser plugin

Le vendredi 06 novembre 2015 à 16:05 +0100, Carlos Garcia Campos a écrit : > Of course it would be better to switch to any other thing that works > on > all browsers, but what? We could create a websocket service on localhost, and create a simple Web page that speak with that service. Websocket

Re: GNOME Shell browser plugin

Michael Catanzaro writes: > Hi, > > I am planning to propose blacklisting the GNOME browser plugin in > WebKit, because it has been causing crashes and hangs for several > years, and we don't know how to fix it. My recent commit apparently > didn't help; when we do WebKit

Re: GNOME Shell browser plugin

On Fri, Nov 6, 2015 at 7:05 AM Carlos Garcia Campos wrote: > Michael Catanzaro writes: > > > Let's fix the issues instead, then. > > Michael, myself, Scott and others discussed this at GUADEC. Here are the minutes from that talk. We had outlined some

Re: GNOME Shell browser plugin

This is what it started out as. An HTTP server hosted locally which the website would poke. The issue happens with multi-user support -- how do you pick a port number that works for all users on a system? While I don't have much to do with extensions anymore, my advice would be to build a local

Re: GNOME Shell browser plugin

I had started working on a service for extensions with sockets and authentication last year, but I didn't manage to finish. I'm re-writing it with a different design and I hope I can finish in 3-4 months. I think it would be a better idea to skip sockets that need lots of work, and just provide a

Re: GNOME Shell browser plugin

On Fri, 2015-11-06 at 16:05 +0100, Carlos Garcia Campos wrote: > Are those bugs in WebKit or the plugin itself? I don't know. I guess most likely there are bugs in both places, but if I knew what was wrong I wouldn't be proposing this. The plugin apparently works fine in Firefox, so there's at