[thelist] favicon weirdness

[Peter-Paul Koch]

>: >I agree with Jeff. I've just spend the last week at Microsoft looking at
>: >some of the stuff that'll be coming out. There are things that you'll be
>: >able to do with IE that you simply can not do with any other browser
>: >(well,certainly without a vast amount of custom code, and huge
>: >numbers of server roundtrips).
>: >
>: great, more proprietary DOM?
>:
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>I think you'll find that IE support for w3 standards will increase
>substantially. I'm sure it's been mentioned on this list that members of 
>the
>IE development teams have been checking these things out in various
>community forums.

That story is just wishful thinking. Is MS engineers asking about the 
standards so weird that it can only be explained when they want to make IE 
standards compliant? What a nonsense.

They might add something in the display: list-item category, something that 
is a standard so they can brag about it but is completely useless in day to 
day web developing.

>However, there is a *vast* amount of application development that's going 
>on
>that extends way beyond the traditional "public website", where the
>capabilities of HTML/Javascript/DOM + HTTP are simply insufficient to cater
>for needs of the application. There'll be a whole heap of stuff that'll
>allow both the client and server to overcome some of these limitations. You
>can do it now - but there's always hassles, and 3rd party technology,
>involved. Instead, it'll be baked into the OS/IE.

Oh, that. You're referring to some new .NET application stuff, I suppose. 
Now that's all very nice and dandy, but for the moment my conclusion is that 
we don't *need* any application stuff because the W3C DOM will serve nicely.

>I can't reveal specifics, obviously, due to NDAs etc. However, anyone who
>does web-application development will be able to tell you all about the
>"extra" stuff that's currently required to get things working

We don't need extra's when we have the W3C DOM, except for a good way to 
save XML back to the server, and pasting it into a textarea and then 
submitting the textarea is a working, albeit ugly, solution.

-------------------------------------------------------------------
ppk, freelance web developer
Interaction, copywriting, JavaScript, integration
http://www.xs4all.nl/~ppk/
Column "Keep it Simple": http://www.digital-web.com/columns/keepitsimple/
New: Browser Wars II: The Saga Continues
http://evolt.org/article/rdf/25/60181/
------------------------------------------------------------------

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail