Dan.

"C:Program Filesmozilla.orgMozilla" and user "profiles" are enabled.

I had the same... (menuitem id="view_gg_menuitem") bug after I installed 0.4.6.

{a few hours later...}

Then I unloaded the system tray icon, using the exit option. Lastly, I used the icon on the desktop to start mozilla. I had been using the tray icon before.

Then the new toolbar was up!

So I checked the shortcut and startup folder was set to the mozilla program folder properly. It was worth the fuss.

John

0.4.6 gives menuitem id="view_gg_menuitem"

if anyone wants a copy, email me:

awmorp@almastud.com.au

0.4.6 is a great improvement over the previous version!

well done!!

0.4.6 gave me the menuitem id="view_gg_menuitem" error. (I'm using Windows XP Pro). I installed 0.4.5 on top of it and that worked. Then today, I reinstalled 0.4.6 (without uninstalling 0.4.5) and now it works too!

Thanks again for all your work.

0.4.6 gave me the menuitem id="view_gg_menuitem" error. (I'm using Windows XP Pro). I installed 0.4.5 on top of it and that worked. Then today, I reinstalled 0.4.6 (without uninstalling 0.4.5) and now it works too!

Thanks again for all your work.

save a bit of space, and accidentally dropping down the box is occasionally annoying...

The googlebar will not show up. If I install 0.4.6 I get the XUL(?) error that everyone talks about, but the line that is supposed to be missing "locale,install,url,resource:/chrome/googlebar/locale/en-US/googlebar" is there. I've tried it with an end "/" and without. Don't know about the square char (I'm assuming its a control code that won't display).

I uninstalled the googlebar, and had more than 4 references in the chrome.rdf file. I swear that I've gotten this thing working before, but I think that was using Pheonix 0.3 perhaps.

Is there a problem with 0.4 and XP in regards to the googlebar? I'd love to get it back...

One more note, there's mention of a "Hide/Unhide googlebar" under view. I haven't seen that. Also, there is supposed to be a drop down under advanced in the Tools->Prefs menu, and there hasn't been.

Help!

Moro

I'm about to try an older version

dl
http://www.latznewmedia.de

jclark

mhhack

One little bug/feature: when I drag a word or phrase to the Google toolbar it replaces the text currently there, On Googlebar it gets added. By design? or am I missing a setting?

0. Close your browser. :)

1. Create a locales/en-US directory in your chrome directory, and put there the content of the chrome/googlebar/locale/en-us/googlebar directory.

ie.
From: chrome/googlebar/locale/en-us/googlebar/*
to: chrome/locales/en-US/
(note: check the case!)

2. Go to your profiles directory and DELETE the file XUL.mfl.
ie.
MozillaProfilesdefault6orygm9u.sltXUL.mfl

Do not care about it: it will be recreated the next start.

3. Restart your browser. Voilà! Everythig works fine now!! Wow! :)

Enjoy googlebar!

Nova

Selecting any of the search buttons yields no reponse.

On a good note tho, the text window that had the height problem is now fixed when using the Pinball theme on PX 2-1-03 build!!

1. Inconsistency: The textbox used in the Toolbar is very limited. It is much uglier than the address bar textbox, and does not support a standard context menu. The feature of being able to copy and paste using the mouse only - without having to touch the keyboard - is important. And textboxes should look and behave the same.

2. The only way to get a word at the right of the toolbar is to manually type it in. pasting it into the textbox does not do anything.

3. Trying to use the page search function the same way as I do it with the Google toolbar in IE does not seem to work. It will tell me when a word can not be found (sometimes it can not find a word in a hyperlink), but I expected the word to be selected, and the window to scroll so that it is visible.

4. The amount of icons is confusing. I would be using less than half. A text explanation near the important icons is also important. People who learned reading and writing using an alphabet find it difficult to have to learn to read Pictograms. I counted on the Google toolbar SEVEN icons WITH an english title near each. I count ELEVEN icons here with no explanation. Some of them (like the TV with the antenna on top) bearing no relationship to their function, and some just funny (like the amoeba and her daughter).

Again, thank you for the good work. Mozilla is already better than IE in some respects. The tide may turn soon.

The googlebar is taller with no button labels than it is with them.
showing button labels makes the highlight, and up directory buttons disappear

the "googlebar" picture button (the first one) is excessively wide.

I have some other issues with mozilla's toolbars in general which are not unique to googlebar, but the googlebar rubs salt in the wounds - you can't move them left to right, there is excessive empty space in the toolbars (easily 40% of my 4 toolbars is empty space), as additional toolbars always extend the area vertically).

also I am suspecting hte reason that googlebar is so bizarrely tall is because of the size of the up directory button - it has a different 3 effect on mouseover than the rest of them, that takes up the entire space from top to bottom (and an unusual amount of space to the right, as well)

Wishlist (some repeats):

1.Toggle it on|off with a button and/or hotkey.
2.Shorter bar, narrower buttons.
3.Fix the focus issue with tabs.
4.Default to replacing not adding items to the text box.
5.Make it share other Mozilla/Phoenix bar(s), if that's possible.
6.Make search terms longer than the bar space available wrap onto a flyout menu (like IE), if that's possible.
7.More buttons to match the menu (for Images, News) and add Labs, Froogle.
8.Have a button available for every item, not only available within the Special, Computer, Info dropdowns.
9.Copy Google's 'fix broken URLs' trick.
10.(Off the wall:) Fake a cookie, so all searches obey user-set preferences (number of results, language, filter etc), yet without needing to eat Google's everlasting, GUID'd, cookie.

1.By replacing the button (in your equivalent of) ...
~phoenixchromegooglebarcontentskinlogo-GOOGLE-2.png
... with something smaller, it becomes just a standard-width button instead of the word-length button.
You can use another button, renamed from the same folder, e.g. ...
~skinSEARCH-norm.png
Or, I use the Google favicon ...
http://www.google.com/favicon.ico
... renamed as logo-GOOGLE-2.png. Once you click the button, the menu flows out to the normal width, so functionality is unimpaired.

2.I find the text search box defaults to too narrow. You can drag it wider of course, but that's a pain for every restart. By editing (your copy of) this file in Notepad ...
~phoenixchromegooglebarcontentgooglebarOverlay.xul
... you can change that. At about line 225 you get this section ...

<hbox id="search-textbox" flex="1" persist="collapsed"
collapsed="false">
<menulist class="googlebarSearchText"
id="googlebarCriteria"
editable="true"
onkeypress="googlebarClearTerms(); googlebarAddTerm
(this.value); if( event.keyCode == 13 ) { googlebarSearch
(event); }"
onFocus="this.select()"
flex="1"
context="DUMMY"
minwidth="100"
width="160">
<menupopup>
</menupopup>
</menulist>
</hbox>

If you change these two lines of that to ...

minwidth="0"
width="250">

... it starts out wider. Adjust the 'width' figure to suit. (Setting the minimum width to '0' lets you squash it right down, for those odd occasions when you might appreciate the maximum room for the search terms highlighted to the right).

While you're there, you can also lose the separators between the buttons to gain a few more pixels, if you like. Delete either|both the lines saying ...

<vbox id="separator"/>

... at about lines 291 and 413.

I hope these might help someone :)

Sorry, I wish I be more helpful than just wishing.

in googlebarOverlay.xul, from version 0.4.6 on line 423:

<toolbarbutton type="menu-button" class="button-all"
id="up-dir-button"

take out the 'type="menu-button" ' to fix the size of the up-directory button. i entered a bugzilla thingie for this. i dont THINK this breaks anything.

I now see that some of my wishlist items are already there (working?) for Mozilla, but not working for Phoenix. Ah well.

1) I'd like to be able to rearrange the buttons a bit. Namely, I want to move the "image search" button off the dropdown and directly on to the bar.
2) The main Googlebar menu has a link to Advanced Google Search... it'd be nice if Advanced Groups and Advanced Image search items were also added (yes, I know these aren't on the real Googlebar, but so what). Again, it would also be nice to be able to move stuff back and forth from dropdowns to the bar itself.
3) The bar's too high. I see somebody posted how to fix it, and I'm about to do it, but it seems like the default should be shorter. It should match the height of the Personal Toolbar, not the Navigation Toolbar (IMHO).

...As for the height of the toolbar, this is NOT a feature bug; it's a rendering one in the modern theme. I added this comment to the related bug that was filed, and here it is: if you use the googlebar in the "classic" theme in mozilla, you'll see that the Up-directory button is intended to work like diggler ( http://diggler.mozdev.org ), and give you a menu next to the button to go up further levels. It works great but renders as just a huge button in modern (classic and many other themes are ok)- in modern, the 1px raised border all around the up button can be clicked on to give the menu. Rather than chop it out of the experimental release, we'd prefer to find a way to fix the way it renders... if you know the way to fix it, visit bug 2899 and let us know; otherwise it may be a while.

One more thing, though. I'm still getting the "xul error" with the latest build on my FreeBSD box. It works fine on my Windows machines. Should I add a note to the bug report, or try to reopen it? I'd be happy to give any debugging info that's required...

Some main points.
If you don't have the "world read" permissions on all the googlebar files... dont forget the
http://locales/en/US/googlebar/* excuse the http prefix, but i want the darn slashes! How dare they steal the slash characters.

Try creating a new "test" mozilla profile, (using a name you'd never really ever want to use), and login to mozilla as that user. If that don't work, leave a note on the help and faq page.

Milly: form preview! Now that's a good one.
Lets see if the http prefix aint too ugly.
It stole my slashes way top for #2, and you say you tried dashes and it stole them too? Well a show/hide search terms button is in the "pre" XPI-rimental.xpi
if ya feel brave. You can find it under bug 3223 as zip download, or xpinstall. It's pre experimental, so drag a copy of the chrome folder to somewhere safe before testdriving.

Yes the context menu for the document area were stuck "on" in that test sample. Attachment 837 should be a single click xpi install. Since you did already, please install this one. The context menu option in the options panel is hooked in, though once you change your option, it doesn't take effect until you open a new tab or window. Everyone else should hold off a while. Andy Ed and AndyB had problems I couldn't reproduce in my 98 & ME machines. But it won't be long. If anyone insists on ignoring this warning, back up your chrome and user preferences at a minimum.

Item 3:
Now, it takes a doubleclick to highlight everything there. And if everything in there is already highlighted, you can doubleclick again on a particular word, to highlight just that word.
While I'm there...
The right click menu now works! (In mozilla 1.3b) The missing cut, copy, paste, popup menu in the search criteria box, you called it text search box in #45,

Item 6:
The context menu for the document area has a googlebar context menu now, that will say "Googlebar", that pops up another menu with the pageinfo options. This, instead of adding 5 or 6 items to the standard context menu, is a better way, no? AndyB's idea to Colin Hill's patch. Thank you Colin. It adds a nice touch, that will surely get more work in the near future. See bug 2471
(Then maybe some of the lesser used buttons can be placed on the context menu and off the toolbar.) Are you saying the document area contextmenu doesn't have a "Googlebar Items" in your phoenix? Your wishlist has some good ideas, though some aren't really easy, they could be considered "the ideal case". Just trying to get it to "no reasonable complaints" first. :) And sadly, the ctrl-f8 nor the ctrl-f12 did not work for me on the mid february phoenix nightly I grabbed one sunday. So I'm kinda waiting to see what happens with both Andy Ed, and AndyB, before going forward.

Thanks for your good ideas!

-John Woods

You may wish to provide a link from your website to the Education on the Internet newsletter or the Web Directory. As we have, according to the Alltheweb Search Engine, over 134,370 websites linked to the Spartacus Educational website, (for further details see http://www.marketleap.com) this should increase your search-engine ranking. As a result, by providing a link to us you will improve your ranking in second-generation search engines such as Google.

Please feel free to send me a 200 word description of new aspects of your website when they become available.

John Simkin

spartacus@pavilion.co.uk

Eventually, ideally, to answer your (lesser used buttons) question, it would be nice if any item could be user-configurable to be either on the bar and/or context menu. And for the context menu to be multiple direct entries or cascaded (like now), by user-configuration. But certainly cascaded is better than multiple direct entries, if/while only one method is possible.

BUT ... though I don't have the Andys' text entry issue, I have another. Pressing any of the search buttons, or clicking any of the document area context menu searches, pops up an error message saying "Alert: Shouldn't have gotten here but, kindly leave us a note on googlebar". So no actual searches work. All the stuff re 'push back', highlighting, adding selected words works fine. Maybe 837 will sort that.

Item 3: yep, double-clicking and re-clicking now works as you say.

I don't get a context menu in the search criteria box, under any circumstances (with/without selection, empty or populated, nada).

I do appreciate the need to get the bugs and most requested features sorted first, and the difficulty in implementing some of the things I glibly wish for. I hope most for the on/off toggle working for Phoenix ...

More when I get a chance to try 837. Should I post there or here? Over there seemed to be more for you code mavens.

But the settings for doc area context menu are now stuck on. (Sorry, I didn't try turning them off last time). Opening a new tab or restarting Phoenix makes no difference. Fine with me (I want it!), but I understand you want to fix that - so I'll try any changes if you like.

Still no sign of a context menu in the search criteria box, under any circumstances.

And I don't get the 'leave a note on googlebar' msg, but just did a image search (after setting it up in the panel) with shift-enter. You may have to delete the 'xul.mfl' file after installing again, then shutting phoenix down and restarting.

Mucho experimentation later, it's clear that Phoenix (presumably Mozilla too) handles over-installing components terribly. Nothing short of a scorched earth install guarantees no residual funkiness. So, clean install of Milestone 0.5 (tried the latest Nightly, but it crashed on start, every time), then your first test (id=824, I presume you meant), and most everything works fine. Text entry, buttons, sticky prefs, push-back, all okay. In the search criteria box, the first double-click selects one word, second double-click selects everything.

But ... the setGoogleContextMenu(); change in googlebarOverlay.js didn't help (even after deleting xul.mfi and restarting) - the doc-contextmenu setting appears to change (i.e. the check-box stays checked or unchecked), but the menu is always there and working, no matter what. Better than the opposite.

And there is still no sign of a context menu in the search criteria box.

I've finally twigged what you meant by a lot of menu work with a dropdown. You could make the dropdown sticky, despite word button presses, until specifically clicked off again at the >>. But even without that, if you combine push-back until fully extended, then dropdown, you've got the best of both systems. Easy for me to say ...

The contextmenu option is working as are the keyboard modifiers, phoenix issue. (addressed in my response)

The criteria box right click (clipboard) popup - also phoenix issue as well. Mozzila 1.3b shows us that much.
No wonder we couln't fix it. :)

I would really like for an option to choose what google site you search when you hit enter! I use Groups 99% of the time. I would love to type in search box, hit enter, and have it search groups (as opposed to, google web)

If not, then it's in a newer pre-XPI version. Back up your Chrome folder (at least, even better to copy elsewhere the whole Mozilla or Phoenix folders under Programs and User Settings). Then go here ...
http://mozdev.org/bugs/show_bug.cgi?id=3223
And install the first attachment here ...
http://mozdev.org/bugs/showattachment.cgi?attach_id=824
Take care: read the page for possible bugs, it's even more experimental. Works great here though, and does what you want.

I would really like for an option to choose what google site you search when you hit enter! I use Groups 99% of the time. I would love to type in search box, hit enter, and have it search groups (as opposed to, google web)

I would really like for an option to choose what google site you search when you hit enter! I use Groups 99% of the time. I would love to type in search box, hit enter, and have it search groups (as opposed to, google web)

But there's a conflict (I guess) with the LittlePhoenix theme...
http://texturizer.net/phoenix/themes.html#LittlePhoenix

It seems to clobber the Back and Forward buttons. This is how it looked with the previous (824) version,. See, immediately to the left of the address box, the Back and Forward buttons and their down-menu arrows are close-coupled :-
http://www.imilly.com/files/orig.jpg

But here they are weirdly spread out. This with 0.4.6.31 over-installed:-
http://www.imilly.com/files/litpx.jpg

And this with a completely clean install of Phoenix 0.5 Milestone plus 0.4.6.31 plus LittlePhoenix :-
http://www.imilly.com/files/litpxclean.jpg

The same buttons with the default Px theme are fine, and I have't tried other themes. I have no idea what's going on.

http://mozdev.org/bugs/showattachment.cgi?attach_id=899

http://mozdev.org/bugs/showattachment.cgi?attach_id=900

The menu popup was missing for when using the modern theme. But classic now has a small spacing problem in the same spot. But if it crosses lines to the back forward buttons in some other other themes, it will need some more work. But we knew that. I'll make a classic version .31 attachment here for the interim, for the classic users.
Rightclick-> save as-> default.css in your
chrome/googlebar/content/skins folder, and restart.

http://mozdev.org/bugs/showattachment.cgi?attach_id=901
I'll be using it myself!

901 is the older file default.css, to restore classic and others to their former glory after installing 0.4.6.31 and it's bug fixes.
Though your "save link target as" dialog will say showattachment.cgi.html, replace the name offered with default.css and then navigate to your
mozilla.org/mozilla/chrome/googlebar/content/skin
folder and save the attachment. Again this as default.css

Thanks

If this is a bug in the google bar, let me know and I will post it accordingly. At that time, I could include a screen shot.

Thanks.

If you do select cancel, then you'll be given the choice to install to the browser's program folder, _if_ you have write access to that folder or it's subfolders. Otherwise you'll get a msg telling you that you don't have write access, and you should install to your home profile folder instead.

If your browser doesn't meet the late build criteria, you should then just get a prompt(after a successful write access test for the permissions to do so) to install to the browser installation folder.

This permits you to install to restrictive OS types, without upsetting the browser for everyone else. I have installed it to my linux test machine, a redhat 7.3, as an ordinary user. No other users are affected. Root's browser has no googlebar, and has zero knowledge about the one installed to the user's profile, and doesn't die because it can't find a file in some user's profile.

It went in late last night, and two more updates this morning. If you have any problems, I've made a bug report already:
http://mozdev.org/bugs/show_bug.cgi?id=3415
just fill in the needed info.

Worse, Mozilla itself won't uninstall, nor will the 1.3 install run to overlay what I've got.

Any ideas on cleaning up ? Almost forgot - this is in Win2Ksp3.

Anyhow, Mozilla won't launch now, so I couldn't load an XPI if I wanted to. And the Mozilla Uninstall just flashes up a box but doesn't remove it, and a fresh Mozilla Install package won't run either, probably colliding with the existing one.

So I've dug myself in pretty deep and really need help that's beyond googlebar's purview.

And, the horror of a machine that adapts to things it thinks are mistakes! "Must sterilize, Must sterilize!!
You, are the creator Kirk" One of my favorites.

If I were in your shoes... Actually the mozilla folks stress 'not installing a new version into the same folder as a previous version.' Running the way you are now, well it may not last. Now you can probably install again to the 'default' location, and copy the mail to the fresh install mail folder.

And after all that, come back and grab the fixed XPI-rimental.xpi

wangtianyao@hotmail.com

then I will send the chinese version to you.

http://www.forobuscadores.com

http://www.forobuscadores.com

However..... it does not set the permissions of the chrome/googlebar files correctly (they are read only root ... the default root umask)
You need to

% chmod -R o+r /usr/lib/mozilla-1.3/chrome/googlebar
to allow non root users to use it. (otherwise mozilla hangs on startup)

Wangtianyao, we may have broken your chinese translation when we added some new things that also need translating, but a chinese translation would be great- sorry if it takes us a few days, but we'll try to talk more to you once we've got things settled down- sorry for the wait. I think that giving translators CVS access would be a good way to keep their work up to date, though, so I'll put in a good word with Andyed, who manages these things.

Buscadores, as far as how many languages we have right now, we've pretty much been keeping only the english one up to date; the release of our next version is the goal to keep things steady for a little while and allow people to translate without fear of too much being broken (older translations without the newer words included cause mozilla give an "I don't understand this so it's all broken" error in large red letters on the bottom of the screen).