Nonononono, lol. I want to be able to click a button and have a list of my bookmarks pop up. Like the bookmark menu button in firefox.Jzero15 said:Yup i dont know how he missed that.
Star=Bookmark
Nonononono, lol. I want to be able to click a button and have a list of my bookmarks pop up. Like the bookmark menu button in firefox.Jzero15 said:Yup i dont know how he missed that.
Star=Bookmark
KillerAJD said:Nonononono, lol. I want to be able to click a button and have a list of my bookmarks pop up. Like the bookmark menu button in firefox.
Use AIMP instead of Winamp, same winnar interface + global keys + minimize to tray + option to see very little bar on top of everything and control it from there.Ashhong said:Alrighty, so I finally made the jump to Chrome on my PC after using it on OSX for a while now. Just a couple questions...
1. Anybody know an extension that allows me to control winamp? Firefox had FoxyTunes and it added a little bar on the bottom of the window.
CTRL + SHIFT + B will open the bookmark bar. From there you have a button for your bookmarks.KillerAJD said:Nonononono, lol. I want to be able to click a button and have a list of my bookmarks pop up. Like the bookmark menu button in firefox.
The only one OS X has is Verbatim Instant. What does Native Client mean?Angelus Errare said:New update in the Dev channel, I now habitually start checking out about:flags to see what's new. Got a couple of new things in;
Web Page Prerendering.
Speculatively prerenders complete webpages in the background for a faster browsing experience
Native Client
Enable support for Native Client
Verbatim Instant
Makes the address bar load urls as you type. Search results are shown exactly as you typed them
Jasoco said:The only one OS X has is Verbatim Instant. What does Native Client mean?
I switched over to this Dev version to try it out. If it crashes again with GIF's, I'm going back to 8 Beta again. Also, it's the latest Dev, but About says there's an update available, but won't download it. Why is Chrome's updater so fucking unpredictable?
Edit: Hey, no crashes in the Simpsons GIF thread! Maybe it's fixed? And it's even scrolling faster now. Hmmm...
Oh, you're on Chromium. I use Chrome. I tried to switch to Chromium once but they don't make it easy to switch back and forth. My profile under Chrome is not the same location as the one for Chromium and I don't want to screw anything up. So I stick with Chrome Dev or Beta depending on which one is better at the time.Sean said:I get all those options in mine (Mac dev version). Here's the build I downloaded: http://build.chromium.org/f/chromium/snapshots/chromium-rel-mac/65778/
manueldelalas said:I had a dream last night; I was seeing a Google event and they where presenting Google Chrome 9, and then they said, oh what the hell, we are also releasing Google Chrome 10 right now...
Date: Thu Nov 11 00:55:56 2010 UTC (41 hours, 28 minutes ago)
Log Message: bumping the version so we look hot, fresh, and new to our new friends
scorcho said:you have that backwards - Safari Reader borrowed code from Readability.
http://www.downloadsquad.com/2010/0...r-looks-familiar-thats-because-apple-used-op/
I dunno. You'd think Google would do this in their own browser.Windu said:yeah it works between chrome browsers on different computers. I'm talking about google.com/bookmarks
I noticed. It's amazing. I'm guessing it has something to do with acceleration? Or did they finally fix the WebKit? Either way, I never want my page to freeze up because someone posted a 1MB+ GIF again. GIF threads will finally be tolerable again.Massa said:So it turns out that upgrading to the Dev Channel version (9.0.5722.1) fixes the gif problems on Mac OS X 10.5. Why didn't I try this before...
Sorry to ask this horribly stupid question, but how do you do that?Massa said:So it turns out that upgrading to the Dev Channel version (9.0.5722.1) fixes the gif problems on Mac OS X 10.5. Why didn't I try this before...
Jasoco said:I noticed. It's amazing. I'm guessing it has something to do with acceleration? Or did they finally fix the WebKit? Either way, I never want my page to freeze up because someone posted a 1MB+ GIF again. GIF threads will finally be tolerable again.
Blu_LED said:Sorry to ask this horribly stupid question, but how do you do that?
Are those Chromium or Chrome builds? Because there is a difference when it comes to your data and which app uses what profile. (I wish there was a way to have Chromium.app and Chrome.app just use the same application support files so I didn't have to worry about accidentally using the wrong one.)Massa said:Just follow the instructions here (back up your browser data, download new app and install):
http://www.chromium.org/getting-involved/dev-channel
It must be a bug, this happens to me on Canary Build but not on DevJasoco said:Are those Chromium or Chrome builds? Because there is a difference when it comes to your data and which app uses what profile. (I wish there was a way to have Chromium.app and Chrome.app just use the same application support files so I didn't have to worry about accidentally using the wrong one.)
Edit: Sweet. It's Chrome. I'm bookmarking that page.
Another Edit: This bug bugs the hell out of me:
When you go into About, it will say "Update Available". So you click "Update Now"...
[IMGhttp://i52.tinypic.com/2chmfll.jpgIMG]
Only to have it say "Update Server Not Available". Every time. The manual updater does not work. So why is it there? At least it updates me automatically. But why even have that stupid checker if it ain't going to report correctly???
Jasoco said:Just open it from the Finder.
I don't get that bug. Can you give more detail? OS version, computer specs, browser build...
aswedc said:Just tried Chrome on a netbook and wow is it terrible on single core machines. The entire browser locks up until a page is mostly rendered, even if it is in a background tab. Firefox and Opera run circles around this.
The Chrome OS netbooks are going to have to be dual core. Hope that doesn't hurt the battery life much, as really long run times are the main reason I'm interested in getting a Chrome OS machine.
I was hoping for much closer to iPad levels. With a standard notebook battery life what's the benefit of Chrome OS over something like Ubuntu? The only thing left would be instant on.Soka said:Using Chrome on my Asus 1215n (dual core Atom w/ nVidia Ion) with Windows 7, and I tend to get a good 4-5 hours of battery life with wifi on and max brightness. With wifi off and brightness down about 2 clicks, I'm closer to 6 hours. Of course, this is a 12" laptop so it's more a "sub-notebook" than a netbook, but the point is that, the battery life is still alright despite running a dual core. I swear, the nVidia Optimus technology that is on this laptop has to add a good 2 hours to the battery life.
You can't put an li as a direct child of a li. Chrome is doing it right, you're doing it wrong.DefectiveReject said:So . . . . . Google Chrome is a bitch
I've done a web app task manager.
And each task is contained within a <ul> and each task is a <li>
each <li> contains a number of <div> tags, with each <div> being specific, i.e a subtask, or an action, and each of those things are <li> or <a> tags within those <div> tags.
Every browser displays the list properly
as they look roughly like this
<div><ul><li><div></div><div></div><div></div><li><ul><li><a></a></li></ul></li><div><li><a></a></li></div></li></ul></div>
The problem is Chrome(and chromium) are closing those bolded <li> tags off immediately (i.e. <div><ul><li></li> whereas every other browser contains everything inside those bolded tags.... .......inside those bolded tags!.
<div>
<ul>
<li>
<div></div>
<div></div>
<div></div>
<li>
<ul>
<li>
<a></a>
</li>
</ul>
</li>
<div>
<li>
<a></a>
</li>
</div>
</li>
</ul>
</div>
josephdebono said:Code:<div> <ul> <li> <div></div> <div></div> <div> <li> <ul> <li> <a></a> </li> </ul> </li> </div> <div> <li> <a></a> </li> </div> </li> </ul> </div>
That makes no sense from a syntactical point of view though.
All <li> must be directly within an <ul> or <ol> and each <li> must be closed off at some point. If you choose to not close <li> tags then every time the browser encounters an <li> and the previous <li> has not been closed off then the previous <li> will be closed at some point where the browser thinks makes sense.
Try surround your sub li in an <ol> or <ul>.
DefectiveReject said:One of my else statements had an additional </div> tag in which threw it out. i took it out and all works in all now. Strange(to me) how the rest compensated for this and chrome didn't.
It's a recent change. Chrome 6 showed the broken GAF tabs fine, Chrome 7 showed them broken as they really were.DefectiveReject said:EDIT:
One of my else statements had an additional </div> tag in which threw it out. i took it out and all works in all now. Strange(to me) how the rest compensated for this and chrome didn't.
Liu Kang Baking A Pie said:It's a recent change. Chrome 6 showed the broken GAF tabs fine, Chrome 7 showed them broken as they really were.
And yes, I agree completely with you. Just because the parsers used to be lenient is no excuse to write sloppy HTML.Liu Kang Baking A Pie said:Webkit isn't fucking around with bad HTML anymore. I like it.
hEist said:Does Chromium auto-update?
yeah i know, stupid question.
Yea, seriously, I'm getting tired of having to clear my cache to get this to work.tmdorsey said:Did anybody ever answer the question to why the "go to first unread post" only works some of the time in Chrome? Is that a problem with the forum code?
SpeedingUptoStop said:Yea, seriously, I'm getting tired of having to clear my cache to get this to work.