Main changes since 75b1u1:

- Reverted something that could be the cause of the process staying after exit
- Fixed high CPU usage with animation in multiple tabs
- Fixed RemoveButton crash and other issues
- Fixed Certificate Viewer crash
- New macros functions for toolbar (not much tested)

addtoolbar(name)
addbutton(toolbarname, command, menu)
removebutton(toolbarname, command)
setcmdicon(name, image, width, height)  // width, height optional, for multi icon image

Download 7z

EDIT: Update 1



Edited 1 time(s). Last edit at 01/26/2015 08:40PM by Dorian.

I began with the obvious, the visual aspect:

- you can't change skins in 2k nor XP (skins not enumerated in the drop down list)
- broken support for older skins in 2k and XP; in 2k not only the icons aren't correctly cropped, but added the black background, what it hadn't previously:


- the locked toolbars, when unlocked, can't be dragged (reported in the b1 thread)
- button status not synched unless mouse or key action.


BTW, do I report this things in the bug tracker? I usually do this in the thread but you might miss them.



Edited 1 time(s). Last edit at 01/13/2015 08:05PM by JohnHell.

Still hanging the process.

With the Flickr procedure I talked in the other thread I'm having the expected hang results.

Even others are reporting happening in Windows 7, as I only can reproduce it in Windows 2000. I end requesting for a fix for it. For me hasn't much sense.

Erratic history funcionality.

- clicking does nothing
- righ clicking and choosing options (now greyed out if not using tabs) does nothing
- doesn't update when changing viewing options

At this moment, switching back to beta 1 update 1. I have too much dependency on history :_(

The Button Mneu State problem where a button stays depessed on the toolbar selected is worse in K-Meleon 75.0 Beta 2 than it was in K-Meleon 75.0 Beta 1.

Now in under Tools Privacy in K-Meleon 75.0 Beta 2, The Button States prevents checksboxes from being added on "block flash","block java", and "block popups"

I'm still having the black page issue. Its occurring for me when I try to view http://www.cnn.com. My graphics card is a NVIDIA GeForce 9400 GT with hardware acceleration disabled and the Classic Skin being used to skin the OS.



Edited 2 time(s). Last edit at 01/14/2015 04:51PM by Zero3K.

Quote
JohnHell
- you can't change skins in 2k nor XP (skins not enumerated in the drop down list)

Maybe remove startupcache. I forgot to delete it automatically with this release.

Quote
JohnHell
- the locked toolbars, when unlocked, can't be dragged (reported in the b1 thread)

With both 2k and XP ?

Quote
JohnHell
BTW, do I report this things in the bug tracker? I usually do this in the thread but you might miss them.

Don't for now.

Quote
Zero3K
I'm still having the black page issue. Its occurring for me when I try to view http://www.cnn.com. My graphics card is a NVIDIA GeForce 9400 GT with hardware acceleration disabled and the Classic Skin being used to skin the OS.

It happens to me too after viewing a lot of images.

Quote

www.cnn.com could not be found. Please check the name and try again.

Normal or I have dns issue ?

Regarding the viewing of http://www.cnn.com/, I don't seem to have a problem. I see the U.S. edition. Does the edition matter. I am on win 7 (32 bit) with whatever graphics that came on my motherboard.

Quote
Dorian

Quote
JohnHell
- you can't change skins in 2k nor XP (skins not enumerated in the drop down list)

Maybe remove startupcache. I forgot to delete it automatically with this release.

Even removed. I forgot the first time, I admit (I almost forgot with every update LOL), but I tested with it removed before I posted the above :/

Even with a new profile, where there is no startupcache, just in case.

Also the locales haven't a drop down list. At first thought, as I remove to save space, I thought it was that, but, no, they don't appear after re-add the locales folder and using a new profile.

This testing most in XP virtual machine, the same, just in case 2k was tricking me.

Quote
Dorian

Quote
JohnHell
- the locked toolbars, when unlocked, can't be dragged (reported in the b1 thread)

With both 2k and XP ?

Yes, on both.

And I'd say is worst than in b1u1 as you can't with, tiny mouse movements, be able to change the mouse to drag. You need to restart to be able to drag the toolbars again after unlock :/

Quote
Dorian

Quote
JohnHell
BTW, do I report this things in the bug tracker? I usually do this in the thread but you might miss them.

Don't for now.

Ok.


About the black page Zero3k and you are saying, is curious, because after I switched from 74 to 75, that I forgot to set layers.accelaration.disabled to true, I don't have black pages on windows 2000, neither in XP.

It's one of those x-files.


OFF-TOPIC
Anyway, I decided yesterday to go beyond and I'm using now version 74, not because of the beta, just for the javascript bug (that I didn't report yet as I was waiting for further datails in their Firefox support pages) that don't block javascript when javascript is toggled. It was driving me crazy and it is a very huge security issue, for my eyes

No more beta testing for now



Edited 1 time(s). Last edit at 01/14/2015 07:28PM by JohnHell.

Quote

Quote
Dorian

Quote
JohnHell
- you can't change skins in 2k nor XP (skins not enumerated in the drop down list)


Maybe remove startupcache. I forgot to delete it automatically with this release.


Even removed. I forgot the first time, I admit (I almost forgot with every update LOL), but I tested with it removed before I posted the above :/

Even with a new profile, where there is no startupcache, just in case.

Also the locales haven't a drop down list. At first thought, as I remove to save space, I thought it was that, but, no, they don't appear after re-add the locales folder and using a new profile.

This testing most in XP virtual machine, the same, just in case 2k was tricking me.

I don't seem to have problem moving toolbars using Win 7.

I also now see the image change on a macro built button.

I think there is a problem keeping toolbars position through a restart when the privacy bar is shown, but it seems to go away if I hide the privacy bar.

Using preferences for apparence > general doesn't work. The only item on that panel which works is the window title.

Does beta 2 no longer require the chrome.manifest file in the root which has this info "binary-component k-meleon.exe"?

Quote
Dorian

Quote
Zero3K
I'm still having the black page issue. Its occurring for me when I try to view http://www.cnn.com. My graphics card is a NVIDIA GeForce 9400 GT with hardware acceleration disabled and the Classic Skin being used to skin the OS.

It happens to me too after viewing a lot of images.

Quote

www.cnn.com could not be found. Please check the name and try again.

Normal or I have dns issue ?

DNS Issue. Try using 4.2.2.1 and 4.2.2.2 as the dns servers assigned to your connection.

I've unpacked the b2 over b1u1. It always worked this way till now.
Under "Appearence" no skin, no language to select.
Images for PrivacyBar buttons have vanished. Same for the image of an extra toolbar button. All the buttons are still working at least.
Images for forward and back buttons are empty as well. Only image I have displayed correctly is that of the bookmarks toolbar.
Win7 x64.



Edited 1 time(s). Last edit at 01/14/2015 11:00PM by Yogi.

I can not change the language on K-Meleon 75b2.

http://kmeleonbrowser.org/forum/read.php?4,131640



Edited 1 time(s). Last edit at 01/14/2015 11:01PM by c-sanchez.

Quote
Yogi
Images for PrivacyBar buttons have vanished. Same for the image of an extra toolbar button. All the buttons are still working at least.

What skin are you using for test?

 



Edited 1 time(s). Last edit at 03/21/2016 12:10PM by adodupan.

Quote
JamesD
What skin are you using for test?

The skin I'm using all the time - Klassic. It's slightly modified but this shouldn't have any impact. The PrivBar is shorter. There are only items on it which I use and there are only images without text - makes the buttons shorter (16x16). It workes fine in KM-74 and worked fine in KM-75 b1u1 as well.
I've checked now the original Klassic skin shipped with KM-b2 and the PrivBar displays here correct but all other toolbars are fu**ed up.

A last try with a fresh new install of KM-b2.
Default skin - all toolbars are displaying correct.
First attempt to customize the browser by switching to the Klassic skin shipped with KM failed. Not possible from tha GUI, at least.
Giving up for now and waiting till basic glitches will get sorted out.

Quote
Yogi
First attempt to customize the browser by switching to the Klassic skin shipped with KM failed. Not possible from tha GUI, at least.

Yes, the appearance > general panel is not working. You can change skins by adding or changing the following line in prefs.js while KM is not running.

user_pref("kmeleon.general.skinsCurrent", "MyKlassic2");

Ok, looks like I've uploaded the wrong package. Download it again.
This will fix the preferences issue.

Quote
Dorian
Ok, looks like I've uploaded the wrong package. Download it again.
This will fix the preferences issue.

What about the "black page" issue?

Quote
Dorian
Ok, looks like I've uploaded the wrong package. Download it again.
This will fix the preferences issue.

Very good. I extracted the new version over existing KM75b2 and both preferences and history are fixed.

Can you fix the protocol mismatch problem in Console2? Error reports that "chrome" and "file" are not accepted when I try to display the source of an error in omni or kmm file.

The missing Klassic Skin icons from K-Meleon 75.0 Beta 2 will be seen if one thing is done.

If the k-meleon.exe file from K-Meleon 75.0 Beta 1 is used on K-Meleon 75.0 Beta 2 then icons for the Klassic Skin are visible.

Good to know history was fixed. Note: I haven't tested myself.

As we are with fix proposals as the kmm error when trying to display the file with the error, that I agree with JamesD

I suggest to change the files c2version.css and richlistbox.css, that are from the console2 skin in k-meleon browser\omni.ja as follows, as they bring a deprecated attribute error since a few versions back that remove the -moz- preffix:

Quote
c2version.css

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";

.console-row[type="error"] description {
	white-space: pre-wrap;
}

/* ........ message rows .............. */

.console-row[type="message"] description {
	white-space: pre-wrap;
}

#ConsoleBox:focus > .console-row[current="true"] {
	outline-offset: -2px;
}

Quote
richlistbox.css after license and description

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul";

richlistbox {
  margin: 2px 4px;
  background-color: -moz-Field;
  color: -moz-FieldText;
  -moz-box-orient: vertical;
}

richlistbox[disabled="true"] {
  color: GrayText;
}

richlistitem[selected="true"] {
  background-color: -moz-Dialog;
  color: -moz-DialogText;
}

richlistbox:focus > richlistitem[selected="true"] {
  background-color: Highlight;
  color: HighlightText;
}

richlistbox[seltype="multiple"]:focus > richlistitem[current="true"] {
  outline: 1px dotted Highlight;
  
  outline-offset: -1px;
}

richlistbox[seltype="multiple"]:focus > richlistitem[current="true"][selected="true"] {
  outline: 1px dotted #F3D982; /* TODO: find a suitable system color */
}

About the inability to stop script execution on-the-fly, end of the story:

http://kmeleonbrowser.org/forum/read.php?12,131017,131673#msg-131673

 



Edited 2 time(s). Last edit at 03/21/2016 12:10PM by adodupan.

Quote
adodupan
It is not possible to add a new menu to 'Main'

const JSB = Components.classes['@kmeleon/jsbridge;1'].getService(Components.interfaces.nsIJSBridge);
JSB.SetMenu('Main', JSB.MENU_POPUP, '&JSBridge Test', '', '');
JSB.SetMenu('&JSBridge Test', JSB.MENU_COMMAND, 'Test About', 'ID_APP_ABOUT', '');

If you open a new windows, you'll see that it worked. Because of the way the rebar plugin is currently working, it can't be fixed. It must be done before windows creation.

Quote
adodupan
You should make it possible to load kplugins inside addons,
but do not do this - 'plugins must be loaded without having access to the preferences',
you just ignore bootstrap.

Why would you need a kplugin in an addon?

Quote
adodupan
Also, icons will not appear in the menu.
If you want to use new functions, this bug needs to be fixed, it's ugly.

Add at the end of the menu:

JSB.SetMenu(TEST.menuName, JSB.MENU_PLUGIN, 'bmpmenu()', 1, '');

This should do the trick until bmpmenu is replaced by mfc features.



Edited 1 time(s). Last edit at 01/19/2015 06:53PM by Dorian.

 



Edited 1 time(s). Last edit at 03/21/2016 12:11PM by adodupan.

Quote
adodupan
It's done.
About your kplugins question, is it your sexual life in crisis, or what
I have already replied to you about that.
Ok, one more time, perhaps this argument is good enough.
Do you plan to disable kplugins in km - answer is no.
So, you should make it possible to load kplugins inside addons.

I do not tthink adding kplugins to addons is a good idea it could cuase break or cause problems for other parts of K-Meleon 75.0 Beta 2

It could also cause problems for Windows when looking Windpws DLLs that kplugins need to function.



Edited 1 time(s). Last edit at 01/21/2015 09:27AM by George_Hall.

Indeed, my sexual life suffer from my work on kmeleon, therefore I should stop.