Closed
Bug 980133
Opened 10 years ago
Closed 10 years ago
Cisco Jabber SDK for Web - request to whitelist plugin
Categories
(Firefox Graveyard :: Plugin Click-To-Activate Whitelist, defect)
Firefox Graveyard
Plugin Click-To-Activate Whitelist
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 30
People
(Reporter: vgargeya, Assigned: benjamin)
References
Details
(Whiteboard: application complete - accepted - qa complete)
Attachments
(1 file)
126.43 KB,
application/vnd.openxmlformats-officedocument.presentationml.presentation
|
Details |
<<Please supply the following information for new plugin whitelist requests>> Plugin name: Cisco Web Communicator Vendor: Cisco Systems, Inc. Point of contact: Vibhavaree Gargeya Current version: 3.0.6 Download URL: http://software.cisco.com/download/release.html?mdfid=283882159&softwareid=283995793&release=9.0%25281%2529&relind=AVAILABLE&rellifecycle=&reltype=latest Sample URL of plugin in use: Not publicly available Plugin details: Please see attached screenshots for Windows and Mac Are there any variations in the plugin file name, MIME types, description, or version from one release to the next? Yes, the version number changes Are there any known security issues in current or older versions of the plugin? Not in the current version. Older versions were using an older libxml2 library that had security issues. This has been addressed in 3.0.6
Assignee | ||
Comment 1•10 years ago
|
||
You also need to provide an HTML transition plan. You can provide that as a comment in the public bug here or privately by email if necessary.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(vgargeya)
Our plan to move away from NPAPI is to install the plugin code natively, and use js-ctypes to communicate between the application and the native code.
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(vgargeya)
Assignee | ||
Updated•10 years ago
|
Whiteboard: application complete
Assignee | ||
Updated•10 years ago
|
Whiteboard: application complete → application complete - accepted
Assignee | ||
Comment 3•10 years ago
|
||
about:plugins data Windows Cisco Web Communicator File: npCiscoWebCommunicator.dll Path: C:\Program Files\Cisco System\Web Communicator\npCiscoWebCommunicator.dll Version: 3.0.6.37292 Cisco Unified Communication System Release 9.2 MR6 : CWC version 3.0.6.168364 MIME Type Description Suffixes application/x-ciscowebcommunicator CiscoWebCommunicator application/x-cisco-cwc-videocall MacOS Cisco Web Communicator File: CiscoWebCommunicator.plugin Path: /Library/Internet Plug-Ins/CiscoWebCommunicator.plugin Version: 3.0.6.168364 State: Enabled Cisco Unified Communications System Release 9.2 MR6 : CWC version 3.0.6.168364 MIME Type Description Suffixes application/x-cisco-csc-videocall Cisco Web Communicator video call plugin application/x-ciscowebcommunicator Cisco Web Communicator browser plugin
Assignee | ||
Comment 4•10 years ago
|
||
Builds for testing are now available at http://people.mozilla.org/~bsmedberg/plugin-whitelisting-91f6f3380041/ Please do a QA pass using a new Firefox profile to ensure that the plugin activates without a popup and appears as "Always Activate" in the addon manager. Report back in this bug when QA is complete. Please try to complete QA by the end of this week.
Flags: needinfo?(vgargeya)
- Used the build available for testing as linked above - Created a new profile - - Tested both 9.2MR5 and 9.2MR6 of the plugin
Flags: needinfo?(vgargeya)
- Used the build available for testing as linked above - Created a new profile - Plugin activates without a pop-up and appears as "Always Activate" in addon manager - Tested both 9.2MR5 and 9.2MR6 of the plugin So QA is complete, and plugin appears to be white listed properly when using a new profile. Question on this - why is a new profile required? I tested using the old (existing) profile, and the plugin was not white listed. What will users who upgrade to a later version of Firefox - that blocks plugins by default see? Will the plugin be white listed for upgrades?
Flags: needinfo?(benjamin)
Assignee | ||
Comment 7•10 years ago
|
||
Users who haven't changed any prefs shouldn't see any change. For users who specifically made your plugin "ask to activate" in the addon manager, it will continue to be click-to-play. For users who have chosen "block plugin" on specific sites, it will continue to be blocked on those sites.
Flags: needinfo?(benjamin)
Whiteboard: application complete - accepted → application complete - accepted - qa complete
Note on Comment 6 - tests were executed on both Windows 7 and Mac OS X 10.9.2
Assignee | ||
Comment 10•10 years ago
|
||
Fixed for Firefox 30 beta 1 in bug 992995.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Target Milestone: --- → Firefox 30
Updated•8 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•