[chromium-dev] Re: middle click on home
Yes, it can also close tabs. I meant to emphasis the _background_ part of the operation. It also opens _in_the_background_. When it closes a tab, it closes it in the background too ;) - Itai On Jun 29, 10:01 am, Mike Pinkerton wrote: > > Middle-click always opens a new tab in the background and making > > exceptions is just likely to confuse users. > > Except when middle-clicking on a tab means "close the tab". So it > means both open and close, depending on the context. > > -- > Mike Pinkerton > Mac Weenie > pinker...@google.com --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: middle click on home
@krtumay: I think you are confused now. Evan was asking about the Home button (which optionally appears in the navigation bar, next to reload). NTP can also be opened in the foreground as a new tab using the small '+" icon. The '+' actually does not support middle-click, you must use left-click. Middle-click always opens a new tab in the background and making exceptions is just likely to confuse users. We are trying to keep things as predictable as possible which is important for software that does not come with a manual. - Itai On Jun 29, 3:19 am, krtulmay wrote: > Consistency with other tabs opening in the background is fine, but I > must agree with Evan on suggesting that the New Tab page should > clearly be an exception. Since you can always open an NTP and there > are so many ways to do it, you would never want to queue any NTPs in > the background, and the only time you ever need an NTP is if you need > it *right now*, so it should open in the foreground. This is a > clearly needed exception. > > And actually, my question about tabs opening in the background should > be generalized to Chrome's default of opening tabs in the background. > It is not fine for the 50% of users who do want tabs to open in the > foreground. And if Google has testing that says the otherwise, I > would like to see an explicit statement saying so and preferably with > quantified stats please. > > On Jun 27, 5:59 pm, Peter Kasting wrote: > > > > > I argued from the point of consistency and mentioned my personal preference > > only as an afternote to point out that the consistent behavior would not be > > universally despised. > > > PK > > > On Jun 27, 2009 4:08 PM, "krtulmay" wrote: > > > This is fine except for the other 50% of users who do want the browser > > to change tabs for them. > > > And before you reply with "there are more than 50% of users who want > > new tabs queued in the background" or say that it's your preference, I > > would like to see explicitly a statement from Google's testing if it > > actually is so and preferably with quantified stats please. > > > On Jun 26, 5:22 pm, Peter Kasting wrote: > Given that > > there are a large numbe... > > > > On Jun 26, 2009 5:09 PM, "Evan Martin" wrote: > > > > On Fri, Jun 26, 2009 at 5:06 PM, Peter Kasting > > > wrote: > > > I don't underst... > > > --~--~-~--~~~---~--~~ Chromium Developers > > mailing list: chromium-dev... --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: What's the real reason of giving up Windows 2000 support?
Feel free to make an eComstation port though, 2.0 is about to be released, plus its not that different from any other OS ;) - Itai On Jun 23, 12:48 pm, "Elliot Glaysher (Chromium)" wrote: > On Tue, Jun 23, 2009 at 8:58 AM, Dan Kegel wrote: > > p.s. And OS/2 is right out. > > And no Amiga port, either. > > -- Elliot --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Try out --enable-omnibox2!
I know this is only for complaints ;) but I like the present look. The clues as to where each omnibox suggestion comes from are great, clear and useful! - Itai On May 14, 3:22 pm, "Ben Goodger (Google)" wrote: > I have adjusted the transparency slightly, and disabled it altogether > when Glass isn't active. Let me know how annoying it is now. (I have a > knob, and can adjust the annoyingness). > > -Ben > > > > On Fri, May 8, 2009 at 2:20 PM, Mike Belshe wrote: > > On Thu, May 7, 2009 at 4:27 PM, Mohamed Mansour > > wrote: > > >> Great! adds a new fresh look. > > > +1 > > >> One question though, is the transparency really needed? It distracts me > >> for some reason from the actual results. I suggest lowering down the > >> transparency a little, but that's just me. > > > +1 - I don't like the transparency either. I'd prefer opaque. > > Mike > > >> On Thu, May 7, 2009 at 1:53 PM, Ben Goodger (Google) > >> wrote: > > >>> Please try out the --enable-omnibox2 command line switch in Chrome and > >>> file bugs against me in the issue tracker. I'd like to get a better > >>> sense of what needs to be done with it so we can turn it on by > >>> default. > > >>> The differences thus far are aesthetic, and in the popup. > > >>> -Ben --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Request for comments: Feed preview work
Minor comment, but I assume you will be triggering the feed-preview when people click on a link to the feed as well. Many sites have an RSS link to the feed's XML file because it is previewable in many browsers without autodiscovery. Currently, Chrome shows unformated XML. Doing CTRL-U after shows the formatted XML source which is at least better than its unformatted version. - Itai On May 6, 8:36 pm, Finnur Thorarinsson wrote: > I just wanted to give you heads up that soon it will be time for me to > devote most of my time on the second part of the Feed handling support in > Chrome, namely: Feed Previews > (http://dev.chromium.org/user-experience/feed-subscriptions). > > Consider this a request for your feedback, especially if you know about the > status of the previous feed preview work or have opinions on the general > direction/approach we should take. > > I have already added an API for PageActions and have a working RSS > PageAction extension, which does feed auto-detection on the page. Now it is > time to look into Feed previews. > > I have spoken briefly to AdamB and EvanM about feed previews and both > suggested modelling this after the view-source implementation. It was also > suggested to add a scheme for this (like we do with view-source), such as > view-feed: or feed: > > I know there has been some work on this front before, although the status of > that is not clear to me -- except that it was disabled at some point (or > removed from the codebase?). I would love to see what was done back then, if > anyone knows more. A cursory look through the code indicated that mime type > sniffing for feed is done. I've heard there is also some remaining work > required for sanitizing the feeds before showing, but besides the above > there is not much more I know at this point in time. > > Comments welcome. --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
