(This isn't guerilla lobbying; I'm genuinely curious as to why they would resist including a feature I find so useful. And anyway, the third-party type-ahead-find extension is working adequately for me, so far...)
Re:Speedier, simpler and safer: Chrome’s basics get even better
by Estragon on Wednesday March 09, 2011 @06:46AM
(#2304605)
That response misses the key advantage of Type-Ahead Find (which I guess I didn't make clear in my question) that pressing tab moves the focus to the next link in the text flow, and pressing Enter (Ctrl-Enter) opens the link (in a new window with Ctrl-Enter.) It's a much faster way to browse, because it completely eliminates mousing.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by Estragon on Wednesday March 09, 2011 @01:27PM
(#2305812)
Yes, your initial response made that clear. Hopefully my response to you made it clear that I don't buy it, because it ignores the main reason why the feature is so attractive.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by pasbesoin on Wednesday March 09, 2011 @12:51PM
(#2305662)
OOT: It's a long-standing design decision (I've seen it described as such; don't currently have the link) not to implement MRU (most recently used) order for Ctrl-Tab switching.
In other browsers, I used that all the time. When looking for a solution for Chrome, I found many other people miss it, as well. As of v5 or v6, IIRC, default key bindings cannot be overridden (for security), so an extension cannot solve this.
Just mentioning again, in case any Chrome developers are passing by and have just had a big jolt of caffeine, making them temporarily more agreeable. ;-)
EDIT: To clarify, I think it would make a good -- even if they are rare in Chrome -- selectable option; keep the default as it is.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by swix on Tuesday March 08, 2011 @01:12PM
(#2301901)
Great as always, it's just sad that the competition is so much behind in js performance :( but awesome work chrome team! I have only noticed slow performance for one single thing in chrome... border-radius:
Have anyone noticed that Chrome is slow if you have a lot of elements (A table with 20+) or something TDs that has -webkit-border-radius ? Scrolling on the page becomes sluggish, but if you dont use the border radius scrolling is normal.
This also happends if you use draggables with jquery and -webkit-border-radius , it's more sluggish to drag this div around (With border-radius) than a normal div, guess it's more work to render round corners, but would be cool with a fix here.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by ootachi on Tuesday March 08, 2011 @01:27PM
(#2301983)
Chrome doesn't have retained layers, so it has to redraw the entire page every time you scroll. In fact, no shipping browser has retained layers except Safari in limited circumstances (not scrolling AFAIK), although Firefox 4 will have it soon.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by beaumartinez on Tuesday March 08, 2011 @05:41PM
(#2302893)
> To justify the added complexity.
Have you had a look at Chromium's source tree[1]? It's huge! I don't know how much complexity they'd save themselves removing a small feature like that (although you never know).
Have a look at the building instructions[2] as well. "Due mostly to its history and its complexity, Chromium uses a nonstandard set of custom tools to check out and build."
It's a good showcase on the complexity of a browser (and Chrome feels so light and speedy as well.)
Re:Speedier, simpler and safer: Chrome’s basics get even better
by sudonim on Tuesday March 08, 2011 @02:46PM
(#2302310)
Unsurprising to see them add the preferences to the browser. Your preferences (settings) exist like this in the CR-48 running Chrome OS. This change is probably driven by the desire to standardize both interface and codebase more than anything else. It's not standard to do it this way on any OS and feels a little odd.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by AndreSegers on Tuesday March 08, 2011 @05:23PM
(#2302839)
Indeed, but I'm mixed on the change. I used to filled with the options while being able to see the webpage in the background, which I can no longer do (without pulling out the tab). But it's growing on me.
Re:Speedier, simpler and safer: Chrome’s basics get even better
by MikeCapone on Tuesday March 08, 2011 @04:45PM
(#2302710)
For some reason I can't watch youtube in full-screen anymore in Chrome (I get a blank screen) on my Macbook, and many youtube video are choppy. Works fine in Safari, and used to work fine in Chrome.
I thought this upgrade would fix it, but it didn't... Anybody else experiencing this issue?
Re:Speedier, simpler and safer: Chrome’s basics get even better
by MikeCapone on Tuesday March 08, 2011 @06:54PM
(#2303124)
I'm on a Mac. It says I have two versions:
Shockwave Flash 10.2 r154
Version: 10.2.154.18
and
Shockwave Flash 10.1 r102
Version: 10.1.102.64
One in a Chrome sub-directory and the other in /Library/Internet Plug-ins/
I'm not familiar with SuperUser, but I'll check it out if I can't figure it out. Thanks!
Update: I disabled one of the two flash plugins and tried youtube and it was fine. Then I re-enabled it and it was still fine. Weird bug, but hopefully it's gone for good.
1: You don't agree with their reason, or
2: You don't believe that is the real reason.
In other browsers, I used that all the time. When looking for a solution for Chrome, I found many other people miss it, as well. As of v5 or v6, IIRC, default key bindings cannot be overridden (for security), so an extension cannot solve this.
Just mentioning again, in case any Chrome developers are passing by and have just had a big jolt of caffeine, making them temporarily more agreeable. ;-)
EDIT: To clarify, I think it would make a good -- even if they are rare in Chrome -- selectable option; keep the default as it is.
Have anyone noticed that Chrome is slow if you have a lot of elements (A table with 20+) or something TDs that has -webkit-border-radius ? Scrolling on the page becomes sluggish, but if you dont use the border radius scrolling is normal.
This also happends if you use draggables with jquery and -webkit-border-radius , it's more sluggish to drag this div around (With border-radius) than a normal div, guess it's more work to render round corners, but would be cool with a fix here.
If it's something you absolutely have to have, there's always extensions.
I do on a regular basis, in order to get PDFs out of their frame on the Blackboard system of my university.
:)
I have the same problem, so I feel you.
Have you had a look at Chromium's source tree[1]? It's huge! I don't know how much complexity they'd save themselves removing a small feature like that (although you never know).
Have a look at the building instructions[2] as well. "Due mostly to its history and its complexity, Chromium uses a nonstandard set of custom tools to check out and build."
It's a good showcase on the complexity of a browser (and Chrome feels so light and speedy as well.)
[1] http://src.chromium.org/viewvc/chrome/trunk/src/ [2] http://code.google.com/p/chromium/wiki/LinuxBuildInstruction...
I thought this upgrade would fix it, but it didn't... Anybody else experiencing this issue?
Have a look at chrome://plugins; ask on SuperUser if you can't find an immediate solution to the problem yourself.
Shockwave Flash 10.2 r154 Version: 10.2.154.18
and
Shockwave Flash 10.1 r102 Version: 10.1.102.64
One in a Chrome sub-directory and the other in /Library/Internet Plug-ins/
I'm not familiar with SuperUser, but I'll check it out if I can't figure it out. Thanks!
Update: I disabled one of the two flash plugins and tried youtube and it was fine. Then I re-enabled it and it was still fine. Weird bug, but hopefully it's gone for good.
(vigorous fist pumps)