Closed Bug 265234 Opened 21 years ago Closed 21 years ago

Updated extension - Bible Toolbar

Categories

(addons.mozilla.org Graveyard :: Administration, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jamison, Assigned: wolf)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 There is an updated version of the Bible Toolbar extension, it is now up to 1.5.3. The xpi is located at http://dupadee.net/bibletoolbar/bibletoolbarFF.xpi for Firefox 0.9+ (including 0.10.1) and http://dupadee.net/bibletoolbar/bibletoolbar.xpi for Mozilla and Firefox 0.8 Reproducible: Always Steps to Reproduce: 1. 2. 3.
Reassigning to a temporary destination pending assignment to a new editor. :-)
Assignee: psychoticwolf → firebot
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assigning the bugs to Update's newest editor, nosebleed. :-) Please be patient with him, as he's new, volunteering to help out and hopefully speed up the process of getting these added.
Assignee: firebot → nosebleed
Severity: normal → enhancement
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 Tested on 1.0PR winXP, installs/uninstalls and works fine.
Whiteboard: tested+
Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 Tested 1.0PR on Linux. Installs/Uninstalls fine. The toolbar was wider than the browser window, so the extension was unusable for me (couldn't get to the "go" button) but the browser was unharmed.
I have used this toolbar a little bit more on winXP, and sometimes after I've preformed a search keyboard input is disabled until I restart the browser.
(In reply to comment #5) > I have used this toolbar a little bit more on winXP, and sometimes after I've > preformed a search keyboard input is disabled until I restart the browser. Odd... I use this quite a bit on WinXP, and have many users who also use XP, and none of them have reported a problem like this. Do you have any other hints on how I could try to reproduce it? Thanks
(In reply to comment #4) > Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 > > Tested 1.0PR on Linux. Installs/Uninstalls fine. The toolbar was wider than the > browser window, so the extension was unusable for me (couldn't get to the "go" > button) but the browser was unharmed. Yep. Known problem. Anything less than 1024x768 gets cut off. I'm looking at shrinking this in a future version. In the meantime, simply hitting enter in one of the search fields will instantiate a search.
Hmm, I've got no idea what's going on with the keyboard eating... maybe it was just random because I can't see it anymore, though I did see it about 3 or 4 times in a row, restarting the browser between each time. But now it WFM.
re: comment #7 I find that I can't search using [enter] or "Go" until I've set some values in "Options". (I'm talking about Windows because I can't even see the options button on my linux box).
(In reply to comment #9) > re: comment #7 > > I find that I can't search using [enter] or "Go" until I've set some values in > "Options". (I'm talking about Windows because I can't even see the options > button on my linux box). Yep, known problem. Need to set options one time before the toolbar works. Still trying to figure out a way to deal with this.
Assignee: nosebleed → psychoticwolf
Thanks for testing, added to the site. :-)
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Whiteboard: tested+
Component: Update → Listings
Product: mozilla.org → Update
Version: other → unspecified
The evil bugspam monkeys have attacked again, updating the QA Contact for all Add-ons :: Add-ons bugs (renamed from Listings). Please ignore and go back to work at your cubicle.
QA Contact: mozilla.update → add-ons
Component: Add-ons → Administration
QA Contact: add-ons → administration
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.