On our home network we have a Windows PC (with printer attached), a Chromebook, a Linux netbook used as a media centre, and, intermittently, an Android phone. Visitors often bring their own devices too. The idea of configuring the network and all of these clients to be able to print to the Windows PC’s printer sounds pretty terrifying and, even were I to achieve it, printing would only be possible from within the local network.
Sometimes you need to leave your computer, perhaps at short notice, and you’ve already built up a number of open tabs. If you don’t have Google Chrome configured to carry on where you left off when opening a new session, then closing the browser will lose those tabs and force you to remember and re-open them later to continue working.
This is another simple tip that most Chrome users will already know about.
When you have multiple tabs opened, you can detach a single tab as a separate instance of the Google Chrome browser. This allows you to group related web pages or apps and run each group in a separate browser instance – maybe on a separate desktop workspace, or even on a separate monitor. To ‘extract’ a tab in this way, just drag the tab away from the tab bar:
Chrome’s Pin Tab feature has been around for some years, but I’m amazed at how many people are still unaware of it – or have forgotten about it – so today’s post is a quick overview.
This tip will work on any version of Google Chrome (as far as I know) but is mainly aimed at those who, like me, use a ChromeOS device such as a Chromebook.
I often find I want to temporarily save and manipulate a short snippet of plain text – maybe some program code, or a short message I want to share to various social media sites. I might want to make some minor edits, and then keep the text on hand to use later.
I’ve lost count of the number of times I’ve closed a tab in Google Chrome only to wish, a few moments later, that I’d left it open.
If this happens to you too, remember that you don’t need to open a new tab and then scrabble around looking for the URL of the page you were viewing.
“What’s making that terrible noise?!”
Sometimes your browser tries to help, but instead does something annoying or counter-productive. One feature of Chrome that fits into that category for me is the auto-playing of multimedia files when I’m browsing the web; it can cost you bandwidth usage, too.
Chrome, like most other browsers, caches content from websites you visit in order to improve performance.
Sometimes, though, things can go wrong and cause you to want to dump the cached data. This is especially common when developing website pages or web applications, but may also be necessary in other situations where you want to be sure you’re displaying up-to-date data from the server.
I’m guessing that most people who use Google Drive and associated Apps will be doing so via Google’s Chrome browser.
Chrome is written to be a robust, fast and efficient browser. I’m not going to venture too deeply into the geeky underworld of how it actually works (you can always check out the source code of it’s open-source sister, Chromium, if you like), but one of the techniques it uses to prevent one hinky page from crashing the whole browser is to separate different tasks into separate processes. This is like having a number of separate programs all running at once, each looking after its own resources (such as memory allocation, calls to the BIOS, and so on). There’s a process for each tab you have open, and one for each extension you have activated.