messagebox in asp.net? how?

M

Mark Rae

That's your opinion and I happen to think it's wrong.
Likewise.

HTML or XHTML have Transitional "flavors" that are, in fact, W3C
standards. There is absolutley nothing wrong with using them.
Click to expand...

Indeed. Which is why if you write something like <script
language="javascript" /> and set your page's target schema for validation to
"XHTML 1.0 Transitional" (which is what you seem to be suggesting as the
right thing to to), you will get a squiggly red line under the word "script"
which, when you hover over it, will tell you that this is not valid XHTML
1.0 Transitional code...
The FONT tag with the FACE, SIZE, COLOR attributes just for starters, but
since it uses these all over the place, they are a perfect example. Many
of the other deprecated tags/and attributes are used widely by VS.NET, MS
FrontPage and non-MS editors. Oh and yes, the the LANGUAGE attribute for
the SCRIPT tag is produced when you tell VS .NET to insert a server script
block into your HTML (and it doesn't even put the TYPE="text/javascript"
in there either).
Click to expand...

Oh blimey! What target schema are you validating against...???
 
S

Scott M.

Inline...


Mark Rae said:
Indeed. Which is why if you write something like <script
language="javascript" /> and set your page's target schema for validation
to "XHTML 1.0 Transitional" (which is what you seem to be suggesting as
the right thing to to), you will get a squiggly red line under the word
"script" which, when you hover over it, will tell you that this is not
valid XHTML 1.0 Transitional code...
Click to expand...

HTML and/or XHTML Transitional Recommendations don't indicate that the
LANGUAGE attribute is incorrect, they state that you must have the TYPE
attribute. For most of my purposes, I use both since not all clients are
new enough to understand TYPE, but all will understand LANGUAGE.
Oh blimey! What target schema are you validating against...???
Click to expand...

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> is the
standard tag added to ASP.NET pages by VS .NET. And, as such, the
tags/attributes I mentioned above are perfectly legal.

I think you are too hung up on W3C Recommendations, rather than real world
usage. Not all W3C Recommendations have been embraced by the development
community, at large, which is why you see slow (and in some cases, no)
adoption of W3C Specs. from time to time.

The fact of the matter is, that if you open VS.NET, and tell it to insert a
client-side script for you, it will produce exactly what I wrote. You can
like that or not, but it works everywhere and is in no danger of not working
anytime soon. The deprecated tags/attributes have been that way for 10 years
now and my money says that they will NEVER become unusable in any parsing
environment, because in the real world, they are used in hundreds of
millions of places.
 
M

Mark Rae

HTML and/or XHTML Transitional Recommendations don't indicate that the
LANGUAGE attribute is incorrect, they state that you must have the TYPE
attribute. For most of my purposes, I use both since not all clients are
new enough to understand TYPE, but all will understand LANGUAGE.
OK.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> is the
standard tag added to ASP.NET pages by VS .NET. And, as such, the
tags/attributes I mentioned above are perfectly legal.
Click to expand...

Not of you configure it properly:
Tools
Options
Text Editor
HTML
Validation...
I think you are too hung up on W3C Recommendations, rather than real world
usage. Not all W3C Recommendations have been embraced by the development
community, at large, which is why you see slow (and in some cases, no)
adoption of W3C Specs. from time to time.
Click to expand...

Fair enough. Let's agree to disagree, then, as I'm sure this is serving no
useful purpose for the rest of the newsgroup...
 
S

Scott M.

Not of you configure it properly:
Tools
Options
Text Editor
HTML
Validation...
Click to expand...

So, it's not configured "properly" to start with? Come on Mark, you're
pushing it here. Your point would be then, that MS is essentially saying
"We have created and shipped a product (3 generations worth) the we knew was
configured incorrectly, but we expect users to go into the options and
'correct' the configuation."

You must know that adding validation elements to your HTML is completely
volunatary in the first place and that adding them only helps when your code
is run through a validator.
Fair enough. Let's agree to disagree, then, as I'm sure this is serving no
useful purpose for the rest of the newsgroup...
Click to expand...

True. Makes me wonder why you brought it up when it wasn't the point of the
thread in the first place.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

AJAX progress does not work on initial page load 6
How to use a messagebox in asp.net 23
ajax progress does not display during intial page load use javascr 2
how to display a MessageBox in ASP.net 3
Messagebox in asp.net? I need another posibillity! 3
Question on accessing a nested GridViews Events 1
SOLUTION: Body onscroll, scrollTop, scrollLeft not working with master pages ??? 0
confirm messagebox, but after onclick firing 13

Top