Robert Kaiser wrote:
JeffM schrieb:
...then there is Google included an actual API for extensions
in their Chrome Browser.
There's an "Add-On SDK" for Mozilla software that does the same. Still,
add-ons built with that only or the Google Chrome API can do so much
less than full-blown add-ons for Mozilla products that I don't expect
all add-ons to switch to using it.
The thing is, in most cases the add-on didn't break, it just needs to have
install.rdf updated. And that is really hostile to users, when a pop-up could
ask if the user wanted to install and warned that it might break things. That is
so much safer than having users unpacking, modifying, repacking, and then trying
an add-on.
Follow this logic: not only are there more users who can figure out a [TRY IT]
button without messing up, but the number of people distributing hacked versions
of add-ons would drop to zero. Sooner or later someone will figure out that
offering an "updated" add-on is a great way to slip in malware.
These are the prices you pay for being a pioneer:
Not just for being a pioneer, but also for allowing many more degrees of
freedom that others.
Could you at least hint WHY a working "disable compatibility check" in button or
about:config form is not available, while developers tell people to hack the
add-on which has higher risks. The add-on manager whines that compatibility
checking is disabled, but clearly it isn't. At least a button would force the
user to consider the issue before blindly hacking install.rdf.
--
Bill Davidsen <[email protected]>
We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination. -me, 2010
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
