[whatwg] Menubars and phishing

[Ian Hickson]

I'm really stuck on this problem of how to handle running remote
applications so they definitely look like they are remote, and an
application on paypcl.com is definitely distinguishable from one on
paypal.com, even if they use near-identical code.

It should also always be possible for the user to control his windows
completely -- resize "unresizable" ones, not have any popup windows that
break out of the browser, always have access to the UA menu bar or
toolbar, etc.

Yet we want these applications to look nice, and have their own toolbars
and so forth, without looking silly.

For popup windows I think the best plan is probably to have "fake" popup
windows that are basically just position <div>s (which can be resized,
etc, but are restricted to the content area of the parent Web page). So
that's not a big problem. The big problem is how to handle menus on the
primary top-level Web application window.

In fact, on Mac, there is no per-window menu bar, and there is no way that
Web apps will ever have access to the top-level menu bar, so come to think
of it menu bars in general are out.

How should Web applications provide their feature access points?

Any suggestions on how to handle this would be welcome.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'