staceyw said:

Being .Net/WPF based could be an interesting story.
1) Being vector based the free scaling/sizing would be new.
2) Browser-in-browser UX (e.g. picture-in-picture).  You could easily add other brower windows inside others for some interesting features.  Each browser could also be at a different scale or clipping region.
3) Make client follow ASP.Net component model and pipeline on the client.  Can hook in anywhere in the pipeline.  Allows you to program and script your browser UX and sessions.  A Favorite, for example, could be a piece of script that sets up some tabs or a browser-in-browser experience.

Many other things become possible and interesting.

-> 3) Make client follow ASP.Net component model and pipeline on the client.  Can hook in anywhere in the pipeline.  Allows you to program and script your browser UX and sessions.

If you use WPF for a reasonable period of time, you might think WPF's control/component model is much better.

Zhou Yong