[Webkit-unassigned] [Bug 124269] New: NPAPI plugins ignore savedData when calling NPP_Destroy and NPP_New
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Nov 13 00:26:54 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=124269
Summary: NPAPI plugins ignore savedData when calling
NPP_Destroy and NPP_New
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Plug-ins
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: cf at cfrost.dk
Hi
Initially I made some observations that led me to look deeper into the NPAPI specification to find out what the expected behaviour should be. The initial observations are:
1) I have a NPAPI video/mp4 object which is instantiated without the "data=".
2) Later on from javascript the "data" property is set and handled on the plugin.
3) Then I change the "className" (again from Javascript) of the object to change its size on the page.
4) This results in a reattachment of the element inside WebKit and the plugin is destroyed and instantiated again.
My problem is that when destroyed and initialised all context in the plugin is lost, and all fields (like "data") needs to be given to the plugin again. But this is not the case. Therefore, when having changed to the correct stylesheet it's not possible to start the video since the "data" field is not known.
>From the NPAPI specification it's clear that NPP_Destroy and NPP_New should allow the use of "savedData" to store and re-store the state of a plugin. However this data is ignored in WebKit, e.g. see Source/WebKit2/WebProcess/Plugins/Netscape/NetscapePlugin.cpp where NPP_Destroy is called and the saved data is discharged immediately after.
Please refer to:
https://developer.mozilla.org/en-US/docs/NPP_Destroy
https://developer.mozilla.org/en-US/docs/NPP_New
Best regards
Christian
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list