RESOLVED INVALID 22079
SafariStand's "Load Plug-in Manually" feature broken in latest build. 
https://bugs.webkit.org/show_bug.cgi?id=22079
Summary SafariStand's "Load Plug-in Manually" feature broken in latest build.
Nabeel Rahimpour
Reported 2008-11-04 23:14:29 PST
The latest build of WebKit as of 2:00 am EST on Wednesday, November 5, 2008 causes a problem with one of the components of the SafariStand plug-in. Specifically the feature that SafariStand has to disable plug-ins from loading automatically. After upgrading to the latest version, plug-ins load no matter what, unless they are totally disabled in the Safari preference menu.
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2008-11-05 04:44:14 PST
*** Bug 22075 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 2 2008-11-05 04:44:31 PST
*** Bug 22076 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 3 2008-11-05 04:44:41 PST
*** Bug 22077 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 4 2008-11-05 04:44:55 PST
*** Bug 22078 has been marked as a duplicate of this bug. ***
Alexey Proskuryakov
Comment 5 2008-11-05 04:46:06 PST
Please report this to SafariStand developers. We can not support unsupported extensions.
Nabeel Rahimpour
Comment 6 2008-11-05 09:29:36 PST
Firstly, I would like to apologize for the duplicates, I didn't realize that the back and fourth was causing duplicate entries. Secondly, Really? Invalid? WebKit changes and causes a Plug-in to break, and it's the Plug-ins problem? Maybe I should clarify: The previous versions of WebKit and the latest release of Safari work with this plug-in fine, however the one at 2:00 am EST on Wednesday, November 5, 2008 no longer works. Plug-ins breaking is something that happens quite often in WebKit (for Flash, Java, Java-script), and being the nightly build, it's expected, and I expect you hear about a lot of them. This one being a slightly more obscure one, I decided to let you know. If you still believe it's invalid though, then I'll leave it be.
Alexey Proskuryakov
Comment 7 2008-11-05 14:20:21 PST
Yes - I realize that this is really unfortunate from end user point of view, but "Safari enhancers" such as SafariStand rely on undocumented inner workings of WebKit that we just cannot preserve going forward (we cannot even really know what they depend upon, as most are not open source). As far as plug-ins that work via official documented APIs are concerned, we certainly must maintain compatibility, please do file bugs if something breaks! Flash and Java are examples of things that shouldn't break (not sure what you mean by Java-script here). In general, plug-ins that work in both Safari and Firefox fall in this category.
Nabeel Rahimpour
Comment 8 2008-11-05 16:01:54 PST
Ah OK, now I understand, thank you for taking the time to clear that up for me. And as for the Java-Script comment, I have had Java-script break or not work properly on certain pages after an update, however, that isn't a plugin of Safari/WebKit, so I guess worded that badly. Thanks for your time. Sincerely, Nabeel Rahimpour
Note You need to log in before you can comment on or make changes to this bug.