Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Change issue status back to 'Assigned'
Pending code changes (auto-populated)
Tracks the current rank of this item in the teams backlog [ID: 1225362]
Build number, such as 117.0.5911.2 [ID: 1223033]
Remove item
[ID: 1223031]
Internals>Plugins
Platform>Extensions
Select items in the list
Supplemental component tags only. Set main component first. [ID: 1222907]
[ID: 1223136]
he CWE ID for the type of security defect the current issue is describing. [ID: 1410892]
Design doc to be reviewed. [ID: 1223032]
[ID: 1223131]
How many engineer days the task is estimated to take. [ID: 1225337]
[ID: 1223081]
[ID: 1223087]
[ID: 1223134]
Milestone(s) impacted by this issue. [ID: 1223085]
Date of next expected progress update or deadline for providing requested information. [ID: 1225154]
[ID: 1223083]
[ID: 1223084]
[ID: 1223086]
[ID: 1223034]
Link to incidents in IRM as a result of this ticket. [ID: 1300460]
[ID: 1223088]
[ID: 1223135]
This field contains Gerrit urls of code changes that ‘fix’ a security bug (i.e., excluding logging/cleanup commits) and is used when a singular fix cannot be uniquely identified from the existing “Code Changes” field. The change can be in the chromium repo or any other third_party repo. [ID: 1358989]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Internals
Platform
[ID: 1253656]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
Steps to reproduce the problem:
1. Install extension on Chrome while only default user exists
2. Write 'navigator.plugins' in console (see that there is a plugin named 'CloudShare plugin')
3. Add another Chrome user, and install the same extension
4. Write 'navigator.plugins' in console
5. Plugin is not visible at all, although in chrome://plugins it's visible
What is the expected behavior?
Plugin should be available and visible from navigator.plugins for all Chrome users, just like the extension is
What went wrong?
When using multiple users functionality, the extension's plugin (a NPAPI plugin) is only available to the first user who opened a Chrome instance
It's not with the order of user creation, it's with the order which the Chrome instance were opened - the first one sees the plugin, and the next ones don't
WebStore page:
Did this work before? No
Chrome version: 27.0.1453.110 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)