301177 - window bottom line DOCTYPE ... imageZoom.dtd

Status: VERIFIED INVALID

(SeaMonkey :: General, defect)

Description

[Heinz Kohl]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050715 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b3) Gecko/20050715 SeaMonkey/1.0a

After "successful" installing imageZoom, every page is showing a very thick
annoying bottom line containíng the text / eror message:

<!DOCTYPE overlay SYSTEM "chrome://imageZoom/locale/imageZoom.dtd">
-------------------------------------------------------------------^

(no image zoom potential as in Firefox, no visible possibility to thrpw away
imageZoom)

Reproducible: Always

Steps to Reproduce:
1. installing imageZoom
2. open any page
3.

Comment 1

[Jaime Mitchell (use [e-mail] for email)]

This is a problem with the image zoom extension not in seamonkey -> Invalid.

Please contact the image zoom author about the problem.

Comment 2

[Heinz Kohl]

.. o.k. and not very surprising, but the Mozilla tools to point at the error and
to remove the error provoking tool are not very impressive, just to say :-(

Comment 3

[Heinz Kohl]

(In reply to comment #1)
> This is a problem with the image zoom extension not in seamonkey -> Invalid.
> 
> Please contact the image zoom author about the problem.

No, this seems to be more a compatibility/interface problem between Seamonkey
and Thunderbird (only Thunderbird with installed imageZoom) (my main mail
utility. Don't want to use an alpha test version for mailing).

Seamonkey should be able to run correctly as a browser together with
Thunderbird, without conflict with addons for thunderbird.

Of course, this specific problem could eventually be handled in another way, but
anyway, there should be no trouble in interfacing between Thunderbird and
Seamonkey. 

If not, it's not usable for me on my main mail PC.

Details: 
I've completely deinstalled Seamonkey, then made it new using nightly build 
200507109 (using another directory).

Same effect as before.

I've an installed imageZoom functionality only in Thunderbird, which I'm using
as main mail utility.

As a work around I've tried also to install imageZoom on Seamonkey -
"successfully installed", but not effect.
O.k., this last one is to expect as an imageZoom problem.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

Again, this is invalid.  There's no way an extension installed in Thunderbird
*only* will affect SeaMonkey builds.  I just installed this extension in the
2005-07-15-05 trunk SeaMonkey build, and see the same exact error you mention,
but to repeat, this is not a bug in SeaMonkey, but rather something for the
extension author to deal with.  (As there hasn't been an update on the homepage
since October 25, 2004, I'd say currently you're stuck.)

So, as the author has already pointed out in
http://imagezoom.yellowgorilla.net/faq/:

"...there is no built in way of uninstalling extensions in these applications, I
recommend that you use the Extension Uninstaller extension to uninstall
extensions from these applications".

You can also just create a new profile in SeaMonkey and delete the old one, but
of course you'll lost your other data (POP3 email, bookmarks, etc).

Comment 5

[Heinz Kohl]

                     LOST IN THE SEA WITH SEAMONKEY ?!
(In reply to comment #4)
> There's no way an extension installed in Thunderbird
> *only* will affect SeaMonkey builds.

... but the same extension in Thunderbird is working 

> http://imagezoom.yellowgorilla.net/faq/:
> 
> "...there is no built in way of uninstalling extensions in these applications, I
> recommend that you use the Extension Uninstaller extension to uninstall
> extensions from these applications".

Thanks for your hint. 
It's necessary to install:
- the extension manager
- the extension uninstaller

After some googling, I found a working link to the uninstaller, and together
with it I found the extension manager:
http://mozmonkey.com/

But BOTH SERVICES, AT LEAST ONE LIKE THE EXTENSION MANAGER, SHOULD BE PART OF a
Seamonkey STANDARD DISTRIBUTION!

At now, Seamonkey is in part working as an user dungeon.
Without change, you may get any error messages like mine, making and earning too
much work for and from too many people

Comment 6

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to comment #5)
>                      LOST IN THE SEA WITH SEAMONKEY ?!
> (In reply to comment #4)
> > There's no way an extension installed in Thunderbird
> > *only* will affect SeaMonkey builds.
> 
> ... but the same extension in Thunderbird is working

And your point here is what, exactly?  Just because an XPI claims to work for
all 3 apps (and I say 'claims to work', because I was hard-pressed to find which
version of Mozilla Suite/SeaMonkey this extension was compatible with.  (But
that's not my responsibility.)
 
> 
> > http://imagezoom.yellowgorilla.net/faq/:
> > 
> > "...there is no built in way of uninstalling extensions in these applications, I
> > recommend that you use the Extension Uninstaller extension to uninstall
> > extensions from these applications".
> 
> Thanks for your hint. 
> It's necessary to install:
> - the extension manager
> - the extension uninstaller
> 
> After some googling, I found a working link to the uninstaller, and together
> with it I found the extension manager:
> http://mozmonkey.com/
> 
> But BOTH SERVICES, AT LEAST ONE LIKE THE EXTENSION MANAGER, SHOULD BE PART OF a
> Seamonkey STANDARD DISTRIBUTION!

Please don't shout, it's rude.

My guess is that once we move to /toolkit, we'll probably have better extension
management.

See bug 272429.

Also see http://wiki.mozilla.org/SeaMonkey:Project_Goals for more information
about where SeaMonkey is headed.

> 
> At now, Seamonkey is in part working as an user dungeon.
> Without change, you may get any error messages like mine, making and earning too
> much work for and from too many people

We're working to make SeaMonkey better, but we don't have infinite resources,
and we're doing what we can; patches welcome!

Comment 7

[Heinz Kohl]

(In reply to comment #6)
> > ... but the same extension in Thunderbird is working 
> And your point here is what, exactly? 

1) There should be a clear way to cope with products under development without
setting up side effects or setting up restrictions for allday work 
(despite their motivation product testers like me mostly using nightly builds
may in part have the need to work with 'failsafe' products, i.e. main line browsers)

2) invisible parts/addons cannot seen by the user in another way than as
integrative parts of the original program. If such tools are called and failing,
it's an error of the product, or the product is faked, and/or the installation
procedure is wrong. 

On this way informations about actual state as given by "Extension Manager" (or
a better solution by you) seems to be necessible also to send usable error messages.

Together with these informations I'd found a way to cope with the conflict for
myself and had never written this bug report.

One of main principles of engineers: the first responsive for an error is the
last one giving his sign (when Mozilla is integrating an addon without showing
it up in a clear way, Mozilla is the last; if anybody else is doing the same,
he's a faker).
In this sight Mozilla should have an interface for integration of addons with
information "look, I'm here!" and responsibility statement from the very
beginning, and an error message should try to show up the responsive. 
 
> .. and I say 'claims to work' ..
'claims to work' is exactly correct ;-)
- but when working, the tool is useful for me. 

> Please don't shout, it's rude.
Sorry, I'd the impression not to be heared otherwise 

> We're working to make SeaMonkey better, but we don't have infinite resources,
> and we're doing what we can; patches welcome!

I'm appreciating that.
I'm working on an own tool having very finite (perhaps too less) resources, and
on this way I've to spend some time making error reports (most of them essential
for my work).

Information about extra features and responsibilities could be valuable for
efficient use of restricted resources (some weeks ago while working on an SVG
error report, it took me about 2 hours just to find out, why the hell just the
browser without SVG ability was drawing the example correctly - an ancient and
forgotten SVG reader extension shown up only as directory entry, at no time on
the list of firefox extensions, and therefore not shown up ..).

Moreover, to have no automatically generated information about addons may set up
a too easy way for falsifiers.

Comment 8

[Heinz Kohl]

The "old" Seamonkey is quiet after removing imageZoom.

But the new Seamonkey Build 2005072109 is shouting in the base line because of
DOM inspector, which is not on the extension list shown by extension manager:

    <menuitem id="menu_inspector" label="&inspectorTaskCmd.label;"
____^

(This, I think, is just in the same manner than before and therefore no error,
even if I don't agree)

Comment 9

[Stephen Donner [:stephend] Not actively reading bugmail]

Heinz - that bug 301565, totally unrelated to any other patch in the world. 
Now, please, this 'bug' is dead, and has been for quite some time.