Re: Changes in galeon 1.3 over mozilla compiled with gtk2

Hi,

> *  The "Clear location" toolbar widgit/button is gone. 

http://bugzilla.gnome.org/show_bug.cgi?id=110350


> *  The "Find entry" toolbar widgit/button is also gone, another small but
>    one of my favorite galeon convenience features.  Several more mouse
>    clicks in different places are now required to find text in a page.

Doesn't mozilla's type-ahead-find (or whatever it is called) solve this
problem? Just press '/' and start searching when the focus is in the web
page.

If that doesn't solve your needs, you probably want to file an
enhancement request in bugzilla.

> *  Text entry fields in smart bookmarks aren't persistent and the fields 
>    are cleared on each use cycle.  I much preferred them to retain text so
>    that, for instance, I could use the google smart bookmark, to perform a
>    series of related look-ups, even if I were browsing a referenced page
>    rather than at a google results page.

You could use the smart bookmark history, IIRC we couldn't think of a
decent use-case for preserving the text, although tko may remember why
exactly it didn't get back in.

> *  I note that favicon.ico reading is strange.  I guess there's no
>    'standard' on this, however I believe SOP is for a browser which supports
>    them to request favicon.ico in the document root even if a URL is a 
>    request for a page in a subdirectory.  galeon 1.2 worked as expected
>    in this regard, however galeon 1.3 won't fetch favicon.ico from the 
>    document root if the URL is a request for a page in a subdirectory.
>    Galeon 1.3 (or possibly it's in the gekko rendering engine) also 
>    appears considerably lest robust in handling the various favicon.ico 
>    multiple image formats which galeon 1.2 handled OK.

Galeon will use favicons that are setup using the <link rel=...> stuff
that sites such as http://www.gnomedesktop.com/ uses. If you can find a
favicon image that isn't used properly, then you need to file a bug.

We are thinking of having the ability to download the /favicon.ico file
for bookmarked sites, but not for general browsing.

> In general, I've seen a lot of applications which seem to have lost lots of
> bits and pieces of functionality in the move from gtk1.2 to gtk2.  Is this
> because of the need for radical rewriting of code in the apps, because these
> features are difficult to support in gtk2, or what?  Is this situation
> expected to improve so that we can expect refinements lost in the migration
> to be restored at some point?

Galeon 1.3 is an almost complete re-write of galeon 1.2, so features are
added, rather than there being a decision to remove them. Most
applications try and follow the HIG, which likes applications to be
simple with sensible defaults.

Crispin




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php