Between Many Tricks and this blog, I spend a lot of time in browsers. Most of the time, I use Safari, but I do occasionally work in Chrome and Firefox, too—most often to check how a page looks or functions.
I keep my “permanent” bookmarks in Safari, and don’t presently use any sort of cross-browser sync. (I used to use one, but had a lot of trouble with duplicates, so I stopped.)
I wanted a way to open a limited number of URLs in either Safari (if that’s what I was in, or if I wasn’t in a browser), or in the frontmost browser, if that browser were frontmost. I could just create the subset as bookmarks in each browser, but if I wanted to add or remove a page from the list, I’d have to do so multiple times.
In the end, I came up with a set of Keyboard Maestro macros that do exactly what I want. I access my short list of multi-browser URLs via Keyboard Maestro’s pop-up palette, as seen at right.
This appears when I press ⌃1; after that, a single digit opens the desired URL. But how does it know whether to open the URL in Safari or one of the other browsers? It takes one helper macro, then one macro for each URL that I want to open in this manner.
This is another oldie but goodie from Mac OS X Hints, explaining how to enable the Debug menu in Safari. To do that, quit Safari, open Terminal, paste the following line, and press Return:
defaults write com.apple.Safari IncludeInternalDebugMenu 1
When you relaunch Safari, you’ll have a (really long) Debug menu on the far right of Safari’s menus. And just why might you want a Debug menu in Safari? Kirk McElhearn offers up one good reason:
Auto-play videos suck. They use bandwidth, and their annoying sounds get in the way when you’re listening to music and open a web page. …
But you can stop auto-play videos from playing on a Mac. If you use Chrome or Firefox, it’s pretty simple, and the plugins below work both on macOS and Windows; if you use Safari, it’s a bit more complex, but it’s not that hard.
In Safari, they key is the Debug menu, as Kirk points out. Go to Media Flags and select (activate) Disallow Inline Video, and that should be the end of auto-playing video. See Kirk’s blog post for ways to do the same in Firefox and Chrome.
Beyond auto-play video, though, there’s lots to geek out about in the Debug menu…
When I posted my 787 takeoffs and landings video, I ran into a weird problem: When embedded here, the video would play in Safari at 4K (2160p), but when viewed on YouTube, the max resolution available was 1440p. After failing with web searches, I asked Twitter about it…
…but didn’t hear anything back. I pretty much gave up on the issue until today, when I stumbled across this article, which describes the exact problem I’m having. The summary of the article describes both the problem and the apparent cause:
What appears to be Google’s shift to the VP9 codec for delivering 4K video on the YouTube homepage is preventing Safari users from watching videos uploaded to the service since early December in full 4K resolution, but not from viewing webpage-embedded videos in the same resolution.
Bingo! Google seems to now be using the open and royalty-free VP9 codec for 4K videos viewed on its YouTube site, but reverts to the H264 codec when those same videos are embedded on other sites.
Note that this issue only affects videos uploaded after December 6, 2016:
Videos uploaded to the service prior to Dec. 6 in 4K resolution can still play back in full 4K resolution on Safari from the YouTube homepage.
I was curious about which macOS browsers this issue affects, so I thought I’d do a little experiment…
Yesterday I ranted on Twitter about CNN’s redesign:
This led to an exchange with a CNN staffer, and a couple people saying “me too!” But it felt it a bit unfair to criticize without specific data. So this morning, I gathered the data, and can now quantify my distaste for the new design.
I compared the current CNN homepage to the latest available on the Internet Archive, calculating how the space was used for each version of the site. The results were eye opening in many ways.
The new CNN design displays half as many clickable stories in the same space, with an image that takes 20% of the available screen, and sucks down over 20% of my CPU just to display its home page. Read on for the gory details.
Note: This follow-up entry details my post-CNN news sources and reading methods.
Please leave feedback for CNN
if you share my frustrations.Thanks to Raymond for posting this address in the comments.
Safari in Yosemite is a familiar yet new beast. Among the interface changes, I really didn’t like the way the URL bar behaved. In particular, these things bugged me:
- Not being able to see the full URL.
- The width of the URL entry box.
- The drop-down that appears when you click in the URL bar (when you have a page loaded).
Thankfully, the fixes for these three issues are easy, if not completely obvious.
Full URL not visible in URL bar
By default, Safari truncates URL to just the base “dot” address, regardless of where you are on a site. So if you’re reading my hint about using a dark Dock, Safari’s URL bar will display this:
But you’re really on this page:
If you prefer knowing where you are in the site hierarchy at all times, the fix is simple. Open Safari’s Preferences, go to Advanced, and add a checkmark next to “Show full website address.”
The URL box will now show the full URL of the page you’re viewing. Of course, that will lead to a second problem—the URL box isn’t large enough to display much of the extended URL. Thankfully, that too is an easy fix.