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.
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
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.
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.
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.
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.
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>
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: