Having browser windows in emacs would also allow allow users to benefit from emacs window capabilities (fuzzy completion with ido-mode, listing/filter with ibuffer, tabs, side-by-side splitting, and basically whatever else folks decide to code in elisp). Classical web browser basically have tabs, and keybindings to next/previous tabs. Emacs would make it much more powerful.
Besides, as many people noted, it shouldn't be hard to do, since technologies to do so already exist. IMHO, the tough step is getting text and textboxes recognised by emacs, but even without that, it'd still be amazing.
Good luck to you joakim, and please consider browsers as an equally useful target of embedding as multimedia apps.
2008/9/8 Chong Yidong
<address@hidden>
> Switching constantly between Emacs and Firefox (e.g., by making Emacs
> open links via a separate Firefox application) is inefficient.
>
> When you say "switching", what does that refer to?
> Are you talking about a UI-level operation?
Yes.
> In what sense is it inefficient?
In the same sense that it's less efficient to perform shell operations
in a separate xterm, rather than doing M-! or M-x grep or M-x gdb etc.
For instance, it's more cumbersome to arrange to view the browser
display and side by side with Emacs, since the browser isn't constrained
to an Emacs window.