| Summary: | Google Chrome Frame not enabled for use in the Browser widget | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Patrick Mueller <pmuellr> |
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | Grant Gayed <grant_gayed> |
| Severity: | normal | ||
| Priority: | P3 | CC: | AndersHessellund, erdal.karaca.de, nikita, remy.suen |
| Version: | 4.0 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Patrick Mueller
I had sent a note to Alex Russell at Google, who works on GCF, about the issue, and he responded with a note indicating that GCF isn't designed to work if you use the IE ActiveX control. Meaning (I think), that GCF shouldn't be expected to work with the SWT Browser widget, as is. He did indicate that you should be able to use GCF stand-alone as an ActiveX control, and that the code snippet from the original Chrome bug should work, or be close to how it's done: http://code.google.com/p/chromium/issues/detail?id=25448 So, assuming that the snippet can be made to work, and that we'd like to be able to use GCF from the SWT Browser widget, I think we will need to enable it as an alternative implementation, as we've done with other alternate browser implementations (like the GTK WebKit version on Linux vs default XULRunner impl, for example). This is a one-off bulk update. (The last one in the triage migration). Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process: https://wiki.eclipse.org/SWT/Devel/Triage See Bug 518478 for details. Tag for notification/mail filters: @TriageBulkUpdate Google Chrome Frame isn't available anymore. |