Problem with Customization of Searchbar Autosizer

Bug #1249912 reported by sfcrj1234
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Searchbar Autosizer
Fix Released
Medium
Unassigned

Bug Description

Firefox 12, no assistant, no way to customize. Can someone please just let me know if I'm missing something, or does this not work with Firefox 12? I would like to use this extension; it was just what I was looking for. The extension is installed and working, but I cannot figure out how to choose the modes or customize it in any way or bring up the "assistant" that is supposed to be available (tried both 1.5.7 and 2.0 in Firefox 12, Windows 7 64-bit).

Revision history for this message
sfcrj1234 (sfcrj1234) wrote :
Revision history for this message
anonymous (anonymous-u) wrote :

Thanks, can you install the attached version and perform the following.

 - Navigate to `about:config` and:
    - set `browser.dom.window.dump.enabled` to `true`.
    - set `extensions.autosizer.debug` to `true`.
 - Restart Firefox from the command line and navigate to `chrome://autosizer/content/prefs.xul` in a new tab then click on the "Assistant" button.

Please post both the command line output and describe what happens, thanks.

Revision history for this message
sfcrj1234 (sfcrj1234) wrote :

I followed the above instructions exactly, and your extension seems to be working properly in my Firefox now. I have attached screenshots showing how it works.
Screenshot 1 shows what comes up when I navigate to the stated location. Screenshot 2 shows what comes up when I click on the "Assistant" button. Screenshots 3 & 4 show the results after I finish going through the assistant. It seems to be working as intended.
Let me know if I need to do anything else. I really appreciate your help and prompt attention to this matter. This extension is great for me.
(I will post each screenshot in a separate reply since it appears I can have only one attachment per post.)

Revision history for this message
sfcrj1234 (sfcrj1234) wrote :

Screenshot 1

Revision history for this message
sfcrj1234 (sfcrj1234) wrote :

Screenshot 2

Revision history for this message
sfcrj1234 (sfcrj1234) wrote :

Screenshot 3

Revision history for this message
sfcrj1234 (sfcrj1234) wrote :

Screenshot 4

Revision history for this message
Kevin Cox (kevincox) wrote :

That's odd, Oh well. Enjoy!

- **status**: open --> non-issue

Revision history for this message
kingn0thing (kingn0thing) wrote :

The same issue here with SBA 2.0.3; tried with autosizer-2.0.0-beta.xpi to no avail.
In both versions, manually launching chrome://autosizer/content/prefs.xul works and the wizard appears.
Here's an excerpt from the console (only the errors):

~~~~~~
07:28:13
Error: document.getElementById("addBtn2Toolbar") is null
Source File: chrome://autosizer/content/prefs.js
Line: 27
~~~~~~
~~~~~~
07:28:16
Error: w is null
Source File: chrome://autosizer/content/wizard.js
Line: 18
~~~~~~
~~~~~~
07:28:16
Error: asw is undefined
Source File: chrome://global/content/bindings/wizard.xml
Line: 413
~~~~~~
~~~~~~
07:28:16
Error: asw is undefined
Source File: chrome://autosizer/content/wizard.xul
Line: 1
~~~~~~

Revision history for this message
Kevin Cox (kevincox) wrote :

> The same issue here with SBA 2.0.3; tried with autosizer-2.0.0-beta.xpi to no avail. In both versions, manually launching chrome://autosizer/content/prefs.xul works and the wizard appears.

Are you sure you were using 2.0.3? That version had those lines removed from `chrome://autosizer/content/prefs.xul`.

Please try the attached version and try again. Thanks.

Revision history for this message
Kevin Cox (kevincox) wrote :

- **status**: non-issue --> open
- **milestone**: 2.0.0 --> future

Revision history for this message
kingn0thing (kingn0thing) wrote :

My bad: I should have stated that the excerpt from the log was from autosizer-2.0.0-beta.xpi attached above.

With SBA 2.0.3 no error in the console; I only mentioned it because the Assistant doesn't appear in this version as well (safe when manually launching chrome://autosizer/content/prefs.xul and clicking on its button).

Revision history for this message
Kevin Cox (kevincox) wrote :

Can you follow the steps I gave in the first comment with the attached version and tell me what happens? I can not reproduce your issue.

Revision history for this message
Kevin Cox (kevincox) wrote :

I can reproduce this with 12.0 on windows 7 64-bit.

- **status**: open --> accepted

Revision history for this message
Kevin Cox (kevincox) wrote :

And 13.0.

Revision history for this message
Kevin Cox (kevincox) wrote :

- **assigned_to**: Kevin Cox

Revision history for this message
Kevin Cox (kevincox) wrote :

Okay, I found the problem, on Windows the prefrences window is considered the last active window where as on Linux (and macs?) the browser window is considered the last active window.

I think I will just change it to launch from the browser as I think that that is nicer anyway, no funky always on top pop-up window that always gets in the way madness.

Revision history for this message
Kevin Cox (kevincox) wrote :

- **status**: accepted --> fixed

Revision history for this message
Kevin Cox (kevincox) wrote :

Fixed in commit cf7d21d8ca2d733c87a40aad50c690f2aba8f860.

I changed up the wizard a bit. The only thing is that it looks a little funny on large displays. A bit of restyling could fix that though. Or I even fixed it so that it could be a popup if you wanted. (Or if you had a large display) Maybe we will auto-detect that. But that is a different issue.

This will be seen in 2.0.5 which is in the repo and downloads section and I will upload it to AMO in a couple seconds.

Revision history for this message
kingn0thing (kingn0thing) wrote :

2.0.5:

1. the user shouldn't be able to open several Wizard dialogs.
2. the red brackets around the Searchbar stay there after exiting the Wizard if you cancel or close it while on the "wiz.norMinWidth" page (they're still there even after disabling SBA, which would imply that it doesn't fully unregister some stuff).
You can have an infinite number of brackets by repeating the steps.
3. if you try to increase the min/max width of the Searchbar to over 1108 pixels (tested with a screen resolution of 1280x1024), you'll notice that buttons and images in the panel as well as in the Add-on Bar will go off screen).
4. There's a conflict with [Dictionary Switcher](https://addons.mozilla.org/firefox/addon/dictionary-switcher):
The first time we try to open the Wizard, only the buttons ("Back", "Finish", and "Cancel") are visible and it seems that the page opens up on the last configuration panel (the "Finish" button appears instead of "Next"). Closing and relaunching the Wizard resolves the issue.

Revision history for this message
Kevin Cox (kevincox) wrote :

I have opened different bugs for these issues.

1+2: [#22]

3: This appears to be intended behavior. If you wish to explain better please open another bug.

4: [#23]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.