I completely agree with Meok on this one. The tabs in Chrome are actual windows docked into a common frame.
But since some people are still used to this method, it would maybe be a good idea considering this for the extensions interface in some way, if it hasn't been already. I'd rather see it as a plugin than an option, even though it would only add a few KB of code. (if that) In fact, this is the very same problem with Firefox, in that it has became more and more bloated with each release, adding in new functionality that THEY believe people would want. Mozilla has been steering away from the goal of Firefox every new release, which is why i switched away. "I don't want functionality i won't use." On May 12, 3:35 pm, Meok <[email protected]> wrote: > I don't agree. I think what we are forgetting is that a "Tab" in > Chrome is a window which is docked. When you click a tab, the browser > controls and toolbars are actually INSIDE the tab, and not that the > tab is inside the browser window. Each tab IS a window itself, hence I > can seamlessly pull them out or snap them back in. Therefore, the > "Browser" itself is only a holder of windows. Closing the last tab > SHOULD close the whole frame if you're viewing Chrome the way it is > meant to be the viewed. We still view Chrome like the other browsers > but the underlying architecture is totally opposite that of Firefox, > IE etc. > > On May 12, 10:28 am, Itai <[email protected]> wrote: > > > @krtulmay: > > Thank you for putting this so consicely, this is exactly the reason > > the last tab close should keep the browser open. > > > As mentioned earlier, there is already an X to close the browser > > entirely, so why not give more functionality > > with the same real-estate and less duplication. --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
