Searchbar Autosizer Firefox Add-on / Tickets / #8 Problem with Customization of Searchbar Autosizer

Anonymous - 2012-06-21

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.

Last edit: Kevin Cox 2012-06-21

autosizer-2.0.0-beta.xpi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Randy J. - 2012-06-22
  
  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.)
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Randy J. - 2012-06-22

Screenshot 1

Screenshot 1.jpg

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Randy J. - 2012-06-22

Screenshot 2

Screenshot 2.jpg

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Randy J. - 2012-06-22

Screenshot 3

Screenshot 3.jpg

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Randy J. - 2012-06-22

Screenshot 4

Screenshot 4.jpg

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-06-25

That's odd, Oh well. Enjoy!

status: open --> non-issue

Last edit: Kevin Cox 2012-06-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

King Nothing - 2012-06-28

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
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kevin Cox - 2012-06-28
  
  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.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - King Nothing - 2012-06-28
    
    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).
    
    Last edit: King Nothing 2012-06-28
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Kevin Cox - 2012-06-29
      
      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.
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-06-28

status: non-issue --> open

milestone: 2.0.0 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-06-29

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

status: open --> accepted
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kevin Cox - 2012-06-29
  
  And 13.0.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-07-02

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-07-02

assigned_to: Kevin Cox
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-07-03

status: accepted --> fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Kevin Cox - 2012-07-03

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.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

King Nothing - 2012-07-03

2.0.5:

the user shouldn't be able to open several Wizard dialogs.

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.

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).

There's a conflict with 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.

Last edit: King Nothing 2012-07-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kevin Cox - 2012-10-12
  
  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]
  
  Related
  
  Tickets: ~~#22~~
  Tickets: #23
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Problem with Customization of Searchbar Autosizer

Milestone

Searches

Help

#8 Problem with Customization of Searchbar Autosizer

Discussion

Related