A Net Applications study (via ReadWriteWeb) says IE’s market share has dropped to 67%:
This is an interesting trend. The actual quantity of market share will vary with methodology, but a 7% drop in a year is something to take note of. Moreover, as Readwrite points out, there are two things that will probably make the [...]
Welcome to Ye Olde Ajax Patterns Podcaste, the final in this series that began twelve months ago. 3+4+4+1 = 12 podcasts in all, covering 71 patterns (the 70 patterns in the the book as well as Dyanmic Favicons). Find them all on the podcast category – http://www.softwareas.com/category/podcast/ or subscribe to the podcast feed at http://www.softwareas.com/podcast/rss2. Thanks [...]
Tags: Agile·AjaxPatterns·DHTML·Firebug·Firefox·IE·Javascript·Links·TDD·Venkman·Web·Web 2.0
Comet Takes to IE Like a Fish Takes to Acid
Comet - or HTTP Streaming, if you will - is a little sensitive when it comes to portability, and I'll give you four guesses which major browser is causing the grief? Yeah, IE makes it difficult for two reasons: (a) IE's XMLHttpRequest component doesn't tell [...]
Tags: AjaxPatterns·Comet·IE·IFrame·Javascript·Links·Push·Streaming·XMLHttpRequest
Setting up a new Windows PC today and not loving the browser warnings.
The messages, as I recall them: "You are about to submit the form. It's dangerous.", "You're going to leave the page. It's dangerous.", "This page is encrypted. It's dangerous.", "This page is not encrypted. It's dangerous.", "This is H20. It's dangerous."
So my question [...]
If Ajax apps are to be rich, there must be a way for the server to pass new information to the browser. For example, new stock quotes or an instant message someone else just sent you. But the browser's not a server, so the server can't initiate an HTTP connection to alert the browser. The [...]
Tags: AjaxPatterns·Firefox·HTTP·IE·Javascript·JotLive·Links·Nevow·Streaming·XMLHttpRequest
