[Webkit-unassigned] [Bug 9468] AcidSearch crashes WebKit

bugzilla-daemon at opendarwin.org bugzilla-daemon at opendarwin.org
Fri Jun 16 13:13:17 PDT 2006


http://bugzilla.opendarwin.org/show_bug.cgi?id=9468


hyatt at apple.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX




------- Comment #4 from hyatt at apple.com  2006-06-16 13:13 PDT -------
Resolving WONTFIX.

This is not a crash in SIMBL.  It is a crash in AcidSearch.  We are definitely
committed to SIMBL working with Safari.  However there is nothing we can do
about keeping individual plugins working in nightly builds.  (Firefox has the
exact same problem.  Extensions can rarely be kept working from version to
version.)

People also keep requesting that Safari have an official "browser extension
API", but I don't think people really understand what that means.  The whole
reason people use mechanisms like SIMBL is it allows them to really patch into
any place in the Safari browser code, which is often a necessity to even do the
kinds of extensions that people use.  Some sort of simplistic official API will
never be able to cover all of the functionality added by extensions.

Note that Firefox itself has no extension API either, and basically relies on
extensions patching into its browser JS/XUL files.  None of that is "public
API", and the extensions have conflict issues, clashing problems, and
versioning trouble.  Firefox does have one feature that would be nice to have,
which is that the extensions are versioned and can be turned off at least when
the browser is upgraded (or auto-updated from a Web site).  Such a feature
could (and should) be built into SIMBL in my opinion, since it is acting as the
extension management layer.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list