Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clicktoplugin not compatible with google hangouts (without extra config) #156

Open
r-owen opened this issue Dec 5, 2015 · 3 comments
Open

Comments

@r-owen
Copy link

r-owen commented Dec 5, 2015

With ClickToPlugin installed I find that google hangouts fails: it tells me the necessary plugins need to be given permission, but Safari doesn't ask me to allow permission. I have worked around the problem by adding this ClickToPlugin's Control Lists preference panel:

Allow plugins on these sites: hangouts.google.com plus.google.com

however, this is a bit heavy-handed because it enables all plugins instead of just the few needed for hangouts. So this is a request to offer a way to enable specific plugins for specific sites and/or make ClickToPlugin support google hangouts by default.

Note that this google page has a link for joining a test hangout (though it uses plus.google.com instead of hangouts.google.com, which is what my normal hangouts use): [https://support.apu.edu/entries/99342956-How-to-get-setup-on-Google-Hangouts]

Thank you for this wonderful Safari extension. I can hardly imagine browsing without it.

@hoyois
Copy link
Owner

hoyois commented Dec 5, 2015

You can get much finer whitelisting using the "Allow plug-ins from these sources" list instead. This matches the URLs of the plugin objects themselves (which you can find by looking at the page source or enabling the "Block plug-ins manually" option).

You can also have the extension ignore the Google Talk plugin. This seems like the most efficient solution, since presumably there's no reason to ever block this plugin.

@r-owen
Copy link
Author

r-owen commented Dec 5, 2015

Thank you.

For the record, if I block manually I see two things that could be blocked:

Plug-in: Google Talk Plugin
Location: https://plus.google.com/hangouts/_/apu.edu/field-ed-youth
Source:
Position: (0,0)
Size: 1×1

Plug-in: Google Talk Plugin Video Renderer
Location: https://plus.google.com/hangouts/_/apu.edu/field-ed-youth
Source:
Position: (0,0)
Size: 1×1

I tried putting "https://plus.google.com/hangouts/_/apu.edu/field-ed-youth" into the "Allow plugins from these sources" list, but (no surprise) it didn't work. I assume more info is required, but I'm not sure how to figure out what it might be.

I am reluctant to allow the two Google Talk plugins globally since I don't want to give badly behaved or hacked web sites access to my microphone or video camera. I feel safer allowing Google to use all my plugins.

What I'd really like is to be able to say "the following web site(s) can use the following specific plugins", but I realize that's not presently possible.

Or I could just run Chrome when I want to use hangouts, which was my solution until I found the workaround.

@hoyois
Copy link
Owner

hoyois commented Dec 6, 2015

Some plugins work without a source. It makes sense that Google Talk works this way, actually. I think this also means that the kind of hacking you're afraid of is simply not possible.

I tried putting "https://plus.google.com/hangouts/_/apu.edu/field-ed-youth" into the "Allow plugins from these sources" list, but (no surprise) it didn't work. I assume more info is required, but I'm not sure how to figure out what it might be.

That would have to go in the locations whitelist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants