ThatObviousUser
ὠαἴÏÏιÏÏÎ¿Ï Ïαá¿Ï εἶ
Brettison said:
Usually when I close Chrome and then re-open it, yeah. Then it hangs when I sign in.
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
Google Chrome |OT|
- Thread starter ThatObviousUser
- Start date
Usually when I close Chrome and then re-open it, yeah. Then it hangs when I sign in.
Vanillalite
Ask me about the GAF Notebook
Exactly what happens to me, and I get a sign in error on my blank page where it shows your apps/frequent pages.Andrex said:
A Human Becoming
More than a Member
I've been getting DNS errors frequently lately on particular sites (Twitter, Facebook, Netflix and Google itself). Any ideas what could be the issue? The message at hand:
The Google said:
ThatObviousUser
ὠαἴÏÏιÏÏÎ¿Ï Ïαá¿Ï εἶ
Btw since I was on vacation I never got to post about my game's demo on the CWS. You can check it out here:
It's incomplete and lacks polish but it's a good indicator of the final game, which should be out pretty soon. Lemme know what you think.
It's incomplete and lacks polish but it's a good indicator of the final game, which should be out pretty soon. Lemme know what you think.
added_time
Member
Copernicus said:
First thing I did was disable it!
Sad to see the FUD flow like bitter tears.
Instant Pages is an awesome feature and, as a developer, I will be implementing it into future projects.
It give designers amazing control over the loading experience in their applications. Pre-load the settings page for an app, so it doesn't have to load in when users visit (usually, you want to get into your settings and out ASAP). I love it.
Instant Pages is an awesome feature and, as a developer, I will be implementing it into future projects.
It give designers amazing control over the loading experience in their applications. Pre-load the settings page for an app, so it doesn't have to load in when users visit (usually, you want to get into your settings and out ASAP). I love it.
Google doesn't determine what should load in the background. This is functionality that a developer must implement manually, including the developers of Google Search. One page can be preloaded at a time per instance of Chrome, across all tabs. Even if you have a bandwidth cap, that is trivial.Copernicus said:
So, it should be on by default, or else nobody would be able to reliably build it into their applications.
Also, it isn't as though you are actually in control of all the data flowing in and out of your machine (or need to be). Ads, background processes, usage metrics, cross-domain web services just a sliver of vital application components that are sending bytes to which you are never made privy.
Utako said:
When you query a search on google it will load the first search result. That's google preloading and fetching data from a random third party without user consent. Simply because the feature is on by default.
This should be treated more like the location where each website needs to ask you implicitly to use it rather than presume you want to use it.
It does not always load the first search result. It is based on a white list. It won't load child porn onto your machine. The same cannot be said for other websites (like NeoGAF :3).Copernicus said:
Nearly all websites fetch data from "random third parties" without user consent simply because JavaScript is on by default. PLEASE DO NOT TURN OFF JAVASCRIPT!!
Ugh. Chrome's two-finger swipe in Chrome is so buggy. It only works 20% of the time. They changed it from the three-finger it was. And when I had a BTT gesture for swiping in Chrome to go back and forth it also froze the tab in a loading loop 60% of the time too. What I get for using Dev I guess.
added_time
Member
heh.. I just realized that what I had disabled was not "Instant Pages" but "Google Instant" which just tries to alter your typed searches in real time.
I guess I'll leave the new feature enabled then.
I guess I'll leave the new feature enabled then.
Andrex said:Btw since I was on vacation I never got to post about my game's demo on the CWS. You can check it out here:
It's incomplete and lacks polish but it's a good indicator of the final game, which should be out pretty soon. Lemme know what you think.
- It could use some more polish control wise and some minor tweaks (ie. you can jump up through a platform, but you can't do it from the side, on the platform with the enemies on in the beginning)
- Controls feel a bit floaty and the game gets a framerate dip whenever text shows up.
- Awesome music.
- Music didn't load first time I loaded the first level.
- Character could use some work design wise. Running animation looks a bit wonky.
- When jumping from the side of a platform, character sometimes pops to the top/side.
RoadHazard
Gold Member
3chopl0x said:
No, that's not it. There's an Instant setting in the search section on the basic settings page (not sure what it's called since my Chrome is in Swedish, but it's the first settings page).
ThatObviousUser
ὠαἴÏÏιÏÏÎ¿Ï Ïαá¿Ï εἶ
MNC said:
Thanks for the feedback!
I am happy to say I'm aware of all these issues and hope to have them all fixed up for the final version. Which includes there being even more awesome music, if that's possible.(Any audio issues are probably Chrome's fault unfortunately, but they seem to be fixing them as time goes on so who knows - might be a non-issue for the final game too!)
This is a tip specifically for Prototype, but if you hold the down button you should be able to pass through the dotted line platforms. You just have to hold it for a bit. I'll be correcting this behavior in the final game of course.
RoadHazard
Gold Member
Shepard said:
Yeah, you're right.
RoadHazard said:
I just told you where it is, lol.
Predict network actions to improve page load performance
When you visit a webpage, Google Chrome can look up the IP addresses of all links on the webpage. Browsers use the IP address to load a webpage, so by looking up this information in advance, any links you click on the webpage will load faster. Websites can also use pre-rendering technology to pre-load the links that you might click next.
RoadHazard
Gold Member
3chopl0x said:
Yep, just read what that setting actually does. The setting existed before Chrome 13, so it's not in any way obvious that it suddently includes Instant Pages in addition to the IP address lookups it already did.
3chopl0x said:
The bolded part is new, the other stuff it already did. A bit annoying that you can't keep the IP address lookups but disable Instant Pages.
Well, now I'm torn.
I can either use the Beta (13) which has a buggy status bar popup and has scrollbars in Lion.
Or the Dev, (14) which has completely broken the Back function. (Seriously. How did they break the BACK function?) As well as other broken things like a non-working two-finger swipe in Lion.
I think I'll suffer with the Beta for a while until they fix the Dev again.
Edit: Now I'm trying Canary, which is on 15, and it seems to work good. But no Lion-specific features of course. Except for the invisible scrollbar so that's good. But no Swipe movements. Darn.
Dammit, there's way too many Chrome versions to keep switching between!
Edit: Aww, man. WTF? I can't make Canary my default browser because it's a "secondary installation"? What? Just let me make it default goddammit! It works better than the Chrome Beta and Dev do for Pete's sake! LET ME MAKE IT DEFAULT!
I can either use the Beta (13) which has a buggy status bar popup and has scrollbars in Lion.
Or the Dev, (14) which has completely broken the Back function. (Seriously. How did they break the BACK function?) As well as other broken things like a non-working two-finger swipe in Lion.
I think I'll suffer with the Beta for a while until they fix the Dev again.
Edit: Now I'm trying Canary, which is on 15, and it seems to work good. But no Lion-specific features of course. Except for the invisible scrollbar so that's good. But no Swipe movements. Darn.
Dammit, there's way too many Chrome versions to keep switching between!
Edit: Aww, man. WTF? I can't make Canary my default browser because it's a "secondary installation"? What? Just let me make it default goddammit! It works better than the Chrome Beta and Dev do for Pete's sake! LET ME MAKE IT DEFAULT!
RoaringHawk
Member
Jzero15 said:
HarryDemeanor said:
Ok, so I still have it installed on my old HDD. Is there a way I can get it in a backup and re-install it? Will post a link to it if possible.
ThatObviousUser
ὠαἴÏÏιÏÏÎ¿Ï Ïαá¿Ï εἶ
wrowa said:
https://chrome.google.com/webstore/search?hl=en-US&q=neogaf
Extensions I made:
Quick Reply
Image Upload
Messages
Smilies
Well this is an interesting turn of events.
The current version of Canary has a proper full working Lion Fullscreen mode.
It actually works. And doesn't crash or freeze or look stupid. What happened? I thought they said it'd be a while? I guess it'll be a while before they trickle it into the stable version as Canary's currently on 15 and Stable's on 13 with Dev being on 14. Still. I'm going to test it some more, but I hope I'm not presumptuous when I say HALLE-FRICKIN-LUJAH!
The only problem is how fast the menubar appears. So if I overshoot a tab, I have to move back to get the menu to go away. But it's not a big deal if I don't care.
Also interestingly enough, I haven't found any show-stopping bugs in the current Canary yet that are forcing me to go back to Chrome Proper.
Hmmmmm....
Edit: Also, the old "no toolbar" Fullscreen mode is now called "Presentation mode" and is separate from regular fullscreen mode. Holy fuck these people are serious about Chrome on Lion. I tell you what.
Edit: AND on OS X it also bounces the Downloads icon when a file is finished like Safari does. (Too bad I don't use the Downloads folder. I use the Desktop. Also sorry if this has been there for a while.)
The current version of Canary has a proper full working Lion Fullscreen mode.
It actually works. And doesn't crash or freeze or look stupid. What happened? I thought they said it'd be a while? I guess it'll be a while before they trickle it into the stable version as Canary's currently on 15 and Stable's on 13 with Dev being on 14. Still. I'm going to test it some more, but I hope I'm not presumptuous when I say HALLE-FRICKIN-LUJAH!
The only problem is how fast the menubar appears. So if I overshoot a tab, I have to move back to get the menu to go away. But it's not a big deal if I don't care.
Also interestingly enough, I haven't found any show-stopping bugs in the current Canary yet that are forcing me to go back to Chrome Proper.
Hmmmmm....
Edit: Also, the old "no toolbar" Fullscreen mode is now called "Presentation mode" and is separate from regular fullscreen mode. Holy fuck these people are serious about Chrome on Lion. I tell you what.
Edit: AND on OS X it also bounces the Downloads icon when a file is finished like Safari does. (Too bad I don't use the Downloads folder. I use the Desktop. Also sorry if this has been there for a while.)
Just noticed a pretty cool feature in Chrome, not sure if it's been there since forever.
If you copy just some text to your clipboard, right clicking the URL bar will give you a "Paste and search" option instead of just the regular "Paste and go" option you get when you copy a URL.
If you copy just some text to your clipboard, right clicking the URL bar will give you a "Paste and search" option instead of just the regular "Paste and go" option you get when you copy a URL.
Just a usability thought:
When Chrome is in Fullscreen, whether it's Mac, Windows or Linux, the tabs should go all the way to the top of the screen. Or at least their "active area" should. It's called "Fitt's Law". It should put the tab click area at the very edge of the screen so I can't overshoot it with my mouse. Right now it wastes 10 pixels of space up there. Also, if it's OS X, it should make sure the menu bar doesn't appear right away.
When Chrome is in Fullscreen, whether it's Mac, Windows or Linux, the tabs should go all the way to the top of the screen. Or at least their "active area" should. It's called "Fitt's Law". It should put the tab click area at the very edge of the screen so I can't overshoot it with my mouse. Right now it wastes 10 pixels of space up there. Also, if it's OS X, it should make sure the menu bar doesn't appear right away.
ThatObviousUser
ὠαἴÏÏιÏÏÎ¿Ï Ïαá¿Ï εἶ
That's how it works on Windows.
<3 Windows.
<3 Windows.
That's Maximized. Not fullscreen. Fullscreen is a bit different. What does it do on Windows when you use Chrome's Fullscreen option? Fake edit: Well now. Windows Chrome doesn't have a Fullscreen option? What gives? I guess Fullscreen must be an OS X thing. Which is interesting because Fullscreen makes the window take up the WHOLE screen including removing the menubar and Dock. Does Linux have Fullscreen?Andrex said:
On the Left is Windows with Maximized window. On the Right is OS X with Fullscreen.
You get more pixels in OS X/Fullscreen. And would get even more if they removed the top buffer. Of course, this is Chrome Canary so hopefully someone realizes this before release. But I assume they kept the buffer there to prevent activating the menubar. Which is why it should have a delay. But I suspect the menubar slide delay is controlled by OS X and not the app developer.
Edit: Even Firefox has Fullscreen in Windows. Chrome MUST have it. But I can't find an actual menubar in Chrome on Windows. Also, ChromeOS has Fitt's Law, but the tabs still have a buffer, though it's smaller than OS X Fullscreen.
Jasoco said:That's Maximized. Not fullscreen. Fullscreen is a bit different. What does it do on Windows when you use Chrome's Fullscreen option? Fake edit: Well now. Windows Chrome doesn't have a Fullscreen option? What gives? I guess Fullscreen must be an OS X thing. Which is interesting because Fullscreen makes the window take up the WHOLE screen including removing the menubar and Dock. Does Linux have Fullscreen?
Windows with Maximizing:
OS X with Fullscreen:
You get more pixels in OS X. And would get even more if they removed the top buffer. Of course, this is Chrome Canary so hopefully someone realizes this before release. But I assume they kept the buffer there to prevent activating the menubar. Which is why it should have a delay. But I suspect the menubar slide delay is controlled by OS X and not the app developer.
Edit: Even Firefox has Fullscreen in Windows. Chrome MUST have it. But I can't find an actual menubar in Chrome on Windows.
"Full Screen" on windows is just hiding the taskbar. Each program then changes how it wants....chrome hides the taskbar if I recall correctly. I'm on my cr48...so I have no f11 key to try, lol.