: K-Meleon Forum
General discussion about K-Meleon.
A word you have used in your post: "<br", has been banned from use. Please use a different word or contact the forum administrators.
[quote=guenter] [quote=deadlock] fix your Console and Console2? It's the same problem and results in CrashBadaboum (as defined in sources). Look for viewSource.xul in chrome/embed.jar and change this: <browser id='content' type='content-primary' <browser id='content' type='chrome' Guenter has the patched chrome for KM 1.6b2 on his site. -- There is a problem with 'mozilla's update plugins site', if it fails to detect its own child. And I can't test Camino with GRE 1.9.1 which should contain all required changes and may even solve Bug 1288. If 'other sites' are affected, you're for sure the first one who finds out. :cool: I will try to get working typeaheadfind with my profile. It never worked for me and crashes KM in Fred's latest. Could be caused by too many URLs.[/quote] For console ViewSource I like better an old suggestion from a mail by You. Repalcing in Console2.xml openDialog("chrome://global/content/viewSource.xul", "_blank", "all,dialog=no", this.getAttribute("href"), null, null, this.getAttribute("line")); With the following that calls a K-Meleon native view-source window. window.open( "view-source:" + this.getAttribute("href") + "?" + this.getAttribute("line") ); The drawback is that K-Meleon's native view-source has not context-menu or other menu and does not accept "line" as parameter. I wonder whether that drawbacks can be fixed. IMHO generally replacing with: <browser id='content' type='chrome' can be a security risk? deadlock has put a patched chrome/embed.jar to http://dhost.info/kmeleonskins/ Not all know where guenter stores K-Meleon stuff. :D Working typeaheadfind came with version K-Meleon 1.0 AFAIK. Make sure no ancient profile entries from before that are present.[/quote]
K-Meleon forum is powered by