Re: how to switch on Standards-compliant mode for IE6 when using the trick w3 provided for serving xhtml as application/xml to IE
On Jan 23, 7:49 pm, Zhang Weiwu <zhangwe...@rea lss.comwrote:
It is not really a question of how advanced anyone is. One browser
currently taking 85%-95% of the market share (by locations) doesn't
know of application/xhtml+xml content type. This way your task is as
"easy" as say to force remotely some browser to act in a special way
on Content-Type application/octet-stream - say display hex codes on
the screen instead of prompting for download.
In my _private_ opinion XHTML is an obsolete technology to forget and
to move on. Yes, the thing is that it got outdated without even ever
being in any wide use. Just the concept appeared not needed and not
interesting to anyone. In this aspect the decision do not add XHTML on
IE7 was some E.L.E. on "splendid XHTML evolution". It was merely the
final conclusion on a pretty much clear picture.
W3C may still save the rest of the face by adopting HTML 5 - and by
dropping any future attempts to obsolete something on the Web by
purely administrative means. W3C tried it several times already and
each time got obsoleted itself instead. Well, some things are getting
over a hard learning I guess...
On Jan 23, 7:49 pm, Zhang Weiwu <zhangwe...@rea lss.comwrote:
Now I know I should not use XHTML but it's too late already. I am already
warned only "advanced user" will be able to use xhtml, but I *thought* I
am an advanced user (4 year Linux user and 3 year apache admin). Now I
think the trouble doesn't worth... I should have used HTML!
warned only "advanced user" will be able to use xhtml, but I *thought* I
am an advanced user (4 year Linux user and 3 year apache admin). Now I
think the trouble doesn't worth... I should have used HTML!
currently taking 85%-95% of the market share (by locations) doesn't
know of application/xhtml+xml content type. This way your task is as
"easy" as say to force remotely some browser to act in a special way
on Content-Type application/octet-stream - say display hex codes on
the screen instead of prompting for download.
In my _private_ opinion XHTML is an obsolete technology to forget and
to move on. Yes, the thing is that it got outdated without even ever
being in any wide use. Just the concept appeared not needed and not
interesting to anyone. In this aspect the decision do not add XHTML on
IE7 was some E.L.E. on "splendid XHTML evolution". It was merely the
final conclusion on a pretty much clear picture.
W3C may still save the rest of the face by adopting HTML 5 - and by
dropping any future attempts to obsolete something on the Web by
purely administrative means. W3C tried it several times already and
each time got obsoleted itself instead. Well, some things are getting
over a hard learning I guess...
Comment