473,574 Members | 13,331 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

beta2 XHTML compliance? is this necessary. OR STUPID...read UP MICROSOFT

I heard that beta 2 now makes ASP.NET xhtml compliant.

Can anyone shed some light on what this will change and it will break stuff
as converting HTML to XHTML pages DO break things. see,
http://www.alistapart.com/articles/betterliving/

I read on
http://msdn.microsoft.com/netframewo...etfxcompat.asp

It said they changed stuff like this

" Standards Compliance: The HTML rendering in ASP.NET was updated to be
XHTML 1.0 Transitional, which is standards compliant "

which is again another STUPID standard compliance mindnumb robot type of
thinking. Standard compliance is and will NEVER be important as getting it
to work on multiple browsers, period. What good is standards if the app
doesn't even work? How about a new standard? It's called getting it to work
instead of listening to some stupid committee who sits around all day in
conference talking to each other but know nothing of the real world in
getting things to actually work.

Jul 21 '05
119 4565
how is coming here to talk to Microsoft? there are no MS employees here that
monitor this place, its only MVP's... besides that the only "MSFT" tags you
will see is MSDN monitors for managed support tickets that MSDN subscribers
created on here... they don't even see the posts that people who don't
subscribe to MSDN.

If you want to talk to microsoft email their wish email address.. this is
not the place for that.

"rhat" <no***@hotmail. com> wrote in message
news:uT******** ********@TK2MSF TNGP15.phx.gbl. ..
BTW....coming here is to talk to microsoft and those who have a clue...

And not MVP's who couldn't even code in the real world but somehow have
all
the time in the world answering the same nickel and dime questions for
free
BUT somehow Microsoft is hiring like crazy, can't even get there products
out the door, but for some reason don't want to hire these so-called
MVP......and why is that? because MVP's are just "profession als" whatever
that means as OPPOSED TO "programmer s" who can actually do the work.



"Brian Henry" <no****@newsgro ups.com> wrote in message
news:%2******** ********@TK2MSF TNGP12.phx.gbl. ..
btw.. coming here for the first time and posting something like this,
just
shows nothing more then an attitude to want to cause a fight about

something
stupid you know little about...

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>I heard that beta 2 now makes ASP.NET xhtml compliant.
>
> Can anyone shed some light on what this will change and it will break
> stuff
> as converting HTML to XHTML pages DO break things. see,
> http://www.alistapart.com/articles/betterliving/
>
> I read on
> http://msdn.microsoft.com/netframewo...etfxcompat.asp >
> It said they changed stuff like this
>
> " Standards Compliance: The HTML rendering in ASP.NET was updated to be
> XHTML 1.0 Transitional, which is standards compliant "
>
> which is again another STUPID standard compliance mindnumb robot type
> of
> thinking. Standard compliance is and will NEVER be important as
> getting
> it
> to work on multiple browsers, period. What good is standards if the app
> doesn't even work? How about a new standard? It's called getting it to
> work
> instead of listening to some stupid committee who sits around all day
> in
> conference talking to each other but know nothing of the real world in
> getting things to actually work.
>
>
>
>
>



Jul 21 '05 #21
name the browsers already that "Arnt" complient with XHTML1.0 you keep
blabbing about them but never backed it up with facts or names or
examples... so start giving them or be quiet, because a lot of us here have
many years of experience with all this and know what does and doesn't work.
"rhat" <no***@hotmail. com> wrote in message
news:eT******** *****@TK2MSFTNG P15.phx.gbl...
Typical, ms speak who knows nothing of the REAL world....

Since XHTML is NOT supported by all browsers, I should not have to
RE-WRITE
my app to just to ACTUALLY GET IT WORK IN the REAL WORLD of all
browsers.....

Getting it to work in the REAL WORLD is MORE important than being
standards
compliant especially when not everyone can agree on which standard to
support.

But because you PROBABLY DON'T CODE, NOR have any web apps to begin that
actually have customers and where you actually have to make a profit, you
wouldn't know.

"John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
news:ef******** ******@TK2MSFTN GP15.phx.gbl...
If you want to degrade asp2 to be non xhtml compliant, all it takes is an
ihttpfilter to degrade the tags you want in the applications you need
degrading - which is the easiest approach to make asp1.x xhtml compliant.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>I heard that beta 2 now makes ASP.NET xhtml compliant.
>
> Can anyone shed some light on what this will change and it will break
> stuff
> as converting HTML to XHTML pages DO break things. see,
> http://www.alistapart.com/articles/betterliving/
>
> I read on
> http://msdn.microsoft.com/netframewo...etfxcompat.asp >
> It said they changed stuff like this
>
> " Standards Compliance: The HTML rendering in ASP.NET was updated to be
> XHTML 1.0 Transitional, which is standards compliant "
>
> which is again another STUPID standard compliance mindnumb robot type
> of
> thinking. Standard compliance is and will NEVER be important as
> getting
> it
> to work on multiple browsers, period. What good is standards if the app
> doesn't even work? How about a new standard? It's called getting it to
> work
> instead of listening to some stupid committee who sits around all day
> in
> conference talking to each other but know nothing of the real world in
> getting things to actually work.
>
>
>
>
>



Jul 21 '05 #22
the following browsers are XHTML 1.0 complient

* Amaya
* Mozilla
* FireFox 1.0
* Internet Explorer 5.0
* Internet Explorer 6.0
* Safari
* Opera

so please... once again... tell me what browsers you are talking about that
arn't complient that using XHTML1.0 code will "break" compatability?

"rhat" <no***@hotmail. com> wrote in message
news:eT******** *****@TK2MSFTNG P15.phx.gbl...
Typical, ms speak who knows nothing of the REAL world....

Since XHTML is NOT supported by all browsers, I should not have to
RE-WRITE
my app to just to ACTUALLY GET IT WORK IN the REAL WORLD of all
browsers.....

Getting it to work in the REAL WORLD is MORE important than being
standards
compliant especially when not everyone can agree on which standard to
support.

But because you PROBABLY DON'T CODE, NOR have any web apps to begin that
actually have customers and where you actually have to make a profit, you
wouldn't know.

"John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
news:ef******** ******@TK2MSFTN GP15.phx.gbl...
If you want to degrade asp2 to be non xhtml compliant, all it takes is an
ihttpfilter to degrade the tags you want in the applications you need
degrading - which is the easiest approach to make asp1.x xhtml compliant.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>I heard that beta 2 now makes ASP.NET xhtml compliant.
>
> Can anyone shed some light on what this will change and it will break
> stuff
> as converting HTML to XHTML pages DO break things. see,
> http://www.alistapart.com/articles/betterliving/
>
> I read on
> http://msdn.microsoft.com/netframewo...etfxcompat.asp >
> It said they changed stuff like this
>
> " Standards Compliance: The HTML rendering in ASP.NET was updated to be
> XHTML 1.0 Transitional, which is standards compliant "
>
> which is again another STUPID standard compliance mindnumb robot type
> of
> thinking. Standard compliance is and will NEVER be important as
> getting
> it
> to work on multiple browsers, period. What good is standards if the app
> doesn't even work? How about a new standard? It's called getting it to
> work
> instead of listening to some stupid committee who sits around all day
> in
> conference talking to each other but know nothing of the real world in
> getting things to actually work.
>
>
>
>
>



Jul 21 '05 #23
In the REAL WORLD, 90% is NOT good enough...just like 99% is NOT GOOD ENOUGH
for server UP TIME

There are always going to be exceptions and if we can support them all NOW
and we can, WE SHOULD NOT BREAK what's not broken.

HTML is a TRUE STANDARD......X HTML is a NOT FULLY ADOPTED STANDARD.

When you can actually write a web app in the REAL world, let me know. NO MVP
who has that much time on their hands should be telling me or anyone else in
the real world what to do until they can actually do it iin a real world
environment with customers themselves first.

TO ALL MVPs:

GET A REAL JOB where you don't spend all day in the newsgroups answering
questions for free and with no accountability if your decisions are wrong
and/or code doesn't even work.
(BTW a lot of you, actually 100% of you, are BOOK SMART intellectuals but
couldn't code a web app or any app if your life depended on it. And why is
this? Well it's because you're too arrogant to admit your mistakes and
therefore you learn nothing and make the same mistakes over and over again.
And that's why you are still here in the newsgroups posting away as opposed
to programming away.)


"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> wrote in message
news:O7******** ******@TK2MSFTN GP14.phx.gbl...
"rhat" <no***@hotmail. com> schrieb:
Just SO these people can add it to their resume saying, "SEE, I can do
XHTML" but in reality this XHTML cause these web pages not to display
properly across these browsers
Much more than 90 percent of the Web users are using browsers which are

more or less standard-compliant. Thus I don't see any reason for supporting very few exotic browsers which do not have a future.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

Jul 21 '05 #24
if you don't believe me then look at the compatability listing

http://www.xmlsoftware.com/browsers.html

"rhat" <no***@hotmail. com> wrote in message
news:eT******** *****@TK2MSFTNG P15.phx.gbl...
Typical, ms speak who knows nothing of the REAL world....

Since XHTML is NOT supported by all browsers, I should not have to
RE-WRITE
my app to just to ACTUALLY GET IT WORK IN the REAL WORLD of all
browsers.....

Getting it to work in the REAL WORLD is MORE important than being
standards
compliant especially when not everyone can agree on which standard to
support.

But because you PROBABLY DON'T CODE, NOR have any web apps to begin that
actually have customers and where you actually have to make a profit, you
wouldn't know.

"John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
news:ef******** ******@TK2MSFTN GP15.phx.gbl...
If you want to degrade asp2 to be non xhtml compliant, all it takes is an
ihttpfilter to degrade the tags you want in the applications you need
degrading - which is the easiest approach to make asp1.x xhtml compliant.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>I heard that beta 2 now makes ASP.NET xhtml compliant.
>
> Can anyone shed some light on what this will change and it will break
> stuff
> as converting HTML to XHTML pages DO break things. see,
> http://www.alistapart.com/articles/betterliving/
>
> I read on
> http://msdn.microsoft.com/netframewo...etfxcompat.asp >
> It said they changed stuff like this
>
> " Standards Compliance: The HTML rendering in ASP.NET was updated to be
> XHTML 1.0 Transitional, which is standards compliant "
>
> which is again another STUPID standard compliance mindnumb robot type
> of
> thinking. Standard compliance is and will NEVER be important as
> getting
> it
> to work on multiple browsers, period. What good is standards if the app
> doesn't even work? How about a new standard? It's called getting it to
> work
> instead of listening to some stupid committee who sits around all day
> in
> conference talking to each other but know nothing of the real world in
> getting things to actually work.
>
>
>
>
>



Jul 21 '05 #25
Cross-platform right? Ok, that means not internal, i.e. public. So where
is the URL? What's the name of the company then? Let's ask around and see if
what you say is really true to begin with and that nothing broke and the
time involved just to have a standard for standards sake.

never ending learning process? here?......if you were really in the real
world you would be here then, this is a holiday.....you would be taking a
break, not posting on a off day.

So you don't know crap and you are full of B.S. Nobody who programs 600, 000
line of code would even be here on a holiday as they really should be
resting from all the work to get that 600,000 lines of code to work.
"Brian Henry" <no****@newsgro ups.com> wrote in message
news:uS******** *******@tk2msft ngp13.phx.gbl.. .
yes it works cross platform, Opera, Firefox and IE all work correctly.. and as for the size of the application its a huge insurance processing
application, if you ever worked in the insurance field you'd know how
utterly complex it is to set up accounts, commissions, coverages,
enrollments, mantain all of that and also process claims, billing, and all
the reports required behind that. What am I doing here? it's called the
never ending learning process... you want to do something else, you ask to
see if there is a better way sometimes and that helps with a community of
people who have been there and done that.
"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
Does your web app work cross browser?

600,000 line of code? really, what are you doing here then?

most people here couldn't even code if they had to, just a bunch of
dimwits
who can't get a job OR in reality keep their job because so they are so
into
their books and the programs they did write DO NOT WORK.
"Brian Henry" <no****@newsgro ups.com> wrote in message
news:eT******** ******@tk2msftn gp13.phx.gbl...
I think you are the one out of touch with reality. The only way new
standards ever get pushed out is to force them out... When something new
or
better comes out it is never adopted at first by everyone... you know
how long it took to get XML to where it is now? You have to make changes to

the
lowest node in the tree to force all the things above it to switch also, this lowest node being the development end in this case. Of which

everything
above will eventually support once they realize there is a need for it.

Even
MS is updateing IE with IE7 to be XHTML complient and such.

And for not having a web app, I maintain a "web app" that is 600,000
lines
of code, and it works perfectly fine in XHTML, and have not seen it
broken
yet. The only part that is broken ever was some of the CSS settings which IE
did not accept correctly, which we go around with other methods.. Ontop
of
that huge application portal we have for our insurance customers, we
have an
internal intranet site, and a secure email site all writen by us in
..NET 1.1
and tested now in 2.0 beta 2.. not ONE problem that was a major one
during
the testing transfer.

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..
> This beta 2 white paper says they are going to XHTML as a default, I

think
>
> These so-called people, have the ACTUALLY TESTED there apps to see if

they
> DON'T break as opposed to "Let's be standards compliant just for the

sake
> of
> standards compliant".
>
> That's the type of nim rod robot thinking of some intellectual who's
> out
> of
> touch of reality.
>
> The reality is #1 let's make sure it works across all browsers as

opposed
> to
> let's make be standard's compliant just to satisfy some committee and

say
> so
> we slap a sticker that means nothing if it ACTUALLY doesn't work and
> breaks
> an app on this browser.
>
> Before you open your mouth and for Microsoft bunch of robots out
there, > LET"S ACTUALLY TEST before jumpt to XHTML....MOST OF YOU so-called
> standard
> advocates DO NOT even HAVE a WEB APP to begin with...so be quiet if you > don't something in production.
>
>
> "Brian Henry" <no****@newsgro ups.com> wrote in message
> news:eL******** ******@TK2MSFTN GP15.phx.gbl...
>> how about you stop complaining and accept standards and change...
> Thousands
>> of people asked for it and MS gave it to them... you should be happy

that
> MS
>> is creating something standard complient. You still have the option to >> use
>> HTML standard if you want to by changing the rendering doc type... no one
> is
>> forceing you to use XHTML 1.0
>>
>> "rhat" <no***@hotmail. com> wrote in message
>> news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>> >I heard that beta 2 now makes ASP.NET xhtml compliant.
>> >
>> > Can anyone shed some light on what this will change and it will
>> > break
>> > stuff
>> > as converting HTML to XHTML pages DO break things. see,
>> > http://www.alistapart.com/articles/betterliving/
>> >
>> > I read on
>> >
>

http://msdn.microsoft.com/netframewo...etfxcompat.asp >> >
>> > It said they changed stuff like this
>> >
>> > " Standards Compliance: The HTML rendering in ASP.NET was updated

to be
>> > XHTML 1.0 Transitional, which is standards compliant "
>> >
>> > which is again another STUPID standard compliance mindnumb robot
>> > type
>> > of
>> > thinking. Standard compliance is and will NEVER be important as
>> > getting
>> > it
>> > to work on multiple browsers, period. What good is standards if
the app
>> > doesn't even work? How about a new standard? It's called getting
it to
>> > work
>> > instead of listening to some stupid committee who sits around all
>> > day
>> > in
>> > conference talking to each other but know nothing of the real
world in
>> > getting things to actually work.
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>



Jul 21 '05 #26
In all of this you haven't stated which browsers don't process XHTML
properly. You keep saying that it is not compatible, but you never give
any evidence.

Jul 21 '05 #27
Is this all browsers on the Mac?

Just because these say they are COMPLIANT doens't mean the web page will
display properly

Does stuff in IE 6 always display in Firefox correctly? NO. end of your
arguments
"Brian Henry" <no****@newsgro ups.com> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..
the following browsers are XHTML 1.0 complient

* Amaya
* Mozilla
* FireFox 1.0
* Internet Explorer 5.0
* Internet Explorer 6.0
* Safari
* Opera

so please... once again... tell me what browsers you are talking about that arn't complient that using XHTML1.0 code will "break" compatability?

"rhat" <no***@hotmail. com> wrote in message
news:eT******** *****@TK2MSFTNG P15.phx.gbl...
Typical, ms speak who knows nothing of the REAL world....

Since XHTML is NOT supported by all browsers, I should not have to
RE-WRITE
my app to just to ACTUALLY GET IT WORK IN the REAL WORLD of all
browsers.....

Getting it to work in the REAL WORLD is MORE important than being
standards
compliant especially when not everyone can agree on which standard to
support.

But because you PROBABLY DON'T CODE, NOR have any web apps to begin that
actually have customers and where you actually have to make a profit, you
wouldn't know.

"John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
news:ef******** ******@TK2MSFTN GP15.phx.gbl...
If you want to degrade asp2 to be non xhtml compliant, all it takes is an ihttpfilter to degrade the tags you want in the applications you need
degrading - which is the easiest approach to make asp1.x xhtml compliant.
--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>I heard that beta 2 now makes ASP.NET xhtml compliant.
>
> Can anyone shed some light on what this will change and it will break
> stuff
> as converting HTML to XHTML pages DO break things. see,
> http://www.alistapart.com/articles/betterliving/
>
> I read on
>

http://msdn.microsoft.com/netframewo...etfxcompat.asp
>
> It said they changed stuff like this
>
> " Standards Compliance: The HTML rendering in ASP.NET was updated to be > XHTML 1.0 Transitional, which is standards compliant "
>
> which is again another STUPID standard compliance mindnumb robot type
> of
> thinking. Standard compliance is and will NEVER be important as
> getting
> it
> to work on multiple browsers, period. What good is standards if the app > doesn't even work? How about a new standard? It's called getting it to > work
> instead of listening to some stupid committee who sits around all day
> in
> conference talking to each other but know nothing of the real world in > getting things to actually work.
>
>
>
>
>



Jul 21 '05 #28
Total B.S.

There are still lots of pages in IE 6 that don't display properly in
Firefox....

That fact that you easily can point to reference sites shows me that you are
just a book worm and not a real life programmer who can actually admit that
XHTML didn't work all the time when you converted over.
"Brian Henry" <no****@newsgro ups.com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..
if you don't believe me then look at the compatability listing

http://www.xmlsoftware.com/browsers.html

"rhat" <no***@hotmail. com> wrote in message
news:eT******** *****@TK2MSFTNG P15.phx.gbl...
Typical, ms speak who knows nothing of the REAL world....

Since XHTML is NOT supported by all browsers, I should not have to
RE-WRITE
my app to just to ACTUALLY GET IT WORK IN the REAL WORLD of all
browsers.....

Getting it to work in the REAL WORLD is MORE important than being
standards
compliant especially when not everyone can agree on which standard to
support.

But because you PROBABLY DON'T CODE, NOR have any web apps to begin that
actually have customers and where you actually have to make a profit, you
wouldn't know.

"John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
news:ef******** ******@TK2MSFTN GP15.phx.gbl...
If you want to degrade asp2 to be non xhtml compliant, all it takes is an ihttpfilter to degrade the tags you want in the applications you need
degrading - which is the easiest approach to make asp1.x xhtml compliant.
--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>I heard that beta 2 now makes ASP.NET xhtml compliant.
>
> Can anyone shed some light on what this will change and it will break
> stuff
> as converting HTML to XHTML pages DO break things. see,
> http://www.alistapart.com/articles/betterliving/
>
> I read on
>

http://msdn.microsoft.com/netframewo...etfxcompat.asp
>
> It said they changed stuff like this
>
> " Standards Compliance: The HTML rendering in ASP.NET was updated to be > XHTML 1.0 Transitional, which is standards compliant "
>
> which is again another STUPID standard compliance mindnumb robot type
> of
> thinking. Standard compliance is and will NEVER be important as
> getting
> it
> to work on multiple browsers, period. What good is standards if the app > doesn't even work? How about a new standard? It's called getting it to > work
> instead of listening to some stupid committee who sits around all day
> in
> conference talking to each other but know nothing of the real world in > getting things to actually work.
>
>
>
>
>



Jul 21 '05 #29
does safari and mozilla render pages exactly the same? no so drop it.
everyone has their own rendering scheme and no one is required to follow W3C
exactly, W3C even says so on their own page. What they say is just a
recomendadtion

"rhat" <no***@hotmail. com> wrote in message
news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
Is this all browsers on the Mac?

Just because these say they are COMPLIANT doens't mean the web page will
display properly

Does stuff in IE 6 always display in Firefox correctly? NO. end of your
arguments
"Brian Henry" <no****@newsgro ups.com> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..
the following browsers are XHTML 1.0 complient

* Amaya
* Mozilla
* FireFox 1.0
* Internet Explorer 5.0
* Internet Explorer 6.0
* Safari
* Opera

so please... once again... tell me what browsers you are talking about

that
arn't complient that using XHTML1.0 code will "break" compatability?

"rhat" <no***@hotmail. com> wrote in message
news:eT******** *****@TK2MSFTNG P15.phx.gbl...
> Typical, ms speak who knows nothing of the REAL world....
>
> Since XHTML is NOT supported by all browsers, I should not have to
> RE-WRITE
> my app to just to ACTUALLY GET IT WORK IN the REAL WORLD of all
> browsers.....
>
> Getting it to work in the REAL WORLD is MORE important than being
> standards
> compliant especially when not everyone can agree on which standard to
> support.
>
> But because you PROBABLY DON'T CODE, NOR have any web apps to begin
> that
> actually have customers and where you actually have to make a profit, you > wouldn't know.
>
>
>
> "John Timney (ASP.NET MVP)" <ti*****@despam med.com> wrote in message
> news:ef******** ******@TK2MSFTN GP15.phx.gbl...
>> If you want to degrade asp2 to be non xhtml compliant, all it takes is an >> ihttpfilter to degrade the tags you want in the applications you need
>> degrading - which is the easiest approach to make asp1.x xhtml compliant. >>
>> --
>> Regards
>>
>> John Timney
>> ASP.NET MVP
>> Microsoft Regional Director
>>
>> "rhat" <no***@hotmail. com> wrote in message
>> news:%2******** ********@TK2MSF TNGP10.phx.gbl. ..
>> >I heard that beta 2 now makes ASP.NET xhtml compliant.
>> >
>> > Can anyone shed some light on what this will change and it will
>> > break
>> > stuff
>> > as converting HTML to XHTML pages DO break things. see,
>> > http://www.alistapart.com/articles/betterliving/
>> >
>> > I read on
>> >
> http://msdn.microsoft.com/netframewo...etfxcompat.asp >> >
>> > It said they changed stuff like this
>> >
>> > " Standards Compliance: The HTML rendering in ASP.NET was updated to be >> > XHTML 1.0 Transitional, which is standards compliant "
>> >
>> > which is again another STUPID standard compliance mindnumb robot
>> > type
>> > of
>> > thinking. Standard compliance is and will NEVER be important as
>> > getting
>> > it
>> > to work on multiple browsers, period. What good is standards if the app >> > doesn't even work? How about a new standard? It's called getting it to >> > work
>> > instead of listening to some stupid committee who sits around all
>> > day
>> > in
>> > conference talking to each other but know nothing of the real world in >> > getting things to actually work.
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>



Jul 21 '05 #30

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

98
2699
by: rhat | last post by:
I heard that beta 2 now makes ASP.NET xhtml compliant. Can anyone shed some light on what this will change and it will break stuff as converting HTML to XHTML pages DO break things. see, http://www.alistapart.com/articles/betterliving/ I read on...
0
8258
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
1
7833
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For...
0
8119
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
0
6482
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then...
1
5635
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
5322
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert...
1
2254
by: 6302768590 | last post by:
Hai team i want code for transfer the data from one system to another through IP address by using C# our system has to for every 5mins then we have to update the data what the data is updated we have to send another system
1
1359
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.
0
1082
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.