| Issue 188028: | Test that Extensions with NPAPI plugins do not run the plugin once installed | |
| 3 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
We don't want Chrome extensions with NPAPI plugins to be installable on chrome os. Code has been checked in to prevent this, but we should ensure it doesn't regress. This shouldn't be that hard...extensions of this type exist in Chrome test data directory, so we can just take one of those and write an autotest that spins up an HTTP server that serves the extension. Make Chrome go to that URL, and then verify that the extension does not get installed. There may be a dialog box to navigate around.
Nov 15, 2010
(No comment was entered for this change.)
Labels:
-Mstone-R9.x Mstone-R10
May 2, 2011
Recently, changes were landed in chrome to allow extensions with plugins to be installed, but then the plugins just won't work. I don't really see how this is a better UX, but...regardless, this test will need to change to vet that, once an extension with a plugin is installed, the plugin will not be run by the browser. I suppose this could be done by: 1) creating a simple test extension that works on Linux Chrome by installing some NPAPI plugin 2) Getting that extension installed at runtime on Chrome OS, either by pointing the browser at a local HTTP server that serves the .crx and then accepting the installation, or by somehow pre-installing it. I think power_LoadTest might pre-install an extension 3) Somehow make it so you can tell if the plugin got run...maybe it calls back to the HTTP server running in the test harness or something? Or the extension itself can detect what happens and report it back to the harness?
Summary:
Test that Extensions with NPAPI plugins do not run the plugin once installed
Cc: su...@chromium.org zelidrag@chromium.org Labels: -Test-Functional -Pri-2 -Mstone-R11 Test-Security Pri-1 Mstone-R13
Jun 27, 2011
(No comment was entered for this change.)
Labels:
-Mstone-R13 Mstone-R14
Jul 25, 2011
(No comment was entered for this change.)
Owner:
nkostylev@chromium.org
Labels: -Mstone-R14 Mstone-R15
Sep 14, 2011
(No comment was entered for this change.)
Labels:
-Mstone-R15 Mstone-R16
Oct 6, 2011
(No comment was entered for this change.)
Status:
Assigned
Owner: ivankr@chromium.org Cc: nkostylev@chromium.org
Oct 19, 2011
(No comment was entered for this change.)
Labels:
-Mstone-R16 Mstone-R17
Dec 1, 2011
(No comment was entered for this change.)
Labels:
-Mstone-R17 Mstone-R18
Feb 3, 2012
(No comment was entered for this change.)
Labels:
-Mstone-R18 Mstone-R19
Mar 19, 2012
(No comment was entered for this change.)
Labels:
-Mstone-R19 Mstone-X
Mar 19, 2012
(No comment was entered for this change.)
Status:
Available
Apr 4, 2012
(No comment was entered for this change.)
Labels:
-Area-DesktopUI Area-UI
May 1, 2012
We changed a lot since this bug was opened. Please re-file this bug in crbug.com if you can reproduce this bug on M20+. Thanks a lot for your help!
Status:
WontFix
Mar 6, 2013
(No comment was entered for this change.)
Labels:
OS-Chrome
Mar 9, 2013
(No comment was entered for this change.)
Labels:
-Team-UI -Area-UI Cr-UI-Shell Cr-UI
|
||||||||||||
| ► Sign in to add a comment | |||||||||||||
Labels: Mstone-R9 Pri-2