Closed Bug 117770 Opened 23 years ago Closed 23 years ago

NPN_GetURLNotify and NPN_PostURLNotify do not fire notification if notifydata is null

Categories

(Core Graveyard :: Plug-ins, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 127259

People

(Reporter: serhunt, Assigned: serhunt)

Details

(Keywords: testcase)

Those API calls take a pointer to a custom data (notifydata) which is supposed 
to be passed back to the plugin when notification comes, so that the plugin can 
distinguish one notification from another. For some reason before firing the 
notification we check this |notifydata| for null:

  if (callbacks->urlnotify != NULL && mNotifyData != nsnull &&
      strnicmp(mNPStream.url, macromediaurl, strlen(macromediaurl)) != 0 )
  {
    ...
    NS_TRY_SAFE_CALL_VOID(CallNPP_URLNotifyProc(callbacks->urlnotify,
                                                npp,
                                                mNPStream.url,
                                                nsPluginReason_Done,
                                                mNotifyData), lib);
    ...
  }
http://lxr.mozilla.org/seamonkey/source/modules/plugin/base/src/ns4xPluginInstan
ce.cpp#164

The Tester plugin easily shows the problem and the difference with NS4x.
Keywords: 4xp
nominating nsbeta1, mozilla.10

*** This bug has been marked as a duplicate of 127259 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"

Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.