K-Meleon

One helpful task for beta testers is to see if your favorite plugins work
with the new build. I just tested:

Adobe Acrobat Reader 5
Flash Player 6
Shockwave 8.5.1

and they all worked.  Let us know what works and doesn't for you.

Andrew

a better description of the macros changes here: http://www.script-source.net/km/MACROS.CFG

this plugin is pretty much virtually untested, other than quick confirmations by myself, so there is
sure to be bugs.  please let me know if you come across any strange behaviour (or if you throw
together a really cool macro :P)

-Rob


----- Original Message -----
From: "Jeff Doozan" <jeff@...>
To: <Kmeleon-dev@...>
Sent: Tuesday, March 26, 2002 12:46 AM
Subject: [Kmeleon-dev] New Build


> Hi everyone,
>
> Here's a new build.  It's based on the Mozilla .9.9 release.  There
> are still a few things lacking (file downloading is broken, PSM, and
> a few more that I can't remember but I'm sure you'll notice) but it's
> otherwise quite nice.  In fact, there are a few nice things to
> distract you from the problems:
>
> 1) Rob Johnson has greatly improved the macros plugin.  Have a look
> at the new macros.cfg file for his notes on that, and be sure to
> thank him.
>
> 2) Via my other project, StrokeIt, we now have real mouse gesture
> support.  You'll need to download a special build of that here:
> http://www.tcbnetworks.com/cgi-bin/download.pl?file=StrokeIt9b9-pre-
> kmeleon.exe
> but I think you'll be pretty happy with it.  I've only preconfigured
> it for two specific gestures:
>
>  - "Down" (move mouse cursor over a link, press the right mouse
> button, move the mouse down, release right button), to Open link in
> new window)
>  - "Down \" (same as above, but move the mouse diagonally down-right)
> , to Open a link in background
>
> Additionally, using the StrokeIt command editor, you can add more
> gesture bindings to execute any command that kmeleon can support (eg,
> draw an F to open the current frame in a new window, E to execute a
> macro that will email the current page to a friend, etc)
>
> We also have frames support, print preview, and all that...but I
> think that was in the last beta, as well.
>
> Here's the link: http://kmeleon.sf.net/files/beta/kmeleon065.exe
>
> Enjoy :)
>
> -- Jeff
>
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

!<jeff@...> Tue, 26 Mar 2002 01:46:39 -0500:

> Here's a new build.  It's based on the Mozilla .9.9 release.  There 
> are still a few things lacking (file downloading is broken, PSM, and 
> a few more that I can't remember but I'm sure you'll notice) but it's 
> otherwise quite nice.  In fact, there are a few nice things to 
> distract you from the problems:

> 1) Rob Johnson has greatly improved the macros plugin.  Have a look 
> at the new macros.cfg file for his notes on that, and be sure to 
> thank him.

how could i not download the beta in the face of all that?

seems better in almost every way (if you don't mind combing
through the temp folder for your downloaded files... ;) and
the macro plugin is working well so far... is it going to
be a major ordeal to re-implement the set/togglepref
macros?

> is it going to be a major ordeal to re-implement the set/togglepref
> macros?

Even before I started playing with the macros plugin I've had problems getting set/togglepref to
work as I would expect them to.  I was planning on investigating it a bit but I've got deadlines up
the bunghole at the moment and free time is sparse, not to mention i don't have a mozilla build
environment set up. If I get some free time maybe i'll look into it, or maybe Jeff can look into it.
I also want to implement some kind of program flow control structure and a looping mechanism, maybe
I should quit sleeping :)

-Rob

!<dillybar1@...> Thu, 28 Mar 2002 20:58:17 -0600:

> I also want to implement some kind of program flow
> control structure and a looping mechanism, maybe I should
> quit sleeping :)

well, worrying about fancy stuff now is probably putting
the cart before the horse, i suppose. :)

in addition to the *pref() macros, the exec() macros also
seem to be not working for me... is this a known
limitation?

-- 
   po

hmm, i dont remember having any problems with exec.  
are you putting the command in quotes? exec("C:\path\to\something.exe");

ill play with it a bit tomorrow.

-Rob


----- Original Message ----- 
From: <po+k_list@...>
To: <kmeleon-dev-admin@...>; "Rob" <dillybar1@...>
Cc: <Kmeleon-dev@...>
Sent: Thursday, March 28, 2002 9:41 PM
Subject: Re: [Kmeleon-dev] New Build


> 
> !<dillybar1@...> Thu, 28 Mar 2002 20:58:17 -0600:
> 
> > I also want to implement some kind of program flow
> > control structure and a looping mechanism, maybe I should
> > quit sleeping :)
> 
> well, worrying about fancy stuff now is probably putting
> the cart before the horse, i suppose. :)
> 
> in addition to the *pref() macros, the exec() macros also
> seem to be not working for me... is this a known
> limitation?
> 
> -- 
>    po
>

after busting out File Moniter to see exactly what was
going on, it became apparent that the "\" characters in the
path were being parsed out, in spite of the path being in
quotes... after escaping the backslashes, it worked fine.

i don't remember that being required before, i didn't use
that many exec() macros...


!<dillybar1@...> Thu, 28 Mar 2002 22:02:39 -0600:

> hmm, i dont remember having any problems with exec.  
> are you putting the command in quotes? exec("C:\path\to\something.exe");

> ill play with it a bit tomorrow.

oh, yeah forgot about that. i had intended to support special characters like tabs \t and newlines
\n in strings, so the backslashes need to be escaped \\

-Rob

----- Original Message -----
From: <po+k_list@...>
To: "Rob" <dillybar1@...>
Cc: <Kmeleon-dev@...>
Sent: Thursday, March 28, 2002 10:48 PM
Subject: Re: [Kmeleon-dev] New Build


> after busting out File Moniter to see exactly what was
> going on, it became apparent that the "\" characters in the
> path were being parsed out, in spite of the path being in
> quotes... after escaping the backslashes, it worked fine.
>
> i don't remember that being required before, i didn't use
> that many exec() macros...
>
>
> !<dillybar1@...> Thu, 28 Mar 2002 22:02:39 -0600:
>
> > hmm, i dont remember having any problems with exec.
> > are you putting the command in quotes? exec("C:\path\to\something.exe");
>
> > ill play with it a bit tomorrow.
>

Here's the new build.

http://kmeleon.sf.net/file/beta/kmeleon065-beta.exe

Sorry for the delay.  I recently "upgraded" my computer, and due to some 
hardware incompatibilties, it's been nearly unusable for the last few 
days.  I did manage to get this kicked together, but it's still lacking 
polish.

-- Jeff

Jeff,

Actually, I think the URL is:

http://kmeleon.sf.net/files/beta/kmeleon065-beta.exe

Time for a test spin!

Andrew



On Sun, 15 Sep 2002, Jeff Doozan wrote:

> Here's the new build.
> 
> http://kmeleon.sf.net/file/beta/kmeleon065-beta.exe
> 
> Sorry for the delay.  I recently "upgraded" my computer, and due to some 
> hardware incompatibilties, it's been nearly unusable for the last few 
> days.  I did manage to get this kicked together, but it's still lacking 
> polish.
> 
> -- Jeff
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev
>

Jeff,

Here's what I'm seeing with the new build:

1) New installer looks great! 

2) It's very quick! Which Mozilla version are we using?

3) It looks like the initial focus bug is gone. This is where K-Meleon
wouldn't recognize as link until you set focus on the browser window. Can
someone confirm that? I still am seeing scrollwheels not always
recognizing the window but that's less of an issue to me.

I just found one major new bug. The rest are mostly spit-and-polish items
and ones that we've known about. I think most of these can be cleaned up
in fairly short order.

New Bugs:

1) Print Preview crashes in gkgfx.dll

Old Bugs:

1) Switching between profiles "on-the-fly" causes problems with second
profile - this is an old one, not sure why it didn't make our lists.

2) Text displayed when exiting secure site doesn't fit dialog box.

3) Dialog box for viewing certificates is too small. Now that I've played
around with "Allow All Windows to be resized" - that allows you to resize
the dialog and "Fix" the problem. Can we just turn that on by default
until we get a permanent fix in place?

4) Selecting Help in Mozilla-style dialog boxes throws errors. This hasn't
been reported before but I'm sure it was in old builds too.

5) No download progress on file download from "Save Link As.."

6) Browser Identification includes older browser versions. Should we
update Netscape and identify us as Mozilla?

7) View Source using an external app like Notepad doesn't work.

8) On File - Save As, it only saves "Web Page, Complete". No other file
types listed are saved.

9) This Mozilla bug:

http://bugzilla.mozilla.org/show_bug.cgi?id=28586

allows us to add this pref:

user_pref("browser.xul.error_pages.enabled", true);

to eliminate dialog pop-ups on bad domains. This is much wanted by those
who use ad blockers. Just adding that pref. generates an error. Is that
something we can fix on our end? This should be on by default, IMO.

10) If you hide the Layers toolbar and then select to open a link in a
"New Layer", it opens a new window. Not a bad behavior but is there any
way to reopen the Layers toolbar if requested in that way?

11) Any way to make the plugins listed in under Preferences - Plugins
appear alphabetically?

12) Did we want to add the Fontsize macro to the View menu?

13) No Frame-specific source when View Source on a page in a Frameset.
This is a known MFCEmbed bug.

That's it for now. This is looking pretty good!

Andrew

We might want to check on this bug:

http://bugzilla.mozilla.org/show_bug.cgi?id=145579

and adjust accordingly, IF we are affected. I haven't had a chance to test
yet.

Andrew

looks good, i like the new installer

----- Original Message ----- 
From: "Jeff Doozan" <jeff@...>
To: <Kmeleon-dev@...>
Sent: Sunday, September 15, 2002 5:36 PM
Subject: [Kmeleon-dev] New Build


> Here's the new build.
> 
> http://kmeleon.sf.net/file/beta/kmeleon065-beta.exe
> 
> Sorry for the delay.  I recently "upgraded" my computer, and due to some 
> hardware incompatibilties, it's been nearly unusable for the last few 
> days.  I did manage to get this kicked together, but it's still lacking 
> polish.
> 
> -- Jeff
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

> 1) New installer looks great! 
ditto

> 2) It's very quick! Which Mozilla version are we using?
it looks like 1.1 (yippee!)

I've tried to reproduce this bug in Moz 1.2a and the recent K-M builds
I've tested. I can't. This is leading me to doubt if this is the scare
it really is. If it is, should we enable the workaround someone posted
over at MozillaZine by default in the next builds and in 0.7?

!<hoshie@...> Mon, 16 Sep 2002 04:27:35 -0500:

> I've tried to reproduce this bug in Moz 1.2a and the recent K-M builds
> I've tested. I can't. This is leading me to doubt if this is the scare
> it really is. If it is, should we enable the workaround someone posted
> over at MozillaZine by default in the next builds and in 0.7?

we could just have the pref("network.http.sendRefererHeader")
set to the 'only on clicks' option... or is that the workaround?

seems like i heard opera has referer sending turned off by
default... if this is true, that might not be a bad example to
follow.

maybe this pref should make it's way into the Prefs dialog?

-- 
   po

none of my macros using the prompt() function work in the newest
build... also, the default macros.cfg is missing lots of ';'
line terminations in many of the commented examples.

otherwise, so far, so good. :)

-- 
    po

> seems like i heard opera has referer sending turned off by
> default... if this is true, that might not be a bad example to
> follow

Noooooo!   referer data is valuable,  i dislike even having the option to to disable it, but to
disable it by default? no no no.  if all browsers did that server logs would be nearly worthless.

Another oldie but goodie:

1) When you select the Loader menu, if you move the mouse off the menu, it
doesn't go away.

Andrew

>
>> seems like i heard opera has referer sending turned off by
>> default... if this is true, that might not be a bad example to
>> follow
>
> Noooooo!   referer data is valuable,  i dislike even having the option
> to to disable it, but to disable it by default? no no no.  if all
> browsers did that server logs would be nearly worthless.
>

I agree, it would be bad tot fully disable the referer. I made a site which
uses the referer data for navigation. I'm sure I'm not the only one that
uses HTTP_REFERER in that manner.
However, if Mozilla can have the referer behavior similar to cookies and
only send referers when you navigate the same site, then that might be a
good choice.

Edwin

* Andrew I. Mutch <amutch@...> [2002-09-16, 03:03 -0400]:
> 10) If you hide the Layers toolbar and then select to open a link in a
> "New Layer", it opens a new window. Not a bad behavior but is there any
> way to reopen the Layers toolbar if requested in that way?

This is nothing I recognise.. Could you please explain a bit more
detailed what you do, what happens, and what you want to happen? I'll
try to look at it tomorrow. But it should be possible to use Layers
without toolbar. That's how the fist few versions worked. (and it
still works for me, unless i misunderstand what you try).

-- 
/Ulf

Ulf,

1) Start K-Meleon
2) Select View - Toolbars and toggle off Layers toolbar.
3) Right click on a link and select to open the link in a "New Layer".
4) The link opens in a New Window.

Now, I know this behavior seems a little strange. But the idea was that if
you had turned off the Layers toolbar to gain more screenspace that when you
decided to open a link using the Layers option, it would re-enable the Layers
toolbar. Mozilla handles tabs in a similar fashion. The Tabs toolbar only
appears once you start using tabs and I believe it goes away when you close
the second to last tab.

Let me know if that makes more sense.

Andrew

Ulf Erikson wrote:

> * Andrew I. Mutch <amutch@...> [2002-09-16, 03:03 -0400]:
> > 10) If you hide the Layers toolbar and then select to open a link in a
> > "New Layer", it opens a new window. Not a bad behavior but is there any
> > way to reopen the Layers toolbar if requested in that way?
>
> This is nothing I recognise.. Could you please explain a bit more
> detailed what you do, what happens, and what you want to happen? I'll
> try to look at it tomorrow. But it should be possible to use Layers
> without toolbar. That's how the fist few versions worked. (and it
> still works for me, unless i misunderstand what you try).
>
> --
> /Ulf
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

* Andrew Mutch <amutch@...> [2002-09-16, 13:05 -0400]:
> 1) Start K-Meleon
> 2) Select View - Toolbars and toggle off Layers toolbar.
> 3) Right click on a link and select to open the link in a "New Layer".
> 4) The link opens in a New Window.

Hmm.. That's how I read it first, and what I tried, but I don't get a
new window..

> Now, I know this behavior seems a little strange. But the idea was that if
> you had turned off the Layers toolbar to gain more screenspace that when you
> decided to open a link using the Layers option, it would re-enable the Layers
> toolbar. Mozilla handles tabs in a similar fashion. The Tabs toolbar only
> appears once you start using tabs and I believe it goes away when you close
> the second to last tab.
> 
> Let me know if that makes more sense.

The report makes sense. The bug not :)

-- 
Ulf

-----Original Message-----
From: kmeleon-dev-admin@...
[mailto:kmeleon-dev-admin@...] On Behalf Of Rob
Sent: Monday, September 16, 2002 5:01 AM
To: po; kmeleon-dev list
Subject: Re: [Kmeleon-dev] Recent Mozilla Security Bug



> seems like i heard opera has referer sending turned off by default... 
> if this is true, that might not be a bad example to follow

Noooooo!   referer data is valuable,  i dislike even having the option
to to disable it, but to
disable it by default? no no no.  if all browsers did that server logs
would be nearly worthless.

I'm not suggesting that we disable this *by default*. I was suggesting
we disable this until the bug is fixed.

Joshua

<HTML><HEAD>
</HEAD>
<BODY>
<div><FONT FACE=3D"Arial" SIZE=3D2> I have script in my toolbars.cfg=
 that it will Open Layer &amp; Close </FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> Layer. It has worked=
 properly.</FONT></div>
<div>&nbsp;</div>
<i><FONT FACE=3D"Arial" SIZE=3D2> </FONT></i><div><i><FONT=
 FACE=3D"Arial" SIZE=3D2> &nbsp; LayerOpen {</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 layers(Open)</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 New Layer/Tab</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 toolhot.bmp[15]</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 toolcold.bmp[15]</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 tooldead.bmp[15]</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;=
 }</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp; LayerClose=
 {</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 layers(Close)</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Close Layer/Tab</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 closelay.bmp</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 closelay.bmp</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 closelay.bmp</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;=
 }</FONT></i></div>
<div>&nbsp;</div>
<i><FONT FACE=3D"Arial" SIZE=3D2> </FONT></i><div><FONT FACE=3D"Arial"=
 SIZE=3D2> But when I installed the new build, Kmeleon0.65 build=
 488 (with </FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> Layers plugin rev 1.6 ? ), my=
 &quot;LayerClose&quot; script did not work.</FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> Then I create a new script in=
 macros.cfg like this:</FONT></div>
<div>&nbsp;</div>
<FONT FACE=3D"Arial" SIZE=3D2> </FONT><div><i><FONT FACE=3D"Arial"=
 SIZE=3D2> LayerClose {</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp; plugin(layers,=
 Close)</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> }</FONT></i></div>
<div>&nbsp;</div>
<i><FONT FACE=3D"Arial" SIZE=3D2> </FONT></i><div><FONT FACE=3D"Arial"=
 SIZE=3D2> and script in toolbars.cfg :</FONT></div>
<div>&nbsp;</div>
<i><FONT FACE=3D"Arial" SIZE=3D2> </FONT></i><div><FONT FACE=3D"Arial"=
 SIZE=3D2> &nbsp; </FONT><i><FONT FACE=3D"Arial" SIZE=3D2>  LayerClose=
 {</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 macros(LayerClose)</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Close Layer/Tab</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 closelay.bmp</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 closelay.bmp</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 closelay.bmp</FONT></i></div>
<div><i><FONT FACE=3D"Arial" SIZE=3D2> &nbsp;&nbsp;=
 }</FONT></i></div>
<div>&nbsp;</div>
<FONT FACE=3D"Arial" SIZE=3D2> </FONT><div><FONT FACE=3D"Arial" SIZE=3D2>=
 This script working properly.</FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> and now, I have a great browser=
 (minus AutoComplete).</FONT></div>
<div>&nbsp;</div>
<FONT FACE=3D"Arial" SIZE=3D2> </FONT><div><FONT FACE=3D"Arial" SIZE=3D2>=
 -- </FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2>=
 ------------------------------------------------</FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> AF-Thoni, </FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> thoni1@... on=
 17/09/2002</FONT></div>
<div><FONT FACE=3D"Arial" SIZE=3D2> ICQ: 127 430 102</FONT></div>
<div>&nbsp;</div>
</body></html>

I made a test case, and yes we, like Moz1.1, are indeed affected.
http://www.script-source.net/km/moz_referer_bug/

I do not think this is a huge privacy issue though.  Where you come from isn't much different than
where you go to, and I think the extremity of the issue is exaggerated in the bugzilla comments.

-Rob


----- Original Message -----
From: "Andrew I. Mutch" <amutch@...>
To: <Kmeleon-dev@...>
Sent: Monday, September 16, 2002 2:31 AM
Subject: [Kmeleon-dev] Recent Mozilla Security Bug


> We might want to check on this bug:
>
> http://bugzilla.mozilla.org/show_bug.cgi?id=145579
>
> and adjust accordingly, IF we are affected. I haven't had a chance to test
> yet.
>
> Andrew
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

I've pulled together the first day's worth of bugs reported to the list
and the forum. I sorted out the bugs that seem to deserve some attention.
There are either "blockers" or cases where functionality is limited or
broken. The rest are minor bugs. I'm hoping that we can:

1) Assign priorities to these bugs

2) Pull out those that can be fixed in K-Meleon 0.8.

3) Have coders take ownership to get these fixed as quickly as possible
and checked into CVS. 

Andrew

Here's the list:
 
Major Bugs

1) Mozilla Referrer Bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=145579

Rob's test case:
http://www.script-source.net/km/moz_referer_bug/

Suggested workaround:

Add the line

user_pref("capability.policy.default.Window.onunload", "noAccess");

to your user.js file.

2) Print Preview crashes in gkgfx.dll

3) Macros using the prompt() function don't work in the newest
build.Also the default macros.cfg is missing lots of ';' line terminations
in many of the commented examples.

4) The new install program always installs all of the plugins even if you
deselect some of them.

5) No download progress on file download from "Save Link As.."

6) View Source using an external app like Notepad doesn't work.

7) On File - Save As, it only saves "Web Page, Complete". No other file
types listed are saved.

Other Bugs

* Old skins no longer work with current toolbar configuration files.
Authors need to update their skins to match the new configuration.

* Switching between profiles "on-the-fly" causes problems with second
profile - this is an old one, not sure why it didn't make our lists.
Text displayed when exiting secure site doesn't fit dialog box.

* Dialog box for viewing certificates is too small. Now that I've played
around with "Allow All Windows to 

be resized" - that allows you to resize the dialog and "Fix" the problem.
Can we just turn that on by default until we get a permanent fix in place?

* When you select the Loader menu, if you move the mouse off the menu, it
doesn't go away.

* Selecting Help in Mozilla-style dialog boxes throws errors. This 
hasn't been reported before but I'm sure it was in old builds too.

* Browser Identification includes older browser versions. Should we update
Netscape and identify us as Mozilla? Might want to revise to match
Mozilla spec per Developer list
posting.

* This Mozilla bug:

http://bugzilla.mozilla.org/show_bug.cgi?id=28586

allows us to add this pref:

user_pref("browser.xul.error_pages.enabled", true);

to eliminate dialog pop-ups on bad domains. This is much wanted by those
who use ad blockers. Just adding 

that pref. generates an error. Is that something we can fix on our end?
This should be on by default, IMO.

* If you hide the Layers toolbar and then select to open a link in a
"New Layer", it opens a new window. Not a bad behavior but is there any
way to reopen the Layers toolbar if requested in that way?

* Any way to make the plugins listed in under Preferences - Plugins appear
alphabetically?

* Did we want to add the Fontsize macro to the View menu?

* No Frame-specific source when View Source on a page in a Frameset. This
is a known MFCEmbed bug.

* Applets flicker on this page: http://www.acuteapplets.com/

* When typing into text boxes on web pages, the arrow keys on keyboard
don't seem to move the cursor around.

> Major Bugs

We're still missing here one - visited links colour still doesn't apply. 
I was like secretly hoping this one got fixed when I saw you didn't 
include it bug list but I still can't get visited links to work. So 
please don't exclude this from bug list unless we at least have some 
kind of workaround to this.


sven

!<robjohnson@...> Mon, 16 Sep 2002 22:13:06 -0500:

> I do not think this is a huge privacy issue though. Where you
> come from isn't much different than where you go to, and I
> think the extremity of the issue is exaggerated in the
> bugzilla comments.

i certainly didn't/don't want to start an argument on this list,
and i fully retract the suggestion about disabling referers. :)

                         --HOWEVER--

i would like to point out that thinking of URLs as only
signifying 'where you came from' or 'where you go to' is
overlooking the fact that they often carry other information
that is even less something you want malicious people to have,
such as session ID strings for webmail, etc... most webmail
services take measures to protect you from this if, for example,
you click on a link in a message, but they can't very well
protect you from an exploit like this... just to keep in mind.

-- 
    po

> i certainly didn't/don't want to start an argument on this list,
> and i fully retract the suggestion about disabling referers. :)

but i like arguing dammit! :)
i just think your average joe blow internet user, and even alot of experienced users, have been
brainwashed into thinking horrible nasty things will happen to them if any stranger gets any little
bit of information about them, and at the same time they're registered yahoo.com and iwon.com
members and 80% of their cookies are for ad targeting.

now, i have some webpages that are not necessarily top secret, but are works in progress.  not a
link on the internet exists to these pages, only my own personal bookmarks.  i wouldnt necessarilly
be happy if the link showed up in someones logs, but if it were anything that would actually bother
me it would be secured, period.

Much more information is revealed about you when you visit a page than what the URI you happen to
exit to will ever say, unless that page happens to be your personal life story or some crap. As far
as sessionids, if any site will validate a session based ONLY on the token, whether it includes
sensitive information or not, well, you can hardly blame the browser for that.

Anyways, it looks like a patch was posted and this may be resolved soon.

cheers,
-Rob

* Andrew I. Mutch <amutch@...> [2002-09-17, 00:00 -0400]:
> I've pulled together the first day's worth of bugs reported to the list
> and the forum. I sorted out the bugs that seem to deserve some attention.

> Here's the list:
>  
> Major Bugs

How about mix the list with older bugs too?

8) Bug 23: Prefs don't save in 'config' tab

I will write the manual as if one should use the builtin prefs editor
and not an external editor (hoping this is fixed before the manual is
complete;)

> 3) Macros using the prompt() function don't work in the newest
> build.

My guess is that Jeff forgot to include the new macros.rc into the
build. (or perhaps i never told him so even. everything is in cvs)

> Also the default macros.cfg is missing lots of ';' line terminations
> in many of the commented examples.

Post an updated macros.cfg and I will commit it.

> * Old skins no longer work with current toolbar configuration files.
> Authors need to update their skins to match the new configuration.

* Translations probably lack a number of menus and popups too.

? and how well do translations and skins work together today? (this
might be a point for the i18n plans)

> * When you select the Loader menu, if you move the mouse off the menu, it
> doesn't go away.

None of the popup menus for systray icons go away by just moving the
mouse off them for me. Never seen that behaviour. They go away if you
click anywhere. Wasn't the old bug that you had to choose an entry in
the menu to have it go away?

> * Browser Identification includes older browser versions. Should we update
> Netscape and identify us as Mozilla? Might want to revise to match
> Mozilla spec per Developer list
> posting.

These are all in prefs.js which claims to be automatically generated.
Is it? Where should these changes go instead? And could someone post a
list of newer browser to include as choices?

> * If you hide the Layers toolbar and then select to open a link in a
> "New Layer", it opens a new window. Not a bad behavior but is there any
> way to reopen the Layers toolbar if requested in that way?

I've still not reproduced this. Could it be that "New Window" was used
accidently?

> * Did we want to add the Fontsize macro to the View menu?

Post an updated menus.cfg and I can commit it if people say it is
good.

-- 
/Ulf

* AF-Thoni <thoni1@...> [2002-09-17, 09:47 +0000]:
> <HTML><HEAD>
> </HEAD>
> <BODY>
> <div><FONT FACE="Arial" SIZE=2> I have script in my toolbars.cfg that it will Open Layer &amp; Close </FONT></div>
> <div><FONT FACE="Arial" SIZE=2> Layer. It has worked properly.</FONT></div>
> <div>&nbsp;</div>
> <i><FONT FACE="Arial" SIZE=2> </FONT></i><div><i><FONT FACE="Arial" SIZE=2> &nbsp; LayerOpen {</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; layers(Open)</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; New Layer/Tab</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; toolhot.bmp[15]</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; toolcold.bmp[15]</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tooldead.bmp[15]</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp; }</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp; LayerClose {</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; layers(Close)</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Close Layer/Tab</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; closelay.bmp</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; closelay.bmp</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; closelay.bmp</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp; }</FONT></i></div>
> <div>&nbsp;</div>
> <i><FONT FACE="Arial" SIZE=2> </FONT></i><div><FONT FACE="Arial" SIZE=2> But when I installed the new build, Kmeleon0.65 build 488 (with </FONT></div>
> <div><FONT FACE="Arial" SIZE=2> Layers plugin rev 1.6 ? ), my &quot;LayerClose&quot; script did not work.</FONT></div>

It seems the latest additions for LayerButtonPopup made some layers
functions unusable from within toolbars. (and the button popup don't
work anyway due to a dated history plugin)

This has been fixed in CVS.
Thanks

/Ulf

> <div><FONT FACE="Arial" SIZE=2> Then I create a new script in macros.cfg like this:</FONT></div>
> <div>&nbsp;</div>
> <FONT FACE="Arial" SIZE=2> </FONT><div><i><FONT FACE="Arial" SIZE=2> LayerClose {</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp; plugin(layers, Close)</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> }</FONT></i></div>
> <div>&nbsp;</div>
> <i><FONT FACE="Arial" SIZE=2> </FONT></i><div><FONT FACE="Arial" SIZE=2> and script in toolbars.cfg :</FONT></div>
> <div>&nbsp;</div>
> <i><FONT FACE="Arial" SIZE=2> </FONT></i><div><FONT FACE="Arial" SIZE=2> &nbsp; </FONT><i><FONT FACE="Arial" SIZE=2>  LayerClose {</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; macros(LayerClose)</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Close Layer/Tab</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; closelay.bmp</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; closelay.bmp</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; closelay.bmp</FONT></i></div>
> <div><i><FONT FACE="Arial" SIZE=2> &nbsp;&nbsp; }</FONT></i></div>
> <div>&nbsp;</div>
> <FONT FACE="Arial" SIZE=2> </FONT><div><FONT FACE="Arial" SIZE=2> This script working properly.</FONT></div>
> <div><FONT FACE="Arial" SIZE=2> and now, I have a great browser (minus AutoComplete).</FONT></div>
> <div>&nbsp;</div>
> <FONT FACE="Arial" SIZE=2> </FONT><div><FONT FACE="Arial" SIZE=2> -- </FONT></div>
> <div><FONT FACE="Arial" SIZE=2> ------------------------------------------------</FONT></div>
> <div><FONT FACE="Arial" SIZE=2> AF-Thoni, </FONT></div>
> <div><FONT FACE="Arial" SIZE=2> thoni1@... on 17/09/2002</FONT></div>
> <div><FONT FACE="Arial" SIZE=2> ICQ: 127 430 102</FONT></div>
> <div>&nbsp;</div>
> </body></html>
> 
> 
> 
> -------------------------------------------------------
> Sponsored by: AMD - Your access to the experts on Hammer Technology!
> Open Source & Linux Developers, register now for the AMD Developer
> Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

Sven,

I didn't include that as it really is a Mozilla bug. However, I can add it
to the list. There's supposed to be a fix for that from Mozilla but it
hasn't been checked in yet. I can look to see if there is a patch posted to
get this to work.

Andrew


sven wrote:

>  > Major Bugs
>
> We're still missing here one - visited links colour still doesn't apply.
> I was like secretly hoping this one got fixed when I saw you didn't
> include it bug list but I still can't get visited links to work. So
> please don't exclude this from bug list unless we at least have some
> kind of workaround to this.
>
> sven
>
> -------------------------------------------------------
> Sponsored by: AMD - Your access to the experts on Hammer Technology!
> Open Source & Linux Developers, register now for the AMD Developer
> Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

Ulf,

I was focused on bugs that were holding up a release or that were easy to fix. I
can include older ones too where appropriate. Let me know which ones you think
need to be on the list. I can review that list too.


> How about mix the list with older bugs too?
>
> 8) Bug 23: Prefs don't save in 'config' tab

Are we still seeing problems with this bug?

>
> None of the popup menus for systray icons go away by just moving the
> mouse off them for me. Never seen that behaviour. They go away if you
> click anywhere. Wasn't the old bug that you had to choose an entry in
> the menu to have it go away?

Sorry - that's my error. You are correct about which was the bug. I think that
is working now.

> > * Browser Identification includes older browser versions. Should we update
> > Netscape and identify us as Mozilla? Might want to revise to match
> > Mozilla spec per Developer list
> > posting.
>
> These are all in prefs.js which claims to be automatically generated.
> Is it? Where should these changes go instead? And could someone post a
> list of newer browser to include as choices?

Check in Preferences.cpp and Preferences.h for locations where that might be
hard-coded.

New Browsers:

Netscape 4.8
Netscape 7

>
> I've still not reproduced this. Could it be that "New Window" was used
> accidently?

No but I think Bill pointed out where the confusion lays:

"When I tried it appears to open a new window - but if you look on th layers
drop down menu it is in fact another layer.  The toolbar doesn't reappear as
Andrew expects which could be where the issue lies.  The same behaviour
happens in Opera where our "layers" are referred to as "windows".

> > * Did we want to add the Fontsize macro to the View menu?
>
> Post an updated menus.cfg and I can commit it if people say it is
> good.

I'll get that added if no one else does it first. I think it actually is Po's
baby.

Andrew

looks like a patch for this was checked in, I assume KM .7 can be built with this Moz bug patched? 

----- Original Message ----- 
From: "po" <pobelly@...>
To: "kmeleon-dev list" <kmeleon-dev@...>
Sent: Tuesday, September 17, 2002 12:54 AM
Subject: Re: [Kmeleon-dev] Recent Mozilla Security Bug


> 
>  !<robjohnson@...> Mon, 16 Sep 2002 22:13:06 -0500:
> 
> > I do not think this is a huge privacy issue though. Where you
> > come from isn't much different than where you go to, and I
> > think the extremity of the issue is exaggerated in the
> > bugzilla comments.
> 
> i certainly didn't/don't want to start an argument on this list,
> and i fully retract the suggestion about disabling referers. :)
> 
>                          --HOWEVER--
> 
> i would like to point out that thinking of URLs as only
> signifying 'where you came from' or 'where you go to' is
> overlooking the fact that they often carry other information
> that is even less something you want malicious people to have,
> such as session ID strings for webmail, etc... most webmail
> services take measures to protect you from this if, for example,
> you click on a link in a message, but they can't very well
> protect you from an exploit like this... just to keep in mind.
> 
> -- 
>     po
> 
> 
> 
> -------------------------------------------------------
> Sponsored by: AMD - Your access to the experts on Hammer Technology! 
> Open Source & Linux Developers, register now for the AMD Developer 
> Symposium. Code: EX8664 http://www.developwithamd.com/developerlab
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

!<ulferikson@...> Tue, 17 Sep 2002 20:02:06 +0200:

>> Also the default macros.cfg is missing lots of ';' line
>> terminations in many of the commented examples.

> Post an updated macros.cfg and I will commit it.

here's this.

>> * Did we want to add the Fontsize macro to the View menu?

> Post an updated menus.cfg and I can commit it if people say it
> is good.

i'll do that, but what's the status of hooking into the mozilla
fontsize function that works on *all* screen fonts, but only
changes them per window, and temporarily? If we're going to
incorporate that, then the macro should be called 'set base
fontsize' or something like that, to distinguish it, i suppose?

-- 
    po

Major Bugs

1) Mozilla Referrer Bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=145579

Rob's test case: http://www.script-source.net/km/moz_referer_bug/

Suggested workaround:

Add the line

user_pref("capability.policy.default.Window.onunload", "noAccess");

to your user.js file.

Mozilla has fixed this. 

<snipped>

* Browser Identification includes older browser versions. Should we
update Netscape and identify us as Mozilla? Might want to revise to
match Mozilla spec per Developer list posting.

K-M's default User Agent is missing the product token & comment. It
should be this: 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
K-Meleon/x.x

The x.x is the current version of the day. The current default user
agent is:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826

<snipped>

Joshua

Josh,

Thanks for the updates. I'll get a revised and updated bug list posted up
tomorrow so we can see how we are progressing.

Andrew



On Tue, 17 Sep 2002, Joshua Holman wrote:

> 
> 
> Major Bugs
> 
> 1) Mozilla Referrer Bug:
> http://bugzilla.mozilla.org/show_bug.cgi?id=145579
> 
> Rob's test case: http://www.script-source.net/km/moz_referer_bug/
> 
> Suggested workaround:
> 
> Add the line
> 
> user_pref("capability.policy.default.Window.onunload", "noAccess");
> 
> to your user.js file.
> 
> Mozilla has fixed this. 
> 
> <snipped>
> 
> * Browser Identification includes older browser versions. Should we
> update Netscape and identify us as Mozilla? Might want to revise to
> match Mozilla spec per Developer list posting.
> 
> K-M's default User Agent is missing the product token & comment. It
> should be this: 
> 
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
> K-Meleon/x.x
> 
> The x.x is the current version of the day. The current default user
> agent is:
> 
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826
> 
> <snipped>
> 
> Joshua
> 
>

* po <pobelly@...> [2002-09-17, 19:27 -0700]:
>>> * Did we want to add the Fontsize macro to the View menu?
> 
>> Post an updated menus.cfg and I can commit it if people say it
>> is good.
> 
> i'll do that, but what's the status of hooking into the mozilla
> fontsize function that works on *all* screen fonts, but only
> changes them per window, and temporarily? If we're going to
> incorporate that, then the macro should be called 'set base
> fontsize' or something like that, to distinguish it, i suppose?

Sounds okay with me. Go for the longer name to be safe. Once it is in
the menu users don't see the macro name anyway.

What about the additions by Robert? Do they handle a common problem?
Anything we want to add? (considering the small size of macros i find
it okay to include quite some, but don't think all has to be bound to
accelerators or menu entries per default) The part I don't follow in
the macro is why the fixed and variable size are kept the same.

-- 
/Ulf

>>> * Browser Identification includes older browser versions. Should we update
>>> Netscape and identify us as Mozilla? Might want to revise to match
>>> Mozilla spec per Developer list
>>> posting.
>>
>> These are all in prefs.js which claims to be automatically generated.
>> Is it? Where should these changes go instead? And could someone post a
>> list of newer browser to include as choices?
> 
> Check in Preferences.cpp and Preferences.h for locations where that might be
> hard-coded.

The only place they are used is in PrefencesDlg.cpp. Values are read
from file and used in the dialog directly. The default value for a
missing user agent string is empty.

Shall I try edit Prefs.js?

How about the toolband info in the same file.. Why are non-active
rebars "visible"? Shouldn't all rebars have a unique index and a
non-zero size? Could this have something to do with bug #184?
  http://kmeleon.sourceforge.net/bugs/viewbug.php?bugid=184
  
> New Browsers:
> 
> Netscape 4.8
> Netscape 7

I would need the full strings :)

>>> * Did we want to add the Fontsize macro to the View menu?
>>
>> Post an updated menus.cfg and I can commit it if people say it is
>> good.
> 
> I'll get that added if no one else does it first. I think it actually is Po's
> baby.

Will you also look at the font macros by Robert Daut?
  http://www.geocrawler.com/lists/3/SourceForge/9632/0/9645514/

Could the menu also include ready settings for big/normal/small fonts?

-- 
Ulf

Hi,
Where Can I  can Get the Newest build? (Build 674)
thanks

6. No default cookieBehavior.

in all.js, the cookieBehavior value is set as 3.
I changed this to 0.
pref("network.cookie.cookieBehavior",       0); 


19. Set K-Meleon to default browser isn't done properly

This is a bug with the "setbrowser" program, not with kmeleon or the 
installer.


5. Rebars lose their position when switched from invisible to visible 
state.

Added Ulf's patch, feedback needed.

22. Downloading from ftp can show filesize -0.00

Some sanity checking added to ensure "accurate" numbers

2. Unable to make paper size selection stay.

Fixed.


I'd still like a test URL for this, I didn't see one it the detailed 
explanation:

21. The URL bar is cleared when a link in a new window fails to load.


http://kmeleon.sf.net/files/beta/kmeleon065_beta.exe

-- Jeff

I have reshuffled the latest fixes in the bug-list. Hope all beta
testers help out in verifying whether the Fixed bugs are truely gone.
Also bug 20 and 16 have had "thought i already fixed that" comments.
Please dubble check that there are bugs present and report it back.

/Ulf

* Jeff Doozan <jeff@...> [2002-10-27, 17:10 -0500]:
> I'd still like a test URL for this, I didn't see one it the detailed 
> explanation:
> 
> 21. The URL bar is cleared when a link in a new window fails to load.

Maybe it is the same as bug #87 in the BTS:
  http://kmeleon.sourceforge.net/bugs/viewbug.php?bugid=87

____________________________________________________________

Must-do:
  1. Print Preview behaves erraticly and can cause K-Meleon to crash.
  4. Uninstaller always deletes everything.
 14. Clicking on an empty browser window causes K-Meleon to crash
 20. Installer doesn't run if loader is running. (tested lately?)

Might-do:
 16. View source doesn't show the correct page for dynamic pages. (tested lately?)

These can probably be fixed without coding (chrome/component issues):
 12. Viewing certificates locks up.
 10. Selecting Help in Mozilla-style dialog boxes throws errors.
 11. Https doesn't work for sites with expired or mismatched certificates.
  9. Visited links don't show different color.
 23. Browser Identification includes older browser versions.
 27. Add support for changing skin. (macro?)

   --------------------

Mozilla Bugs:
 13. warnAboutCookies opens large dialogbox and hangs while loading.
  8. Text doesn't fit dialog box when exiting encrypted pages

Til later:
  7. Pop-up windows can become fullscreen when brought up from minimized state.
 15. Switching profiles in session creates a messed-up second session.
 17. View - Toolbars show a menu which isn't properly aligned.
 25. List the plugins under Preferences - Plugins alphabetically
 30. Configurable mouse events in accel.cfg
 26. Add more cookie handling to Edit - Preference - Privacy
 28. Typos in intaller.
 21. The URL bar is cleared when a link in a new window fails to load.

Fixed:
  2. Unable to make paper size selection stay.
  3. Installer always install everything. (might be fixed already?)
  5. Rebars lose their position when switched from invisible to visible state.
  6. No default cookieBehavior.
 18. Painting problems with About.
 22. Downloading from ftp can show filesize -0.00
 24. Did we want to add the Fontsize macro to the View menu?
 29. Comments in toolbars.cfg are wrong (but the code is right)

Invalid:
 19. Set K-Meleon to default browser isn't done properly

Someone posted the 674 build on betanews.com

//PH

Jeff Doozan wrote:

>6. No default cookieBehavior.
>
>in all.js, the cookieBehavior value is set as 3.
>I changed this to 0.
>pref("network.cookie.cookieBehavior",       0); 
>
>
>19. Set K-Meleon to default browser isn't done properly
>
>This is a bug with the "setbrowser" program, not with kmeleon or the 
>installer.
>
>
>5. Rebars lose their position when switched from invisible to visible 
>state.
>
>Added Ulf's patch, feedback needed.
>
>22. Downloading from ftp can show filesize -0.00
>
>Some sanity checking added to ensure "accurate" numbers
>
>2. Unable to make paper size selection stay.
>
>Fixed.
>
>
>I'd still like a test URL for this, I didn't see one it the detailed 
>explanation:
>
>21. The URL bar is cleared when a link in a new window fails to load.
>
>
>http://kmeleon.sf.net/files/beta/kmeleon065_beta.exe
>
>-- Jeff
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: ApacheCon, November 18-21 in
>Las Vegas (supported by COMDEX), the only Apache event to be
>fully supported by the ASF. http://www.apachecon.com
>_______________________________________________
>Kmeleon-dev mailing list
>Kmeleon-dev@...
>https://lists.sourceforge.net/lists/listinfo/kmeleon-dev
>
>  
>

And everyone began moaning and groaning about how bad the build is.  People
don't realize that this is a developer build - not a general normal person
build.

Whoever posted it there should be beaten to a pulp.


At 11:36 PM 10/27/02 +0100, Peter Halvarsson wrote:
>Someone posted the 674 build on betanews.com
>
>//PH
>
>Jeff Doozan wrote:
>
>>6. No default cookieBehavior.
>>
>>in all.js, the cookieBehavior value is set as 3.
>>I changed this to 0.
>>pref("network.cookie.cookieBehavior",       0); 
>>
>>
>>19. Set K-Meleon to default browser isn't done properly
>>
>>This is a bug with the "setbrowser" program, not with kmeleon or the 
>>installer.
>>
>>
>>5. Rebars lose their position when switched from invisible to visible 
>>state.
>>
>>Added Ulf's patch, feedback needed.
>>
>>22. Downloading from ftp can show filesize -0.00
>>
>>Some sanity checking added to ensure "accurate" numbers
>>
>>2. Unable to make paper size selection stay.
>>
>>Fixed.
>>
>>
>>I'd still like a test URL for this, I didn't see one it the detailed 
>>explanation:
>>
>>21. The URL bar is cleared when a link in a new window fails to load.
>>
>>
>>http://kmeleon.sf.net/files/beta/kmeleon065_beta.exe
>>
>>-- Jeff
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: ApacheCon, November 18-21 in
>>Las Vegas (supported by COMDEX), the only Apache event to be
>>fully supported by the ASF. http://www.apachecon.com
>>_______________________________________________
>>Kmeleon-dev mailing list
>>Kmeleon-dev@...
>>https://lists.sourceforge.net/lists/listinfo/kmeleon-dev
>>
>>  
>>
>
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: ApacheCon, November 18-21 in
>Las Vegas (supported by COMDEX), the only Apache event to be
>fully supported by the ASF. http://www.apachecon.com
>_______________________________________________
>Kmeleon-dev mailing list
>Kmeleon-dev@...
>https://lists.sourceforge.net/lists/listinfo/kmeleon-dev
>
>
--------------------------------
Brian Bruns
Founder, The Summit Open Source Development Group
Network Security & Research Division
http://www.2mbit.com
ICQ: 8077511

No spam tolerated.

The following are confirmed fixed:

3. Installer always installs everything: I did not install what I
unselected.

11. Https sites can't be loaded... : Load fine

18. Painting problems with About: Paints fine

28. Typos in installer: I did not see any typos in the installer. 

29. Typos in toolbars.cfg: Typo fixed

Bugs:

* One minor installer issue that I think Ulf mentioned: When you mouse
over the entry for the Opera Hotlist plugin, it doesn't display any text
describing what it is leaving the text for Internet Explorer displaying.

Looking good!

Andrew

> * One minor installer issue that I think Ulf mentioned: When you mouse
> over the entry for the Opera Hotlist plugin, it doesn't display any 
text
> describing what it is leaving the text for Internet Explorer 
displaying.

As always, thank you for your tireless bug hunting, Andrew (and Ulf!).  
This was just a part of the installer that I forgot to uncomment when we 
re-added the hotlist plugin, it should work fine in future builds.

-- Jeff

I went through Ulf's ordered list and confirmed fixed what I could. I've
also added some comments where I could find information that seemed to
apply. I suggest closing #23 and I've added #30, which is a new bug with
the Uninstall routine. Please review and continue testing!

Andrew

----------------------------------

Must-do:
  1. Print Preview behaves erraticly and can cause K-Meleon to crash.
  4. Uninstaller always deletes everything.
 14. Clicking on an empty browser window causes K-Meleon to crash
 20. Installer doesn't run if loader is running. 
Installer runs with beta 681 loader running with loader selected or
unselected on installation. However, browser does not load after 

installation is complete. You have to manually start it from the desktop
icon. 

Might-do:
 16. View source doesn't show the correct page for dynamic pages. 
It appears the browser is querying back to the server to generate the
source instead of using the source of the page that is loaded. Mozilla 

Tracking Bug: http://bugzilla.mozilla.org/show_bug.cgi?id=57724
Possibly relevant: http://bugzilla.mozilla.org/show_bug.cgi?id=60426
See Chimera Bug for possible fixes and links back to relevant Mozilla
bugs: http://bugzilla.mozilla.org/show_bug.cgi?id=153884

These can probably be fixed without coding (chrome/component issues):
 12. Viewing certificates locks up.
Mozilla bug needs to be filed. I'll try to work this up.
 10. Selecting Help in Mozilla-style dialog boxes throws errors.
The best way to view this is to visit one of the https test sites
(https://levindustries.com) and select the "Help" button when the "View 

Certificate" window is generated. This will probably completed hang
K-Meleon and even if you close the browser, I usually find the process
running in the background. 
Either need to:
a) Include relevant chrome
b) Generate our own dialog boxes that don't include a "Help" button. 
  9. Visited links don't show different color.
http://bugzilla.mozilla.org/show_bug.cgi?id=70714
 23. Browser Identification includes older browser versions.
Let's close this. It's not a critical issue and supports the two things
that people want - privacy and browser sniffing. I believe that Jeff updated the Default string to include the K-Meleon information.
 27. Add support for changing skin. (macro?)

New:
 30. Uninstaller hangs if Loader running

   --------------------

Mozilla Bugs:
 13. warnAboutCookies opens large dialogbox and hangs while loading.
Mozilla bug needs to be filed. I'll try to work this up.
  8. Text doesn't fit dialog box when exiting encrypted pages
Mozilla bug needs to be filed. I'll try to work this up.

Til later:
  7. Pop-up windows can become fullscreen when brought up from 
minimized state.
 15. Switching profiles in session creates a messed-up second session.
 17. View - Toolbars show a menu which isn't properly aligned.
 25. List the plugins under Preferences - Plugins alphabetically
 30. Configurable mouse events in accel.cfg
 26. Add more cookie handling to Edit - Preference - Privacy
Can we get more details on this?
 21. The URL bar is cleared when a link in a new window fails to load.

Fixed:
  2. Unable to make paper size selection stay.
  5. Rebars lose their position when switched from invisible to visible 
state.
 22. Downloading from ftp can show filesize -0.00

Fixed - Confirmed:
  3. Installer always install everything.
  6. No default cookieBehavior.
 11. Https doesn't work for sites with expired or mismatched 
certificates.
 18. Painting problems with About.
 24. Did we want to add the Fontsize macro to the View menu?
 28. Typos in installer.
 29. Comments in toolbars.cfg are wrong (but the code is right)

Invalid:
 19. Set K-Meleon to default browser isn't done properly

I've been trying to duplicate the password bug where saving two different
passwords for the same site causes the browser to crash on wallet.dll.
Assuming I'm testing the right bug, can someone test to see if they get
the same behavior?

Andrew

A nice small project for someone familiar with HTML is to crank out a new
"About:" page that is generated when you enter:

about: 

in the URL bar. Currently, it just spits up the default Mozilla page. If
we could have something more K-Meleon specific, it would be nice. The file
to edit is "about.xhtml" an is in the embed.jar archive in the chrome
directory. We would also want to replace the Mozilla graphic with a
K-Meleon one. That file is in the same archive as "logo.gif". 

Andrew

I'm adding the extra information Andrew asked for and confirm that 
bug 5 is fixed. Also suggest that 17 and 25 (and possibly 26) are
either closed or moved to BTS for later handlling.

/Ulf

----------------------------------

Must-do:
  1. Print Preview behaves erraticly and can cause K-Meleon to crash.

  4. Uninstaller always deletes everything.

 14. Clicking on an empty browser window causes K-Meleon to crash

 20. Installer doesn't run if loader is running. 

   Installer runs with beta 681 loader running with loader selected or
   unselected on installation. However, browser does not load after
   installation is complete. You have to manually start it from the
   desktop icon. 

   
Might-do:
 16. View source doesn't show the correct page for dynamic pages. 

   It appears the browser is querying back to the server to generate
   the source instead of using the source of the page that is loaded.
   Mozilla 

   Tracking Bug: http://bugzilla.mozilla.org/show_bug.cgi?id=57724
   Possibly relevant: http://bugzilla.mozilla.org/show_bug.cgi?id=60426
   See Chimera Bug for possible fixes and links back to relevant Mozilla
   bugs: http://bugzilla.mozilla.org/show_bug.cgi?id=153884

   
These can probably be fixed without coding (chrome/component issues):
 10. Selecting Help in Mozilla-style dialog boxes throws errors.

   The best way to view this is to visit one of the https test sites
   (https://levindustries.com) and select the "Help" button when the "View 

   Certificate" window is generated. This will probably completed hang
   K-Meleon and even if you close the browser, I usually find the
   process running in the background. 
   Either need to:
    a) Include relevant chrome
    b) Generate our own dialog boxes that don't include a "Help" button. 

  9. Visited links don't show different color.
   http://bugzilla.mozilla.org/show_bug.cgi?id=70714

 27. Add support for changing skin. (macro?)

 
New:
 30. Uninstaller hangs if Loader running

 
   --------------------

   
Mozilla Bugs:
 12. Viewing certificates locks up.
   Mozilla bug needs to be filed. I'll try to work this up.

 13. warnAboutCookies opens large dialogbox and hangs while loading.
   Mozilla bug needs to be filed. I'll try to work this up.

  8. Text doesn't fit dialog box when exiting encrypted pages
   Mozilla bug needs to be filed. I'll try to work this up.

   
Til later:
  7. Pop-up windows can become fullscreen when brought up from minimized state.

 15. Switching profiles in session creates a messed-up second session.

 26. Add more cookie handling to Edit - Preference - Privacy
    (I don't think we need to be able to control all preferences from
    the Edit-Preferences.. There is the prefs.js and macros also /Ulf)

"  I am currently using the newest k-m 0.65 beta, and I was surprised
"  to see that the more refined cookie handling present in Mozilla 1.0
"  is not configurable in the beta. I had to insert entries in my
"  prefs.js file, which I think could be done more easily in
"  preferences.
"
"  The prefs I am talking about are:
"
"    user_pref("network.cookie.lifetime.enabled", true);
"
"      Setting only this pref to true means that cookies will not be
"      saved, but it will act like the browser is accepting cookies
"      (same effect as making cookies.txt read-only).
"
"    user_pref("network.cookie.lifetime.behavior", 1);
"
"       This pref requires that the above pref be set. If this pref is
"       used, then cookies will have a maximum lifetime of 90 days,
"       which is the default.
"
"     user_pref("network.cookie.lifetime.days", 20);
"
"       This pref changes the maximum lifetime to a different number
"       (here I use 20).
"
"   I hope that someone adds something to the preferences>privacy options to
"   make use of this.

 21. The URL bar is cleared when a link in a new window fails to load.

"  When you open a link in a new window and the request fails, you
"  can't try again with the same window. Mozilla always keeps the url
"  in the url bar so you just have to press enter to try accessing the
"  site again.

"  Maybe it is the same as bug #87 in the BTS:
"    http://kmeleon.sourceforge.net/bugs/viewbug.php?bugid=87


Fixed:
  2. Unable to make paper size selection stay.
 22. Downloading from ftp can show filesize -0.00

 
Fixed - Confirmed:
  3. Installer always install everything.
  5. Rebars lose their position when switched from invisible to visible state.
  6. No default cookieBehavior.
 11. Https doesn't work for sites with expired or mismatched certificates.
 18. Painting problems with About.
 24. Did we want to add the Fontsize macro to the View menu?
 28. Typos in installer.
 29. Comments in toolbars.cfg are wrong (but the code is right)

 
Move to BTS or Close:
 23. Browser Identification includes older browser versions.
   Let's close this. It's not a critical issue and supports the two
   things that people want - privacy and browser sniffing. I believe
   that Jeff updated the Default string to include the K-Meleon
   information.
 17. View - Toolbars show a menu which isn't properly aligned.
 25. List the plugins under Preferences - Plugins alphabetically

 
Invalid:
 19. Set K-Meleon to default browser isn't done properly

!<amutch@...> Mon, 28 Oct 2002 01:20:00 -0500 (EST):

> I've been trying to duplicate the password bug where saving two
> different passwords for the same site causes the browser to crash on
> wallet.dll.

Confirmed that it's no longer a crashing bug (so far as i've been able
to stress it)... it appears that the second set of login info is added
alongside the old set in the password file, and upon returning to the
page again, *nothing* is automatically filled into the login fields...
obviously, this isn't the best possible scenario, but it's a hell of a
lot better than crashing the browser... :) Someone would simply have to
open the password file in a text editor at this point, and remove the
entry they no longer wanted, i guess. If this could eventually be
enhanced with an 'Overwrite Previously Saved Login?' dialog or something,
that would make password changes easy enough...

-- 
   po

I'm afraid that bug 2 doesn't seem to be fixed - but has changed. Instead=
 of reverting to US Letter it now changes to user defined 0mm x 0mm.
Also Print Preview no longer makes KM crash for me. Instead I get the save=
 dialog, which when cancelled leaves me with a page full of oversized=
 jumbled text, which refreshing doesn't correct.
Otherwise, it's definitely getting there!

Jon

*********** REPLY SEPARATOR  ***********

On 28/10/02 at 08:16 Ulf Erikson wrote:

>I'm adding the extra information Andrew asked for and confirm that 
>bug 5 is fixed. Also suggest that 17 and 25 (and possibly 26) are
>either closed or moved to BTS for later handlling.
>
>/Ulf
>
>----------------------------------
>
>Must-do:
>  1. Print Preview behaves erraticly and can cause K-Meleon to crash.
>
>  4. Uninstaller always deletes everything.
>
> 14. Clicking on an empty browser window causes K-Meleon to crash
>
> 20. Installer doesn't run if loader is running. 
>
>   Installer runs with beta 681 loader running with loader selected or
>   unselected on installation. However, browser does not load after
>   installation is complete. You have to manually start it from the
>   desktop icon. 
>
>   
>Might-do:
> 16. View source doesn't show the correct page for dynamic pages. 
>
>   It appears the browser is querying back to the server to generate
>   the source instead of using the source of the page that is loaded.
>   Mozilla 
>
>   Tracking Bug: http://bugzilla.mozilla.org/show_bug.cgi?id=3D57724
>   Possibly relevant: http://bugzilla.mozilla.org/show_bug.cgi?id=3D60426
>   See Chimera Bug for possible fixes and links back to relevant Mozilla
>   bugs: http://bugzilla.mozilla.org/show_bug.cgi?id=3D153884
>
>   
>These can probably be fixed without coding (chrome/component issues):
> 10. Selecting Help in Mozilla-style dialog boxes throws errors.
>
>   The best way to view this is to visit one of the https test sites
>   (https://levindustries.com) and select the "Help" button when the "View=
 
>
>   Certificate" window is generated. This will probably completed hang
>   K-Meleon and even if you close the browser, I usually find the
>   process running in the background. 
>   Either need to:
>    a) Include relevant chrome
>    b) Generate our own dialog boxes that don't include a "Help" button. 
>
>  9. Visited links don't show different color.
>   http://bugzilla.mozilla.org/show_bug.cgi?id=3D70714
>
> 27. Add support for changing skin. (macro?)
>
> 
>New:
> 30. Uninstaller hangs if Loader running
>
> 
>   --------------------
>
>   
>Mozilla Bugs:
> 12. Viewing certificates locks up.
>   Mozilla bug needs to be filed. I'll try to work this up.
>
> 13. warnAboutCookies opens large dialogbox and hangs while loading.
>   Mozilla bug needs to be filed. I'll try to work this up.
>
>  8. Text doesn't fit dialog box when exiting encrypted pages
>   Mozilla bug needs to be filed. I'll try to work this up.
>
>   
>Til later:
>  7. Pop-up windows can become fullscreen when brought up from minimized
>state.
>
> 15. Switching profiles in session creates a messed-up second session.
>
> 26. Add more cookie handling to Edit - Preference - Privacy
>    (I don't think we need to be able to control all preferences from
>    the Edit-Preferences.. There is the prefs.js and macros also /Ulf)
>
>"  I am currently using the newest k-m 0.65 beta, and I was surprised
>"  to see that the more refined cookie handling present in Mozilla 1.0
>"  is not configurable in the beta. I had to insert entries in my
>"  prefs.js file, which I think could be done more easily in
>"  preferences.
>"
>"  The prefs I am talking about are:
>"
>"    user_pref("network.cookie.lifetime.enabled", true);
>"
>"      Setting only this pref to true means that cookies will not be
>"      saved, but it will act like the browser is accepting cookies
>"      (same effect as making cookies.txt read-only).
>"
>"    user_pref("network.cookie.lifetime.behavior", 1);
>"
>"       This pref requires that the above pref be set. If this pref is
>"       used, then cookies will have a maximum lifetime of 90 days,
>"       which is the default.
>"
>"     user_pref("network.cookie.lifetime.days", 20);
>"
>"       This pref changes the maximum lifetime to a different number
>"       (here I use 20).
>"
>"   I hope that someone adds something to the preferences>privacy options
>to
>"   make use of this.
>
> 21. The URL bar is cleared when a link in a new window fails to load.
>
>"  When you open a link in a new window and the request fails, you
>"  can't try again with the same window. Mozilla always keeps the url
>"  in the url bar so you just have to press enter to try accessing the
>"  site again.
>
>"  Maybe it is the same as bug #87 in the BTS:
>"    http://kmeleon.sourceforge.net/bugs/viewbug.php?bugid=3D87
>
>
>Fixed:
>  2. Unable to make paper size selection stay.
> 22. Downloading from ftp can show filesize -0.00
>
> 
>Fixed - Confirmed:
>  3. Installer always install everything.
>  5. Rebars lose their position when switched from invisible to visible
>state.
>  6. No default cookieBehavior.
> 11. Https doesn't work for sites with expired or mismatched certificates.
> 18. Painting problems with About.
> 24. Did we want to add the Fontsize macro to the View menu?
> 28. Typos in installer.
> 29. Comments in toolbars.cfg are wrong (but the code is right)
>
> 
>Move to BTS or Close:
> 23. Browser Identification includes older browser versions.
>   Let's close this. It's not a critical issue and supports the two
>   things that people want - privacy and browser sniffing. I believe
>   that Jeff updated the Default string to include the K-Meleon
>   information.
> 17. View - Toolbars show a menu which isn't properly aligned.
> 25. List the plugins under Preferences - Plugins alphabetically
>
> 
>Invalid:
> 19. Set K-Meleon to default browser isn't done properly
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>Kmeleon-dev mailing list
>Kmeleon-dev@...
>https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

Antwort auf E-Mail von Andrew I. Mutch, vom 28 Oct 2002 1:40

> A nice small project for someone familiar with HTML is to crank out a
> new "About:" page that is generated when you enter:
> 
> about: 
> 
> in the URL bar. Currently, it just spits up the default Mozilla page.

There are at the top a star and 'mozilla' and the next line is the 
user-agent-string. My user-agent string is (translated): 'is not your 
matter'. It looks very funny:

     Mozilla
is not your matter

> We would also want to replace the Mozilla graphic with a K-Meleon
> one. That file is in the same archive as "logo.gif". 

IMHO the user-agent-string should be removed too :-)

--
Robert Daut, daut@...

im not sure of the legalities so i left the Mozilla/Netscape copyright info
on there.  also im not sure how to link to the ReadMe.htm file in the
install directory (for the Release Notes link)

-Rob

----- Original Message -----
From: "Andrew I. Mutch" <amutch@...>
To: <Kmeleon-dev@...>
Sent: Monday, October 28, 2002 12:40 AM
Subject: [Kmeleon-dev] New About Page


> A nice small project for someone familiar with HTML is to crank out a new
> "About:" page that is generated when you enter:
>
> about:
>
> in the URL bar. Currently, it just spits up the default Mozilla page. If
> we could have something more K-Meleon specific, it would be nice. The file
> to edit is "about.xhtml" an is in the embed.jar archive in the chrome
> directory. We would also want to replace the Mozilla graphic with a
> K-Meleon one. That file is in the same archive as "logo.gif".
>
> Andrew
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Kmeleon-dev mailing list
> Kmeleon-dev@...
> https://lists.sourceforge.net/lists/listinfo/kmeleon-dev

minor annoyance bug that i dont think ive seen reported:

when mousing over links and images with a 'title' attribute (IE: <a
href="foo.html" title="click here">) the tool tip appears about 100px below
the cursor, when it should appear immediately below the cursor.

-Rob

Rob,

Can the Mozilla link be less prominent? Also, can you include the UA string back
in there? People do ask what version of Mozilla it is running on. Good work.

Andrew

Rob Johnson wrote:

> im not sure of the legalities so i left the Mozilla/Netscape copyright info
> on there.  also im not sure how to link to the ReadMe.htm file in the
> install directory (for the Release Notes link)
>
> -Rob
>
> ----- Original Message -----
> From: "Andrew I. Mutch" <amutch@...>
> To: <Kmeleon-dev@...>
> Sent: Monday, October 28, 2002 12:40 AM
> Subject: [Kmeleon-dev] New About Page
>
> > A nice small project for someone familiar with HTML is to crank out a new
> > "About:" page that is generated when you enter:
> >
> > about:
> >
> > in the URL bar. Currently, it just spits up the default Mozilla page. If
> > we could have something more K-Meleon specific, it would be nice. The file
> > to edit is "about.xhtml" an is in the embed.jar archive in the chrome
> > directory. We would also want to replace the Mozilla graphic with a
> > K-Meleon one. That file is in the same archive as "logo.gif".
> >
> > Andrew
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Kmeleon-dev mailing list
> > Kmeleon-dev@...
> > https://lists.sourceforge.net/lists/listinfo/kmeleon-dev
>
>   ------------------------------------------------------------------------
>                   Name: about.xhtml
>    about.xhtml    Type: unspecified type (application/octet-stream)
>               Encoding: quoted-printable
>
>                Name: logo.gif
>    logo.gif    Type: GIF Image (image/gif)
>            Encoding: base64

I dont think this got through because of the attachments, heres links:
http://www.script-source.net/km/about/about.html
screenshot of how it should look ->
http://www.script-source.net/km/about/about_km.png
updated embed.jar -> http://www.script-source.net/km/about/embed.jar
----
I moved the Mozilla link up to the top, the UA is there its just smaller and
under the big K-Meleon link.  Are you not seeing it?  javascript must be
enabled for it to show (which is true for the old about: page also).  i've
attached a screenshot of how it looks on my system with km build 681.

also, about the 'Release Notes' link, i don't think it's possible to
determine the install directory from a webpage,
maybe Jeff can shed some light as to whether or not it's possible to link to
ReadMe.htm in the install directory (without knowing the exact path to the
install directory).
Id assume not since it would be a bit of a security hazard.  Otherwise we'll
have to either remove
that link, or add ReadMe.htm to embed.jar.

-Rob

----- Original Message -----
From: "Andrew Mutch" <amutch@...>
To: "Rob Johnson" <robjohnson@...>
Cc: <Kmeleon-dev@...>
Sent: Monday, October 28, 2002 12:24 PM
Subject: Re: [Kmeleon-dev] New About Page


> Rob,
>
> Can the Mozilla link be less prominent? Also, can you include the UA
string back
> in there? People do ask what version of Mozilla it is running on. Good
work.
>
> Andrew
>
> Rob Johnson wrote:
>
> > im not sure of the legalities so i left the Mozilla/Netscape copyright
info
> > on there.  also im not sure how to link to the ReadMe.htm file in the
> > install directory (for the Release Notes link)
> >
> > -Rob
> >
> > ----- Original Message -----
> > From: "Andrew I. Mutch" <amutch@...>
> > To: <Kmeleon-dev@...>
> > Sent: Monday, October 28, 2002 12:40 AM
> > Subject: [Kmeleon-dev] New About Page
> >
> > > A nice small project for someone familiar with HTML is to crank out a
new
> > > "About:" page that is generated when you enter:
> > >
> > > about:
> > >
> > > in the URL bar. Currently, it just spits up the default Mozilla page.
If
> > > we could have something more K-Meleon specific, it would be nice. The
file
> > > to edit is "about.xhtml" an is in the embed.jar archive in the chrome
> > > directory. We would also want to replace the Mozilla graphic with a
> > > K-Meleon one. That file is in the same archive as "logo.gif".
> > >
> > > Andrew
> > >

Okay, the two major bugs are fixed in this build now, which means this 
should be pretty close to 'release quality'.  I haven't added the about: 
changes yet, but I hope to do that later tonight.

http://kmeleon.sf.net/files/beta/kmeleon065_beta.exe

Please report all crashes and anything that you think needs to be 
changed before we call this .7

-- Jeff

Unless there are serious problems, or important things that I forgot, 
these are the binary files (plugins and kmeleon.exe) that will comprise 
.7.  I still need to get the installer cleaned up a tad, and the config 
files are easily changed if there's anything outstanding, but unless 
there are serious bugs or omissions, these are release quality binaries:

http://kmeleon.sf.net/files/beta/kmeleon065_beta.exe

To Check:
- Please check that the page setup dialog box is behaving properly now.

To Do:
- We still need to agree on a skins macro to include.

- We need to do some testing with installing this as an upgrade to 
Kmeleon 0.6.  Specifically with the matter of preserving existing 
profiles.  IIRC, the .6 uninstaller always kills the profiles directory, 
which is a very bad thing, but something we must deal with.  I propose 
having the .7 installer detect if it's being installed on top of .6, 
move the .6 profiles directory to the temp folder, run the .6 
uninstaller, install to the directory, and then copy the profiles back.  
Any suggestions or concerns would be very welcome.

Enjoy,

 Jeff

In 07rc1 layers seem to close themselves when you right-click on them.
Unless I'm having screwed setup here I think this is a bug. Layer should not
close on right-click. They should either display popup menu or do nothing
but definitely not close.

Also, enabling layers.catch causes error on KM exit every time. Disabling
the pref gives normal closing behaviour again.

s.

* sven vahar <sven@...> [2002-10-31, 06:41 +0200]:
> In 07rc1 layers seem to close themselves when you right-click on them.
> Unless I'm having screwed setup here I think this is a bug. Layer should not
> close on right-click. They should either display popup menu or do nothing
> but definitely not close.

You get a popup menu if you have one named LayerButtonPopup in
menus.cfg. Without such a menu you get the right-click to close
behavior (which I am pretty sure someone else asked for).

> Also, enabling layers.catch causes error on KM exit every time. Disabling
> the pref gives normal closing behaviour again.

I'll look at this. But could you please explain the "errors" you see.
(it's much easier to see the same as you if i know what to look for)

Thanks.
-- 
Ulf

* sven vahar <sven@...> [2002-10-31, 21:06 +0200]:
> * Ulf Erikson <ulferikson@...> [2002-10-31, 19:32 +0100]:
> > * sven vahar <sven@...> [2002-10-31, 06:41 +0200]:
> > > In 07rc1 layers seem to close themselves when you right-click on them.
> > > Unless I'm having screwed setup here I think this is a bug. Layer should not
> > > close on right-click. They should either display popup menu or do nothing
> > > but definitely not close.
> >
> > You get a popup menu if you have one named LayerButtonPopup in
> > menus.cfg. Without such a menu you get the right-click to close
> > behavior (which I am pretty sure someone else asked for).
>
> I'd disagree then. Close on right-click does not make any sense UI-wise. It
> goes against any well-established widget behaviours, at least in Windows.
> Right-click either provides additional information or extra features
> (context menus) or doubles left-click in behaviour (selects the object).
> Having it to perform destructive action is not nice at all when all other
> windows apps do not do so.

This is changed in CVS. Middle-click on a layers button will now close
a layer while right-clicking without having a LayersButtonPopup will
do nothing.

> > > Also, enabling layers.catch causes error on KM exit every time. Disabling
> > > the pref gives normal closing behaviour again.
> >
> > I'll look at this. But could you please explain the "errors" you see.
> > (it's much easier to see the same as you if i know what to look for)
>
> Literally, it says "k-meleon.exe has generated errors and will be closed by
> Windows. You will beed to restart the program." It does this on my two
> separate boxes, both w2k sp2.

This crash is fixed in CVS.

(in addition to these two issues I also addressed bug #247, which is
 about vanishing buttons, by splitting layers.width into layers.minWidth 
 and layers.maxWidth)

Thanks
-- 
Ulf

Newest layers.dll pulled off of http://kmeleon.freewebsites.com/ don't seem
to honour the width property. The one with 0.7 release does but newer one
ignores layer.width happily and uses default width.


s.

* sven vahar <sven@...> [2002-11-02, 08:09 +0200]:
> Newest layers.dll pulled off of http://kmeleon.freewebsites.com/ don't seem
> to honour the width property. The one with 0.7 release does but newer one
> ignores layer.width happily and uses default width.

Yes. These changes was intended for 0.7 (i see no point in keeping
backward compatibility for non-release versions), but it seems as if
Jeff never applied that patch.

There are two width preferences now:

* Ulf Erikson <ulferikson@...> [2002-10-31, 21:48 +0100]:
> (in addition to these two issues I also addressed bug #247, which is
>  about vanishing buttons, by splitting layers.width into layers.minWidth 
>  and layers.maxWidth)

-- 
Ulf

>>What is your "attempt to close the browser"?
>>The same as before?
>>http://www.geocrawler.com/mail/msg.php3?msg_id=9624950&list=9632
 
Sorry, yes, using the X in the upper right hand corner of the browser which I assumed most use.

>>When catch is true Window events are applied on layers. That is
>>WM_CLOSE will only close a layer. Use WM_QUIT to close the browser
>>and layers("openwindow") and layers("closewindow") to fine-tune.
 
You'll have to excuse my ignorance but I usually just copy and paste from your page. How do I assign WM_QUIT to be the function of the X located in the in the upper right corner of the browser? Or do I have to create another toolbar button for ID_APP_EXIT?

>>I suggested to split catch into catchOpen and catchClose once:
>>http://www.geocrawler.com/mail/msg.php3?msg_id=9386949&list=9632

Has that been implemented? If so, does it mean the following replacing "catch"? Therefore "X" closing the browser instead of just the layer?

user_pref("kmeleon.plugins.layers.catchClose", false);
user_pref("kmeleon.plugins.layers.catchOpen", true);
-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

* j s n j <jsnj@...> [2002-11-02, 13:47 -0500]:
> >>What is your "attempt to close the browser"?
>  
> Sorry, yes, using the X in the upper right hand corner of the
> browser which I assumed most use.

I'm afrad I can be rather lazy when it comes to decipher, what I find,
ambiguous bug-reports. I usually have a long enough list of things I
wish to improve anyway. Just be patient and I might understand you :)

> >>I suggested to split catch into catchOpen and catchClose once:
> >>http://www.geocrawler.com/mail/msg.php3?msg_id=9386949&list=9632
> 
> Has that been implemented? If so, does it mean the following
> replacing "catch"? Therefore "X" closing the browser instead of just
> the layer?
> 
> user_pref("kmeleon.plugins.layers.catchClose", false);
> user_pref("kmeleon.plugins.layers.catchOpen", true);

That would probably be the better setting for you, yes. But it is not
implemeneted yet as no one seemed to like the idea back then. I'll
look at adding it "soon".

But I still guess that this will not be enough for every situation..
-- 
Ulf

* Ulf Erikson <ulferikson@...> [2002-11-04, 17:20 +0100]:
> > >>I suggested to split catch into catchOpen and catchClose once:
> > >>http://www.geocrawler.com/mail/msg.php3?msg_id=9386949&list=9632
> > 
> > Has that been implemented? If so, does it mean the following
> > replacing "catch"? Therefore "X" closing the browser instead of just
> > the layer?
> > 
> > user_pref("kmeleon.plugins.layers.catchClose", false);
> > user_pref("kmeleon.plugins.layers.catchOpen", true);
> 
> That would probably be the better setting for you, yes. But it is not
> implemeneted yet as no one seemed to like the idea back then. I'll
> look at adding it "soon".

This is in CVS now. With layers.catch still valid with the meaning to
catch both open and close messages.

* Ulf Erikson <ulferikson@...> [2002-11-02, 10:23 +0100]:
> * sven vahar <sven@...> [2002-11-02, 08:09 +0200]:
> > Newest layers.dll pulled off of http://kmeleon.freewebsites.com/ don't seem
> > to honour the width property. The one with 0.7 release does but newer one
> > ignores layer.width happily and uses default width.
> 
> Yes. These changes was intended for 0.7 (i see no point in keeping
> backward compatibility for non-release versions), but it seems as if
> Jeff never applied that patch.

Since 0.7 went out with a single width preference I readded the old
width (with it's old meaning) for the time being.

> There are two width preferences now:
> 
> * Ulf Erikson <ulferikson@...> [2002-10-31, 21:48 +0100]:
> > (in addition to these two issues I also addressed bug #247, which is
> >  about vanishing buttons, by splitting layers.width into layers.minWidth 
> >  and layers.maxWidth)

Changed layers.minWidth and layers.maxWidth to operate on millimeters
instead of pixels.

-- 
Ulf