IceDogg wrote:After removing Toolkit is there something needed to be done to undo what it may have busted? Like I have several other extensions (add-ons) that still don't work even after removing toolkit. Here is my list: Add Bookmark here 2, QuickJava, Permit Cookies (hard one to live without), ExExceptions. I have 3 others that do work. ABP (which is the latest Dev build not release build), DOM Inspector, Download TimeStamp. Thanks
You could try renaming or deleting extensions.sqlite from your profile. Close Minefield 1st.
Thanks, but that made 2 of the 3 that were working stop, so I put the old one back. ABP is the one that continued to work.
CatThief wrote: I also have a local theme install script that I used in the past until current Moz apps would no longer respond to it. This sure is a lot of trouble for such a fundamental process.
Nope, that's OK, it only took me 5 minutes to make. Hope you, er, find it useful.
Oh no, Frank, that's not what I meant. I'm grateful to you for taking the time. What I meant was how the restructuring of the AOM is causing you, us all, to go through this sort of trouble just so our add-ons will install. It shouldn't be necessary. This thing landed way too soon.
Still passionate for Mozilla themes and extensions, just not actively developing them for public release anymore.
Could you do us all a favor and upload your pictures to a place like imageshack and then replace them here with thumbnails, please? It will mean much easier viewing for all of us. Thanks.
Ray
OS'es: 4 computers with Win10 Pro 64-bit; Current Firefox, Beta, Nightly, Chrome, Vivaldi
So with the old AOM you would be presented with a restart button in the install addons box after the addon had been installed, but now after you press install, the box just disappears and you have to manually go into the AOM, scroll down the list to the addon, and click the restart button. Is this a bug or is it intended to be this way? Is there a way to put the restart button back on the install addons box? IMO it's annoying to have to manually go to the AOM to restart.
Intel Core i3-2310M | NVIDIA GeForce GT 540M | 16GB G.SKILL DDR3 1333MHz PC3-10666 | Western Digital 750GB 5400RPM | Windows 7 SP1 x64
ajnauron wrote:@pal-moz yeah probably a theme issue. I use and will continue to use Strata40+Stratabuddy 0.6.1 until we get the new theme with glass.
I guess you could call it a "theme issue" as the new AOM uses totally custom instructions that require theme support... in other words, EVERY theme that wants to support 3.7 will have to muddle through this thing. As for me, I call it a design faux pas. It's the kind of design breakage that if an extension did it, it would be considered unacceptable.
Bug: 1. Open AOM 2. Hit CTRL+F to open findbar What we see: findbar stays above (as a layer) AOM, so bottom line (at the height of findbar's height) in AOM is covered by findbar. What was expected: findbar opens, and AOM gets resized like all the tabs do when you press CTRL+F on any web site.
Drug0y wrote:Bug: 1. Open AOM 2. Hit CTRL+F to open findbar What we see: findbar stays above (as a layer) AOM, so bottom line (at the height of findbar's height) in AOM is covered by findbar. What was expected: findbar opens, and AOM gets resized like all the tabs do when you press CTRL+F on any web site.
same behavior both on AOM and web page. not resized.
Drug0y wrote:Bug: 1. Open AOM 2. Hit CTRL+F to open findbar What we see: findbar stays above (as a layer) AOM, so bottom line (at the height of findbar's height) in AOM is covered by findbar. What was expected: findbar opens, and AOM gets resized like all the tabs do when you press CTRL+F on any web site.
same behavior both on AOM and web page. not resized.
I was thinking the same thing. What would change is if opening the find bar meant the page content only then exceeded the viewable area and thus the vertical scroll bar would appear. This action would create the impression of the page resizing.
Ray
OS'es: 4 computers with Win10 Pro 64-bit; Current Firefox, Beta, Nightly, Chrome, Vivaldi
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.