Dev channel has been bumped up to 0.12.362.2 this evening with a number of improvements:
- The new Chrome Logo is visible on boot.
- You can now retake your login photo or swap the image out for any other image by going to Wrench -> Settings -> Personal Stuff.
- The window switcher button that appeared in 0.11 is now only visible when two or more windows are open (so people who only have one window open won't wonder about the useless box at the top right).
- All bugs eradicated.
Okay, maybe the last one's not quite true. But if see anything else good or bad, be sure to let us know.
I got right my prediction I did yesterday. http://www.tweetdeck.com/twitter/WilliamAleman/~2H5DdReplyDelete
At least we can now change the login picture!
The RGB values are messed up, way too blue.ReplyDelete
Extension bubble's are misplaced also.
The bug icon is working overtime on this update.
I was about to ask if anyone else had been experiencing the HP-like blue screen. I'm glad to hear my vision is presumably intact.ReplyDelete
I'm also glad to see the three improvements referenced by Jay.
On the other hand, I'm still thirsting for Guest-Mode-like speed in my regular profile (especially after using canary on my dual core HP, tonight -- I almost feel like I'm using IE6 on my Cr-48, in comparison (gasp!)).
The extension crash notifications are no longer located in a yellow bar at the top of a page, but are now in a proper notification popup.ReplyDelete
i had a bit of a tweak-out session because the display color looked a bit off for me, too (yes, slightly bluish). additionally, the popup for the panelize extension shows up completely blank; i remember where the buttons i usually click are located, and i can kind of blindly stab at the blank window and get things to happen, but yeah. weird UI stuff. to the bug-reporter i go!ReplyDelete
there is a shift in the hue of the entire screen, I'm not sure If I like it or not, but it was most definitely intentional. I think that the white is now more white than it was before (comparing to a white piece of paper next to the screen)ReplyDelete
I think the cause for a lot of the regressions and problems is the fact that the GPU is awake now because I can't remember if it's awake in 11. Can someone check in about:gpu-internals?ReplyDelete
google voice extension is not workingReplyDelete
this might just be me going nuts, but i think my fan is spinning up a lot more than usual. someone mentioned the GPU being awake; maybe this has something to do with it? i bet my battery life's taking a slight hit, too; i will let the battery run down again and see what happens.ReplyDelete
I think the hue is more blue because we have been bumped up to a new version of the Chrome Browser - we are now running 12 rather than 11...ReplyDelete
gmail checker plus and google voice aren't working properly.ReplyDelete
Pretty much any extension that uses a pop-down window is broken. I've seen the content of TabCloud appear on the opposite side of the screen but it's usually just blank.ReplyDelete
Also, video performance has really bottomed out.
On a positive note, I find this build jumps onto an acceptable bssid for WPA2-Enterprise purposes very well. In the past, I often had to switch back and forth between manually setting different bssids to even establish a wireless connection.ReplyDelete
On the other hand, I'm still unable to effectively edit the /etc/init/login.conf file (so I can avoid manually running a script at login). Anyone have any advice?
Nice find on the WPA2-Enterprise setup, Jay!!ReplyDelete
I was wondering why I was having such an easy time, recently.
Sure enough, I removed all my networks (in wpa_cli), started up again, and, after selecting "do not check" for the certificate, the network clicked and now works from a cold boot!!
I feel like I've come to the end of a grueling battle. In a way, I'm almost sad it's over. I do look forward to the saved time/headaches.
On another note, I'm really looking forward to the next dev release, as I feel I've been riddled with bugs on this one (speed, online music issues, google voice extension, general wonkiness, etc.). Yet, I'm assuming the first release on a new version number can generally feel like a pretty rough ride!
Here's hoping we'll see another build before the end of the week.
I think we are going have another build before friday.ReplyDelete
New Dev update 4/14/11 http://cros-omahaproxy.appspot.com/ReplyDelete
Nice! Did you peak, LivingChains?ReplyDelete
To connect to a WPA2 network, do I have to be in dev mode?ReplyDelete
@Woopwa: No, not with the latest dev-channel updates.ReplyDelete
The reason I ask is that I have a wireless network at work that is "greyed out" and is listed as Not Configured. When the mouse rolls over that network, there is no option to connect.ReplyDelete