[Webkit-unassigned] [Bug 72484] [v8] Exception thrown in npObjectInvokeImpl may overwrite the exception message thrown by NPN_SetException

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=72484





--- Comment #16 from Hongbo Min <hongbo.min at intel.com>  2011-12-03 06:17:06 PST ---

(In reply to comment #15)
> (In reply to comment #14)
> > For Safari, Firefox and Opera, they are both not using v8 as javascript engine. In this sense, this patch serves as a chromium-specific bug-fixing.  It just provides a chance to solve such an issue but depending on the implementation in browser-side. 
> > 
> > In order to make chromium throwing the correct message set by NPN_SetException, chromium itself needs to apply another patch as described at http://codereview.chromium.org/8576001/
> > 
> > I had a try on Safari/Firefox/Opera, they also can't throw the expected message set by NPN_SetException. 
> > 
> > As far as I concerned,  this patch is the simplest solution for solving this issue for chromium/v8. I have also tried other solution, but will involve more changes even if NPAPI interface spec.
> 
> If the v8/chromium behavior is currently the same as Safari, Firefox, and Opera, then we shouldn't change our behavior. Plugin authors expect chromium's NPAPI implementation to match the other NPAPI implementors as much as possible.

>From this aspect, it makes sense that we need to match the same behavior between Safari, Firefox and chromium, etc, although it is indeed a bug. 

> 
> If you feel there is a bug in the NPAPI specification, you're welcome to talk to plugin-futures (https://mail.mozilla.org/listinfo/plugin-futures) about it. Without plugin-futures support for changing the behavior, however, I don't think this patch is a good idea.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.