stevo_ said:

I wouldn't get to excited, I don't think its going anywhere.. theres just a lot of work that needs to go into a browser.. writing one in .net would be interesting from an extensibility point (perhaps, but still less so interesting than extensions in say firefox- which are much more approachable).

But I don't really see otherwise why..

Paste the following into XAMLpad:

<Window
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    Title="Window1" Height="300" Width="300">
    <Grid>
        <Rectangle Width="40" Height="40" Fill="Beige" HorizontalAlignment="left"/>
        <WebBrowser  Margin="15" Source="http://channel9.msdn.com" />
        <Rectangle Width="40" Height="40" Fill="AliceBlue" VerticalAlignment="top"/>
        <Menu VerticalAlignment="Top">
            <MenuItem Header="_File">
                <MenuItem Header="_New"/>
                <MenuItem Header="_Open"/>
                <MenuItem Header="Close"/>
        </MenuItem>
        </Menu>
        <Label VerticalAlignment="Center" HorizontalAlignment="Center">This Text should should appear over the top of everything</Label>
    </Grid>
</Window>

 

Notice how the webbrowser appears over the top of everything. It's a limitation of hosting a native control in a WPF application, which really limits the things you can acheive. A 100% WPF based managed webbrowser control would allow you to integrate HTML content in a much more natural and flexible way.