Development :  K-Meleon Forum
K-Meleon development related discussions. 
Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Robert
Date: November 03, 2002 08:58PM

K-meleon does not support link-tags, for example:
<link rel="next" href="foo.htm" title="next page">

I know, that no many browsers support these tags, but it is a chicken and egg problem :-)

Mozilla 0.9, 1.1 and 1.2 have a site-navigation-bar and I think, k-meleon should have this too.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Andrew
Date: November 04, 2002 12:01PM

Robert,

This is an RFE. Hopefully, it can be worked into a future release. However, you are only the second person to ask for it.

http://kmeleon.sourceforge.net/bugs/viewbug.php?bugid=135

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Andy Korvemaker
Date: November 05, 2002 02:36AM

Eventually I'd like to see it also. It's not critical, but I think it could be a really useful feature.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: pandy
Date: November 16, 2002 03:57PM

Well, now there are three. :-)

The lack of support for LINK is one of the things that are holding easily customizable CSS sites back (alternate stylesheets). Moz supports it and with it's newly released 7beta Opera also does.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: sven
Date: November 16, 2002 06:20PM

Yes and no. Both <link rel="stylesheet" ... > and <link rel="alternate stylesheet" ... > are supported.

It's the option to switch between alternate stylesheets thats missing.

But that's entirely different thing from supporting link-bar with additional navigational features it can give.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Stefan
Date: November 16, 2002 06:49PM

It should be easy enough to write a macro to enable the SS switching though.

Also, my vote would be for such a macro functionality to be included by default in the next release of K-Mel, becuse the lack of such a functionallity is actually a breach vs the CSS spec for a CSS capable browser.

Perhaps some of the skilled coders around here would like to take a shot at implementing this in a nice way for K-Mel smiling smiley

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: pandy
Date: November 17, 2002 06:25AM

Sorry for not expressing myself clearly enough. Yes, of course I meant the ability to switch between them :-/

The link bars used in Moz and now Opera7 are also great. It doesn't need to be a bar IMO but some way to navigate links embedded in LINK elements would be nice.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: C
Date: November 24, 2002 01:57PM

Yes, if there is anything thats on my wish list for the next KM its full support for HTML 2.0 ^^

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: sven
Date: November 24, 2002 02:39PM

HTML 2.0 contanins some deprecated elements which doesn't make sense to support anymore. When was last time you actually used or saw ISINDEX or MENU. Some are outright obsolete like XMP and LISTING.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: David Johnson
Date: April 02, 2003 03:05PM

Are we talking about XHTML 2.0 here? Last time I looked HTML was at 4.01, and XHTML 1.0 was released, but 2.0 was only a working draft.

Or is XHTML 2.0 now a full recommendation?

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Andy Korvemaker
Date: April 03, 2003 05:02AM

Nope, we're talking about plaing old HTML 2.0. The question was orginally about the <link> tag that first appeared (I think) in HTML 2.0 and still exists today in the newer standards (HTML 4.01, XHTML 1.0). Pretty much it was a feature request to have some method of accessing the information in the <link> tag, such as Mozilla and Opera now do.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Andy Korvemaker
Date: April 03, 2003 05:03AM

Nope, we're talking about plain old HTML 2.0. The question was orginally about the <link> tag that first appeared (I think) in HTML 2.0 and still exists today in the newer standards (HTML 4.01, XHTML 1.0). Pretty much it was a feature request to have some method of accessing the information in the <link> tag, such as Mozilla and Opera now do.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Andy Korvemaker
Date: April 03, 2003 05:04AM

oops. sorry about the dupe...

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: Ronald Clifford Buckman
Date: June 29, 2003 01:21AM

As a K-Meleon 0.7.1 user, I also would like to see K-Meleon fully support the <link> tag.

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: MonkeeSage
Date: June 29, 2003 02:15AM

What exactly are you trying to do?

If you want to access attributes of a link tag in Mozilla (and thus KM), you'd do something like this:

<!-- the link to manipulate / read from -->
<link id="thislink" src="#" attribute1="some value" value="Test Link" title="Test Link">Test Link</link>

<!-- the script to do the reading or manipulating -->
<script type="application/x-javascript; version=1.5">
   const theLink =  document.getElementById("thislink");

   function readLinkAtt() {
        alert(theLink.getAttribute("attribute1"));
        // or, like this
        // alert(theLink.attribute1);
   }

   function writeLinkAtt() {
        theLink.setAttribute("attribute1", "some other value");
        // or, like this
        // theLink.setAttribute.attribute1 = "some other value";
   }
</script>


Shelumi`El
Jordan

S.D.G

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: MonkeeSage
Date: June 29, 2003 02:27AM

NM, I see the problem...doesn't work in Firebird either...looks like the Mozilla implementation of the <link> spec is still in transition and is not fully implemented. I made a test page:

<!DOCTYPE&nbsp;HTML&nbsp;PUBLIC&nbsp;"-//W3C//DTD&nbsp;HTML&nbsp;4.01&nbsp;Transitional//EN">
<html>
<head>
<title>untitled&nbsp;page</title>
<meta&nbsp;http-equiv="content-type"&nbsp;content="text/html;&nbsp;charset=utf-8">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<!--&nbsp;the&nbsp;script&nbsp;to&nbsp;do&nbsp;the&nbsp;reading&nbsp;or&nbsp;manipulating&nbsp;-->
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<script&nbsp;type="application/x-javascript;&nbsp;version=1.5">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;const&nbsp;theLink&nbsp;=&nbsp;&nbsp;document.getElementById("thislink");

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;readLinkAtt()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;alert(theLink.getAttribute("title"));
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;or,&nbsp;like&nbsp;this
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;alert(theLink.title);
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;writeLinkAtt()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;theLink.setAttribute("title",&nbsp;"some&nbsp;other&nbsp;value");
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;or,&nbsp;like&nbsp;this
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;theLink.setAttribute.title&nbsp;=&nbsp;"some&nbsp;other&nbsp;value";
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;defer_link()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;readLinkAtt();&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;writeLinkAtt();
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;readLinkAtt();&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</script>
</head>
<body&nbsp;onload="setTimeout('defer_link()',600);">
<!--&nbsp;the&nbsp;link&nbsp;to&nbsp;manipulate&nbsp;/&nbsp;read&nbsp;from&nbsp;-->
&nbsp;&nbsp;&nbsp;<link&nbsp;rel="Index"&nbsp;type="text/html"&nbsp;&nbsp;href="#"&nbsp;title="Test&nbsp;Link">Test&nbsp;Link</link>
</body>
</html>

Doesn't work in either browser...the link is just text and the js breaks.


Shelumi`El
Jordan

S.D.G

Options: ReplyQuote
Re: Why k-meleon doesn't support HTML 2.0 completely?
Posted by: MonkeeSage
Date: June 29, 2003 02:32AM

Ooops posted the wrong one:


<!DOCTYPE&nbsp;HTML&nbsp;PUBLIC&nbsp;"-//W3C//DTD&nbsp;HTML&nbsp;4.01&nbsp;Transitional//EN">
<html>
<head>
<title>untitled&nbsp;page</title>
<meta&nbsp;http-equiv="content-type"&nbsp;content="text/html;&nbsp;charset=utf-8">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<!--&nbsp;the&nbsp;script&nbsp;to&nbsp;do&nbsp;the&nbsp;reading&nbsp;or&nbsp;manipulating&nbsp;-->
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<script&nbsp;type="text/javascript;&nbsp;version=1.5">
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;const&nbsp;theLink&nbsp;=&nbsp;&nbsp;document.getElementById("thislink");

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;readLinkAtt()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;alert(theLink.getAttribute("title"));
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;or,&nbsp;like&nbsp;this
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;alert(theLink.title);
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;writeLinkAtt()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;theLink.setAttribute("title",&nbsp;"some&nbsp;other&nbsp;value");
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;//&nbsp;or,&nbsp;like&nbsp;this
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;theLink.setAttribute.title&nbsp;=&nbsp;"some&nbsp;other&nbsp;value";
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;preDeferLink()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;setTimeout('preDeferLink()',600);
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;function&nbsp;deferLink()&nbsp;{
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;readLinkAtt();&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;writeLinkAtt();
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;readLinkAtt();&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</script>
</head>
<body&nbsp;onload="preDeferLink();">
<!--&nbsp;the&nbsp;link&nbsp;to&nbsp;manipulate&nbsp;/&nbsp;read&nbsp;from&nbsp;-->
&nbsp;&nbsp;&nbsp;<link&nbsp;rel="Index"&nbsp;type="text/html"&nbsp;id="thislink"&nbsp;href="#"&nbsp;title="Test&nbsp;Link">Test&nbsp;Link</link>
</body>
</html>

Options: ReplyQuote


K-Meleon forum is powered by Phorum.