286169 - If you have the weather plug-in and then install the spoofstick plug-in the spoofstick plug-in will move.

Status: RESOLVED INVALID

(Firefox :: Toolbars and Customization, defect)

Description

[stop6667]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

When you follow all the steps specified, the Weather plug-in and the Spoofstick
plug-in switch places for some reason. This is not a major bug, but it is easier
on my eyes if I can easily glance at the Spoofstick text while reading down the
page then looking over to the right and then back.  

Reproducible: Always

Steps to Reproduce:
1. Download and install the weather toolbar plug-in. Put it to the right side of
the bookmarks toolbar.
2. Download and install the spoofstick toolbar plug-in. Put it in the middle of
the bookmarks toolbar.
3. Exit and go back into FireFox.

Actual Results:  
The Weather plug-in will be in the middle and the Spoofstick plug-in will be on
the right.

Expected Results:  
The Weather plug-in should stuck on the right and the spoofstick should stay in
the middle of the toolbar.

Here is my build configuration, if it is of any revelance. Other then that than
that since I am using the Firefox Defauly 2.0 theme.



Build platform
target
i686-pc-cygwin

Build tools
Compiler 	Version 	Compiler flags
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TC -nologo -W3 -nologo -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 	12.00.8804 	-TP -nologo -W3 -nologo -Gy -Fd$(PDBFILE)

Configure arguments
--disable-ldap --disable-mailnews
--enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth
--enable-crypto --disable-composer --enable-single-profile
--disable-profilesharing --enable-optimize --disable-debug --disable-tests
--enable-static --disable-shared --enable-official-branding

Comment 1

[Ali Ebrahim]

Sorry, we don't support issues with plugin/extension conflicts. You'll have to
contact the respective vendors.