Html Component Question

  • Thread starter Thread starter WStoreyII
  • Start date Start date
W

WStoreyII

I dont think that it really matters, but just for my own reference?

I found a calendar component tutorial online for html components.
in this component the tag for a script was <SCRIPT
LANGUAGE="JavaScript"></SCRIPT>

here is the problem when i tried this in my own component it would not work
until i used the tag like this
<SCRIPT TYPE="text/javascript"></SCRIPT>

i could understand why this would not work on different browsers but the
calendar project works just fine on my computer so
i dont understand why it did nto work in my project. Is this stuff case
sensitive????

Thanks for the help

WStoreyII
 
WStoreyII said:
I dont think that it really matters, but just for my own reference?

I found a calendar component tutorial online for html components.
in this component the tag for a script was <SCRIPT
LANGUAGE="JavaScript"></SCRIPT>
Click to expand...

The language attribute is deprecated.
here is the problem when i tried this in my own component it would not work
until i used the tag like this
<SCRIPT TYPE="text/javascript"></SCRIPT>
Click to expand...

The type attribute is now required for the script element.
i could understand why this would not work on different browsers but the
calendar project works just fine on my computer so
i dont understand why it did nto work in my project.
Click to expand...

Different error correction?
Is this stuff case
sensitive????
Click to expand...

HTML is not case sensitive.
 
then how come it worked when i loaded the calendar example and not on mine?

ill send the demo if you wish

wstoreyii
 
Bits of it are. Compare <strong>Hello</strong> with
Click to expand...
<strong>HELLO</strong>.
</nitpick> :-)

<pedantic>
HTML is not case sensitive.

The content whose structure the HTML describes may be case sensitive in
certain languages (such as English) where there is such a thing as case
(unlike other languages, such as most South East Asian ones (and especially
Chinese and its derivatives (where there are not even any "letters")) where
there is no concept corresponding to upper and lower case) but the HTML bit
(the stuff inside the start and end tags, the attributes and so on) is not,
with the exception of the value of some of the attributes, such as in the
case of href="example.com" where "example.com" may or may not be case
sensitive depending on which operating system the server is running, however
one could actually argue that the "example.com" bit is actually part of the
content, even though it does not appear as content within an element but
rather as the value of an attribute.
</pedantic>
 
rf said:
<strong>HELLO</strong>.
</nitpick> :-)

<pedantic> // What is Pedantic???????
HTML is not case sensitive.

The content whose structure the HTML describes may be case sensitive in
certain languages (such as English) where there is such a thing as case
(unlike other languages, such as most South East Asian ones (and especially
Chinese and its derivatives (where there are not even any "letters")) where
there is no concept corresponding to upper and lower case) but the HTML bit
(the stuff inside the start and end tags, the attributes and so on) is not,
with the exception of the value of some of the attributes, such as in the
case of href="example.com" where "example.com" may or may not be case
sensitive depending on which operating system the server is running, however
one could actually argue that the "example.com" bit is actually part of the
content, even though it does not appear as content within an element but
rather as the value of an attribute.
</pedantic>
Click to expand...
 
WStoreyII said:
then how come it worked when i loaded the calendar example and not on mine?

ill send the demo if you wish
Click to expand...

Er, send it where?

Provide a link to the demo and a link to your implementation.
 
rf said:
<pedantic>
The content whose structure the HTML describes may be case sensitive in
certain languages (such as English) where there is such a thing as case
(unlike other languages, such as most South East Asian ones (and especially
Chinese and its derivatives (where there are not even any "letters")) where
there is no concept corresponding to upper and lower case) but the HTML bit
(the stuff inside the start and end tags, the attributes and so on) is not,
with the exception of the value of some of the attributes, such as in the
case of href="example.com" where "example.com" may or may not be case
sensitive depending on which operating system the server is running, however
one could actually argue that the "example.com" bit is actually part of the
content, even though it does not appear as content within an element but
rather as the value of an attribute.
</pedantic>
Click to expand...

Wow, that's one long sentence!

<nitpick>
Whether a link is case-sensitive may depend on operating system, but it
doesn't have to. A server can just as easily be configured to show the
same page for every URL, or show a different one based on the first
letter of the file name and nothing else; there's no requirment to map
URLs on to real files, although that's normally done.
</nitpick>
 
Leif K-Brooks said:
Wow, that's one long sentence!

<nitpick>
Whether a link is case-sensitive may depend on operating system, but it
doesn't have to. A server can just as easily be configured to show the
same page for every URL, or show a different one based on the first
letter of the file name and nothing else; there's no requirment to map
URLs on to real files, although that's normally done.
</nitpick>
Click to expand...

True.
 
rf said:
value of some of the attributes, such as in the case of
href="example.com" where "example.com" may or may not be case
sensitive depending on which operating system the server is running
Click to expand...

<nitpick>
The hostname portion of a url should never be case-sensitive.
That is, http://WwW.SiteNAme.CoM/ should work regardless of case or server
OS.
What is case-sensitive depending on OS is the filename portion, meaning
everything that comes after the single slash.
</nipick>
 
Matt Kruse said:
<nitpick>
The hostname portion of a url should never be case-sensitive.
That is, http://WwW.SiteNAme.CoM/ should work regardless of case or server
OS.
What is case-sensitive depending on OS is the filename portion, meaning
everything that comes after the single slash.
</nipick>
Click to expand...

<nitpick depth="2">
href="example.com" refers to the local file 'example.com', not the
host 'example.com' and so may be case-sensitive.
</nitpick>
 
rf said:
<strong>HELLO</strong>.
</nitpick> :-)

<pedantic>
HTML is not case sensitive.

The content whose structure the HTML describes may be case sensitive in
certain languages (such as English) where there is such a thing as case
(unlike other languages, such as most South East Asian ones (and especially
Chinese and its derivatives (where there are not even any "letters")) where
there is no concept corresponding to upper and lower case) but the HTML bit
(the stuff inside the start and end tags, the attributes and so on) is not,
with the exception of the value of some of the attributes, such as in the
case of href="example.com" where "example.com" may or may not be case
Click to expand...

Actually, to nit-pick even more: example.com isn't case-sensitive either.
Hostnames/domains are not case-sensitive. You get to the same site with:

www.yahoo.com, Www.Yahoo.Com or WWW.YAHOO.COM

The part that comes after the hostname/domain can be case-sensitive, but does
not necessarily have to be, depending on server configuration.
sensitive depending on which operating system the server is running, however
one could actually argue that the "example.com" bit is actually part of the
content, even though it does not appear as content within an element but
rather as the value of an attribute.
</pedantic>
Click to expand...

I would argue that the HREF attribute is neither content nor HTML. It is a value
assigned to the HREF attribute and as such obeys it's own syntax rules as
defined by the W3C: <url:
http://www.w3.org/TR/REC-html40/struct/links.html#adef-href />

A "uri" is defined as: <url: http://www.w3.org/TR/REC-html40/types.html#type-uri
/>

--
| Grant Wagner <[email protected]>

* Client-side Javascript and Netscape 4 DOM Reference available at:
*
http://devedge.netscape.com/library/manuals/2000/javascript/1.3/reference/frames.html

* Internet Explorer DOM Reference available at:
*
http://msdn.microsoft.com/workshop/author/dhtml/reference/dhtml_reference_entry.asp

* Netscape 6/7 DOM Reference available at:
* http://www.mozilla.org/docs/dom/domref/
* Tips for upgrading JavaScript for Netscape 7 / Mozilla
* http://www.mozilla.org/docs/web-developer/upgrade_2.html
 
rf said:
HTML is not case sensitive.
Click to expand...

That is an unfortunate but persistent simplification, not to say
misnomer. The issue is substitution, not sensitivity.

E.g., to refer to an instance of the element type 'div' in a parsed
HTML document instance set you'd need to address 'DIV', not 'div'
(forget the source, Luke). For attribute values the situation is even
more error-prone, since a lot of attribute values in HTML are declared
to be CDATA and case folding isn't applied (as opposed to all other
types).
 
Grant said:
Actually, to nit-pick even more: example.com isn't case-sensitive either.
Hostnames/domains are not case-sensitive.
Click to expand...

But "example.com" is a file name, not a domain name. It happens to
resemble a domain name, yes, but it has no protocol segment, so it's
interpreted as a file name by a browser with a quarter of a brain.
 
Back
Top