{"action":"created","issue":{"url":"https://api.github.com/repos/dmarmor/epichrome/issues/55","repository_url":"https://api.github.com/repos/dmarmor/epichrome","labels_url":"https://api.github.com/repos/dmarmor/epichrome/issues/55/labels{/name}","comments_url":"https://api.github.com/repos/dmarmor/epichrome/issues/55/comments","events_url":"https://api.github.com/repos/dmarmor/epichrome/issues/55/events","html_url":"https://github.com/dmarmor/epichrome/issues/55","id":133863322,"number":55,"title":"Sudden incompatibility with BrowserFairy","user":{"login":"rschend","id":10687740,"avatar_url":"https://avatars.githubusercontent.com/u/10687740?v=3","gravatar_id":"","url":"https://api.github.com/users/rschend","html_url":"https://github.com/rschend","followers_url":"https://api.github.com/users/rschend/followers","following_url":"https://api.github.com/users/rschend/following{/other_user}","gists_url":"https://api.github.com/users/rschend/gists{/gist_id}","starred_url":"https://api.github.com/users/rschend/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rschend/subscriptions","organizations_url":"https://api.github.com/users/rschend/orgs","repos_url":"https://api.github.com/users/rschend/repos","events_url":"https://api.github.com/users/rschend/events{/privacy}","received_events_url":"https://api.github.com/users/rschend/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-16T02:12:44Z","updated_at":"2016-02-16T05:22:21Z","closed_at":null,"body":"First, a big thanks to @dmarmor for the latest update. It sounds like he's busy otherwise, so it was a nice surprise to see the broken icon issue sorted that quickly.\r\n\r\nI've been using Epichrome with [BrowserFairy](http://www.browserfairy.com/) to create pretty great workflow, where I force all work-related links to open in my work-specific SSB (the one hooked up to my work Google profile, with all its bookmarks, extensions, etc.). But this has only been possible using the text rules in BF. Even tho BF can direct links based on which app the link is coming from, it can't do it when the app is an Epichrome SSB. The dev says this is because the links are actually coming via a Python script, and not from Chrome itself. He says he plans on adding this functionality soon, which will be great.\r\n\r\nIn the meantime, it looks like 2.1.10 has broken BF compatibility altogether. Now, when BF tries to direct a link to one of my SSBs, if that SSB isn't already open, then the icon bounces but nothing happens. If it is already open, then a duplicate copy of the icon briefly shows in the dock, then goes away. Either way, I get this console error:\r\n\r\n![bf-epi console](https://cloud.githubusercontent.com/assets/10687740/13065175/b453a16e-d427-11e5-900a-c85cf72c6efd.jpg)\r\n\r\n'FFD Chrome' is the name of my SSB.\r\n\r\nIs this possibly a result of other changes in the new version?\r\n\r\nI consider the fact that Epichrome worked with BrowserFairy _at all_ was great, so no complaints here that it might no longer play nice with it. But man, it really could make for an amazing combination."},"comment":{"url":"https://api.github.com/repos/dmarmor/epichrome/issues/comments/184526591","html_url":"https://github.com/dmarmor/epichrome/issues/55#issuecomment-184526591","issue_url":"https://api.github.com/repos/dmarmor/epichrome/issues/55","id":184526591,"user":{"login":"dmarmor","id":3878113,"avatar_url":"https://avatars.githubusercontent.com/u/3878113?v=3","gravatar_id":"","url":"https://api.github.com/users/dmarmor","html_url":"https://github.com/dmarmor","followers_url":"https://api.github.com/users/dmarmor/followers","following_url":"https://api.github.com/users/dmarmor/following{/other_user}","gists_url":"https://api.github.com/users/dmarmor/gists{/gist_id}","starred_url":"https://api.github.com/users/dmarmor/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dmarmor/subscriptions","organizations_url":"https://api.github.com/users/dmarmor/orgs","repos_url":"https://api.github.com/users/dmarmor/repos","events_url":"https://api.github.com/users/dmarmor/events{/privacy}","received_events_url":"https://api.github.com/users/dmarmor/received_events","type":"User","site_admin":false},"created_at":"2016-02-16T05:22:21Z","updated_at":"2016-02-16T05:22:21Z","body":"Well, I've just confirmed this bug on my system (I use Browser Fairy too). No real idea what could be causing it, though. The big change in architecture came in v2.1.8, where I changed over to using a full clone of Chrome as an engine inside each Epichrome app (that was necessary to overcome a problem that was causing Epichrome apps to not properly use the GPU). I would've thought if something was going to break Browser Fairy compatibility, that would've done it. I honestly can't think what I've changed in 2.1.10 that would break things...\r\n\r\nThank you also for letting me know about the text rule situation--good to know the BF dev is aware of us! They're absolutely right, too, links from Epichrome apps are actually coming from a python script, which is the server listening on the other end of the Epichrome Helper extension. This is the only way to route URLs out of Epichrome apps (or out of Chrome itself as far as I know).\r\n\r\nIf I get a little time here and there, I'll try to poke around and see if I can figure out what's causing the breakage with BF. And if you figure out anything or hear anything from the BF dev, let me know?"}}