simply check: "at startup display a blank page".
And if I want a direct link to "about:config"? Do I just check "at startup display the config page"? Even if there was such an option, what if I wanted both
What about a link to just "about:"? Or have you never seen that page?
The "about:" namespace may not be quite as vast as "http:", but it is not trivial either.
Besides, think, why do you need a "default handler" for "http" at all? All it does is determine which browser opens links from your harddrive, and, by your argument, they are not needed.
It's incredible with what you come up. But obviously you didn't bother to read me:
Since nothing at the opened browser will be in any way different from having it opened like everyone else does, by a normal program link or a real document link.
Okay, what is your
definition for a "document link" exactly?
Explain to me how it works for http, in exactly
why it shouldn't work for "about:blank" either.
If it is just a link to an html on the harddrive, then it still doesn't work for, you know, web pages.
If it is a link file, like "http://"
;, then why shouldn't it work for "about:" as well? Why should a file, in the same file format, sometimes open in K-Meleon, and sometimes not? And mind you, that a valid "http:" link which does work in K-Meleon, if you right click, click on "Properties", and replace "http:" with "about:", would no longer open with K-Meleon.
But what you are complaining about, is that it's a great deficit for you that the browser "only" has a default handler to open DOCUMENTS, but that there's no handler to open a desktop item "about:blank", which means NOTHING, just the browser itself and an empty page.
And what is an http link if not "NOTHING" but opening the browser and inputting the link? What is the difference, exactly, between an http link and an about link? Both are protocols which K-Meleon supports, and must therefore have the option to trap. Or alternately, if you don't believe in protocol trapping, then neither should be trapped.
But one yes and one no is just inconsistent behavior. It is the same file type, after all (.URL, a text file containing a link). It's like a movie player that opens AVIs with Xvid, but somehow lets Windows Media Player open AVIs with DivX (I don't think that's even possible, actually, maybe with DDE). Would that make sense to you?
And this everyone else does by adding the program link on desktop
No, some people add the browser's program link to open their homepage, not "about:blank". These two can be configured
to be the same, but they can also be used as two different things (configure the browser to open with a homepage, but still have a link to "about:blank"). Just because you
can't think of a reason someone would want to do this, doesn't mean it shouldn't be supported.
Incidentally, opening my, now working, "about:blank", if the program is still open, opens a new tab, whereas the program link opens a new window. So these are not equivalent even if you configure them.
you could still just create an empty file on the desktop with an ending ".html", there's absolutely no need to have that start with that completely unusual "about:"
Again, this would only work for emulating
, and this still wouldn't be the same, because it will have different load times, disk activity, file type, and text in the URL bar. Not to mention it would show the ".html" extension, whereas ".url" is hidden by default (even if setting extensions to "show"). Oh, you'd better not suggest changing the OS "hide extensions" settings next, a program that forces you to change OS settings is just wrong.
Or, wait, I know, maybe I should create an html with a meta tag which redirects to "about:blank", place it somewhere on my harddrive, then place a shortcut (".lnk", not ".url") to that file? Yeah, that's not overkill or over-complicated at all. Oh, no wait, it would still have the html in the back history. Yup, no go.
Also, there's the fact that it gives you a big "Do not touch this" warning when you open it.
LOL! That's for completely clueless users, without any experience with other browsers either, but you're certainly not pretending that this would scare people like YOU off ;-) (nor me of course
1. No, no it isn't. The wrong setting in "about:config" could make your browser to crash. I've crashed 'Fox this way before. And that's the good version, an incorrect setting could also make you abuse your network connection and cache, which you would only notice when your ISP sends you an angry letter, or when you realize your every post is a double-post. The settings there are mostly for people who have already had a look at the source code and know precisely what they're doing.
2. Who said that didn't scare me off? When I found it in the menu and saw the big message, I read it as it was displayed, as a "Do not enter!", so I didn't enter. I only finally entered when I saw I have no choice, and I'm still crossing my fingers that there wouldn't be any nasty side effects (like my bookmarks becoming corrupted or something).
3. Are we now assuming that the average K-Meleon user is at "developer" level? Do I even have to explain what's wrong with that? Or are we just assuming that every user who wants to disable double-click behavior is a developer? Maybe it's just me, but I don't see how one would imply the other.
If you like open bookmarks at last and links at next you can make a macro to open links that switch the pref kmeleon.tabs.onOpenOption between values 0 and 1.
I can set it backwards, using the macro behavior on bookmarks. But, again, I can't set it for opening ".url" or ".html" files, nor for the behavior of clicking on the tab bar.
So this issue is, unfortunately, without a workaround. Unless I want to try and compile K-Meleon myself (Although I don't think that counts as a "workaround").
P.S. Do any developers even read this forum? Should I post this in the SF tracker instead?