Benjamin Lutz wrote:
> First, the splash screen should be disable-able. Not that it isn't cool, but
> I just don't like splash screens. I think I'm not the only one.
I guess, you can (as I know the Mozilla folks - there are prefs for
everything :) ). try starting "Mozilla.exe -help" in a console window,
and dig through the default prefs (<instdir>/defaults/prefs) - they are
a huge base for tweaking info. Posts the results here if you find
something interesting.
> Although it's already been mentioned, I'll say it again - Beonex should
> store it's size, position and state (maximized or not) on exit. It's
> annoying to have to maximize every window before using it.
It does store its size for me (But I'm using Linux).
Storing max/min: Implemented, pending checkin. Contacted developer to
speed things up.
> Some people mentioned the address should be selected with a single click. I
> think this would be good too, and I'd also like to see a keyboard shortcut
> to it.
Ctrl-L
> It seems you have much confidence in Google's "I Feel Lucky" Button.
Not really. But more confidence than in Netscape Netcenter.
What is your opinion? Should the Internet Keywords feature be disabled
by default?
> Changing the default behaviour for entering search strings to displaying
> Google's search result page may provide the user with some less erratic
> results.
I don't understand.
> I've grown ot love this feature of IE, the sortability of the Favorites
> (That you can drag and drop the favorites into any order instead of having
> to have them sorted by name). Any chance we'll see this in Beonex?
worksforme.
> You could write a guide for webmasters how to convert their sites
<http://www.mozilla.org/docs/web-developer/>. More to come. Help welcome.
> if you
> display a page you reached via a post method, the source viewer displays the
> wrong page - it displays the page you would have received if you typed in
> the address of it directly, ie it drops the form data. I consider this an
> upright bug.
Yes, bad bug, known. Architectural problem, because this is a new type
of cache. (You can't use the memcache, because it won't store posts, I
think, and page athors can also prevent normal caching. You can't use
the source of the shown page, because that might be altered via JS.)
Will probably be fixed for 1.0.
> Have a lot of fun, Benjamin Lutz
Thanks!
