Version 6.0 test

Friday, September 27, 2024

Trust Prompt — Whoops! That last change was triggering the trust prompt far too often. Backing it out for now.

Wednesday, September 25, 2024

Trust Prompt — When a web page’s certificate isn’t trusted (e.g. for a self-signed certificate), OmniWeb once again presents a trust prompt which allows you to inspect the certificate details and choose whether to trust and load the page.

Thursday, September 12, 2024

System Requirements — Updated system requirements, supporting macOS 11 Big Sur through macOS 15 Sequoia.
Unread Bookmarks Crash — Fixed a crash on launch encountered when a bookmark is unread.

Friday, July 19, 2024

Software Update — Software Update now supports app updates that use the more compact .txz archive format.

Tuesday, April 24, 2024

Software Update — Fixed software update on systems where System Integrity Protection (SIP) has been disabled. Our audit check for memory tampering was failing on systems with SIP disabled, causing it to report an abort the process with an error message saying “OSUInstallerService was invalidated from this process”.

Friday, September 15, 2023

macOS 13 Compatibility — Updated OmniWeb for compatibility with macOS 14 (Sonoma).

Wednesday, April 12, 2022

Keyboard Beeps — Fixed beeps that would occur when holding down scrolling keys.

Sunday, October 23, 2022

Location Bar — The nonfunctional location field in the Navigation toolbar has been removed. Instead, use the Location Bar (see View > Toolbars > Location Bar).
Title and URL Updates — Fixed a bug where the window title and URL wouldn’t update when navigating github.com (and presumably other single-page applications).

Monday, August 2, 2022

macOS 13 Compatibility — Worked around a crash encountered when creating a new workspace on macOS 13 (Ventura) beta 4 (filed with Apple as FB10929854).

Monday, June 13, 2022

Browser Identity — Updated OmniWeb’s user agent string to identify as Safari 15 rather than as a generic WebKit browser, so it works better with websites like Slack. Removed the custom JavaScript identity preferences (which haven’t been used since updating to WebKit 2).
Build Toolchain — OmniWeb is now built with Xcode 13.4 using the macOS 12 SDK (and has been updated for compatibility with the latest beta tools and SDK).

Sunday, November 21, 2021

Browser Identity — Updated OmniWeb’s user agent string to identify as a generic WebKit browser rather than OmniWeb, which fixes scrolling with the scroll wheel on the Synology admin interface.

Friday, November 19, 2021

Failed Loads — Failing to load a page will now report the failure (such as “A server with the specified hostname could not be found") rather than failing silently.
Untrusted Sites — Loading an untrusted site will once again prompt to ask whether you’d like to load the site anyway.

Tuesday, November 10, 2020

M1-powered Macs — OmniWeb is now a native Universal app on M1-powered Macs.

Friday, July 31, 2020

Frames and JavaScript — Whether JavaScript is disabled in a particular frame is now based on whether it was disabled when the main frame loaded, rather than determining the JavaScript settings for each child frame based on the URL being loaded within that frame. This means that the entire webpage will consistently have JavaScript enabled or disabled, rather than potentially having it enabled in some frames and disabled in others.

Tuesday, July 21, 2020

Reload With JavaScript Enabled — Added a menu item to reload the current page with JavaScript temporarily enabled. (Useful when you want to turn off JavaScript by default, but need to temporarily turn it back on to use a page. If you’d prefer to enable JavaScript permanently for a website, use site preferences instead.)

Friday, July 3, 2020

macOS 11 Compatibility — Implemented support for catching crashes on macOS 11 (Big Sur).
Disable JavaScript — Reimplemented the site and global preference for enabling and disabling JavaScript. (This setting requires macOS 11.)
Authentication Prompts — Reimplemented support for authenticating with a web server.

Sunday, February 16, 2020

Download filenames — When picking a unique filename for a download, OmniWeb will no longer break up a version number to insert its own number. (To pick an old example from when this bug was originally filed, a second download of OmniWeb-5.5.dmg will be named OmniWeb-5.5-1.dmg rather than OmniWeb-5-1.5.dmg.)
Downloads crash — Fixed a bug where opening a download in a new tab would crash.

Thursday, January 9, 2020

Downloads — Implemented support for downloading files from WebKit’s external processes (rather than trying to restart the download within OmniWeb, which only worked for sites that could repeat the download at the same URL without authentication). This should help with downloading any sort of protected content, including dynamic “blob” content generated by a web page such as PDF reports.

Sunday, January 5, 2020

History — Restored support for persistent history and Spotlight indexing of visited pages. (Happy New Year!)

Thursday, December 19, 2019

Crash — Fixed a crash sometimes encountered when Command-Clicking on a link which had trouble loading.

Thursday, December 12, 2019

Saved Passwords — Updated the password autofill logic so it no longer interacts with the pasteboard.

Monday, November 25, 2019

Saved Passwords — Updated the password autofill logic to be compatible with more websites.
Save — Reimplemented support for saving the original source for a page.
View Source — Hooked up OmniWeb’s ancient source viewer/editor. (Not sure whether this is worth keeping; in general, I’d recommend using the Web Inspector instead.)

Sunday, November 24, 2019

Print — Reimplemented support for printing web pages (using the upcoming public API when available, otherwise falling back on the existing private SPI).
Save — Reimplemented support for saving web pages to a .webarchive file (using the upcoming public API when available, otherwise falling back on the existing private SPI).
JavaScript Prompt Crash — Fixed a crash encountered when JavaScript prompted for input from a page which had a URL without a hostname.

Thursday, November 21, 2019

Synchronized Passwords — By default, saved passwords will now be synchronized through the iCloud keychain. There isn’t a visible preference setting for this (at least not yet), but you can disable this by setting the ShouldSyncPasswords preference to false using this command (in Terminal): defaults write com.omnigroup.OmniWeb6 ShouldSyncPasswords -bool false.
Saved Passwords — Stopped saving two copies of every saved password to the keychain, since synchronized passwords don’t seem to run afoul of the Catalina bug where keychain entries disappear.
Saved Passwords — Saved passwords will now detect associated account name fields that are more distant (in the document object model) than other fields. (It would previously only detect account name fields that were at least as close as any other fields, including hidden fields.)

Sunday, November 17, 2019

Saved Passwords — Saved passwords will now detect associated account name fields that specify their input type as email.
Lost Passwords — We now save two copies of saved passwords to the keychain to work around a regression in Catalina where Internet Password keychain entries disappear from the login keychain (FB7444659).
Crash — Fixed a crash encountered when saving a password without an associated account name.

Wednesday, November 13, 2019

Bookmarks — Hooked up the bookmarks view and editor once again, and made it look a bit less out-of-place in Dark Mode. (Need to do a full pass through all our icons in both Dark and Light mode at some point, they’re all looking pretty dated!)
Crash — Fixed a crash encountered when following a link which targets a new tab or window.
Crash — Fixed a crash encountered when a tab couldn’t determine its current address.

Monday, November 11, 2019

Browser Identity — Updated OmniWeb’s default user agent string to identify as a variant of Safari 13 rather than Safari 7.
Home Page — Updated the home page: the search field now uses DuckDuckGo, and the various links to omnigroup.com now use https.
Browser Prompts — Fixed a regression where prompts from web pages were being ignored (and effectively cancelled) rather than presented.
App URLs — URLs belonging to other apps (such as Twitter authentication links) will once again be handed off to the system to open.
OmniWeb URLs — Hooked up omniweb: URLs (such as the home page) so they get handled within the app rather than doing nothing—or worse, handed off to the system.

Sunday, November 10, 2019

WebKit 2 — OmniWeb is now based on WebKit 2 and requires Mojave or Catalina. This will be a great thing in the long run, but it also means that a lot of OmniWeb’s earlier features are no longer implemented—and some will be impossible to implement. I’ve still been using it as my daily browser, but there are a number of areas of functional regression, such as: downloads don’t always hand off properly (API request filed in WebKit’s bug database); it’s no longer possible to see the target of a link by hovering the mouse over it (API request filed). Some features that probably won’t be coming back include the source editor (instead, use the web inspector which allows resources to be debugged and edited) and the activity monitor (WebKit doesn’t provide the level of control we used to have for this). I haven’t dug into what might be possible in the way of cookie management yet. The biggest daily pain point for me over the past year or so has been the total lack of any sort of password management; as of today, some very crude management is now in place—see the Password AutoFill note below—which is why I’ve decided these builds might be worth making available to testers again.
Dark Mode — OmniWeb now supports Dark Mode.
Password AutoFill — Some very crude password autofill support is finally back in place. When OmniWeb detects that you’re editing a password field, its background turns yellow. In that field, press Control-S to save the login/password you’re editing to the keychain, or press the Down Arrow key to autofill a login/password from the keychain.

Tuesday, October 24, 2017

Authentication Prompt Crash — Fixed a crash encountered whenever an authentication prompt was cancelled.

Monday, September 18, 2017

Sierra compatibility — Fixed a crash which was introduced by building OmniWeb with Xcode 9 using the 10.13 High Sierra SDK.

Sunday, July 16, 2017

El Capitan and Sierra compatibility — Recent test builds of OmniWeb (after r291920) were failing to launch on 10.11 El Capitan and 10.12 Sierra due to a linker bug in Xcode 9 beta 3. Worked around the bug so OmniWeb should work once again on shipping versions of the operating system. (That said, there are some really great changes coming in 10.13 High Sierra that will finally make it possible for OmniWeb to migrate from WebKit 1 to WebKit 2, so at some point these builds are going to drop support for earlier versions of the OS. But that day isn’t today.)

Sunday, July 9, 2017

Window Size Hint — Resizing a browser window will now display a hint showing the size of the web page (in pixels) so you can easily see when you’ve resized the window to 800x600, 1280x1024, etc.
Tab Sidebar — When space is available on the screen, opening and closing the tab sidebar will no longer disrupt the layout of your current web page: it will grow and shrink the window rather than growing and shrinking the web page. (Also, opening the tab sidebar is now animated so that the change is not quite so jarring even when the layout does have to change.)

Sunday, June 18, 2017

Tab Sidebar — Drawers are deprecated in High Sierra (and were causing some misbehaviors like sending the parent window to the back every time you opened a drawer), so this seems like a good time to make a long-overdue change: tabs now live in a sidebar rather than a drawer.
High Sierra compatibility — Tab thumbnails generally draw correctly now on High Sierra (instead of showing empty or clipped content).
Tab Drops — You can once again drop tabs directly onto the main area of a browser window to move or copy those tabs to that window.

Tuesday, June 14, 2017

High Sierra compatibility — Fixed some crashes encountered on beta builds of High Sierra when displaying the completions for an address and when opening the print dialog on a Mac with a Touch Bar.

Welcome to OmniWeb 6

System Requirements — Current test builds of OmniWeb 6.0 require El Capitan (macOS 10.11) or later. (The current development target is High Sierra, i.e. macOS 10.13.)

What else is broken? — Please let us know if you notice regressions which aren’t in the “Not Ready” list below.

What We Know is Not Ready

Site Preferences — Web pages should honor the “override page styles” site preference. There may be a bunch of other styles that aren’t yet working.
Proxy Server Authentication — Proxy server authentication hasn’t been reimplemented yet.

If you encounter some other issue with these builds, please use Send Feedback in the OmniWeb menu or email omniweb@omnigroup.com to let us know!

Earlier Changes

Tuesday, September 6, 2016

Updated Memory Architecture — Over the holiday weekend, rewrote a bunch of low-level code to use the weak references provided by modern Objective C’s Automatic Reference Counting rather than our hand-rolled weak reference implementation from two decades ago. Going forward, this will make this code much easier to maintain, but since this touched a lot of code in fundamental ways it may take a little while to sort out new issues introduced by these changes. I’ll keep my eye on the crash reports and fix new things that I see crop up, but if you want a reasonably stable from before these changes went into place I recommend using r268795.

Thursday, September 1, 2016

401 Crash — Fixed a crash encountered when a web page denies access with a 401 Unauthorized error but doesn’t provide any authentication methods. (This typically happens when reconnecting to a web site which requires a login through a web form rather than through HTTP authentication.)

Tuesday, August 9, 2016

Sandboxed Public Test — Turned Public Test back on. If you’re upgrading from a pre-sandboxed copy of OmniWeb, you may need to migrate your older bookmarks, favorites, and workspaces by hand from ~/Library/Application Support/OmniWeb 5 to your sandboxed container in ~/Library/Containers/com.omnigroup.OmniWeb6/Data/Library/Application Support/OmniWeb.

Sunday, August 7, 2016

Sandboxing — Finished with the last of the major regressions from introducing sandboxing. There may be a few remaining issues (if you weren’t syncing your bookmarks and favorites, you’ll have to copy them into place by hand) but OmniWeb seems fairly usable once again. Will do a bit more internal testing before making public test builds available again.

Tuesday, August 28, 2015

Sandboxing — Enabled sandboxing. Unfortunately, this introduces a number of regressions that we don’t have time to fix at the moment. Turning off public test builds so this doesn’t cause issues for people outside Omni.

Tuesday, June 23, 2015

Performance — Improved scrolling performance on El Capitan.

Tuesday, May 26, 2015

Untrusted Server Certificates — OmniWeb will once again ask for permission to continue connecting to servers with untrusted certificate chains, rather than immediately giving up with the message “The operation couldn’t be completed. (OSStatus error -9807.)”

Sunday, January 4, 2015

Preference Registration — Updated OmniWeb’s preference registration to match changes to our shared frameworks made in early December. This fixes the recent regressions with preferences, autocomplete, opening new windows on launch, and many other issues.

Remainder of 2014

Broken builds — No other intentional changes were made to OmniWeb after October 2, but some changes to our shared framework logic did affect OmniWeb. In particular, a change to the dynamic loader on December 12 broke OmniWeb’s preference registrations which in turn broke many of its features which rely on those preference registrations.

Thursday, October 2, 2014

Yosemite — Some rendering and stability issues on Yosemite should now be fixed; OmniWeb 6.0 now requires Yosemite.

Tuesday, July 22, 2014

Resource Unavailable — Fixed a common cause of “Resource Unavailable” errors: they were being triggered by HTTP redirects to a malformed URL (e.g. to URLs with space characters which should have been quoted in the URL as “%20").
Yosemite compatibility — Fixed some “Layout still needs update” errors introduced by autolayout changes to the NSView API.

Monday, May 12, 2014

Bundle Uploads — Added support for automatically generating a zip file when uploading bundles (such as OmniOutliner documents).
Stability — Good news! After 24 hours, I think it’s safe to conclude that our most common crash is finally fixed! (Normally we would have seen hundreds of those crashes in that time; in the last 24 hours there have been none.)
File Uploads — Reimplemented support for uploading files.

Sunday, May 11, 2014

Stability — May have finally tracked down the crash in _CFURLResponseCreateCopy(). Then again, it’s never been easy to reproduce on demand so it’s hard to know for sure until we try this fix for a few days and see whether any more crashes in that location get reported. (Thank you for sending in those crash reports!)
Fragmented gzip-encoded content — Some websites which send compressed content have been rendering poorly in OmniWeb 6 since last December, and if you checked the Error Log you would see a message saying “failed to read from gzip decoding stream” and “inflate: buffer error”. It turns out this “buffer error” is an expected state for the gzip-decoding library; we just needed to provide more buffer space and resume decoding. This is now fixed.
NSURLErrorDomain error -999 — When Omni Software Update gets an error while trying to load its release notes, it will now log a message to the console rather than displaying a modal error dialog. Also, it won’t ever bother logging a message if the error is NSURLErrorCancelled (-999).

Sunday, Jan 5, 2014

Stability — Continued work on tracking down the crash in NSURLCache. Found a WebKit preference setting which was frequently updating the cache size as pages from different sites loaded, which may have been the trigger for the crash.

Wednesday, Jan 1, 2014

Memory Leak — Fixed a memory leak encountered when closing a window.

Sunday, Dec 29, 2013

Load Blocked Stylesheets — “Load All Images” will now load linked stylesheets as well as images.
URL with query but no path — Fixed a bug where URLs with a query but no path (e.g. “magnet:?xt=") would get parsed into a URL with an empty path (e.g. “magnet:/?xt=").
Load All Images — “Load All Images” and the “unloaded images” status bar indicator both work once again.
Stop — The Stop button and the spinning page load indicator should work again.
Delete key in Bookmarks — The Delete key works once again in Bookmarks.

Friday, Dec 27, 2013

Encoding crash — Fixed a crash encountered when a website indicated that its content was encoded with the identity encoding.

Thursday, Dec 26, 2013

Middle-Click — Middle-clicking on a link will open it in a background tab.
Construction tape — Removed the construction tape from the title bars of browser windows.

Tuesday, Dec 24, 2013

Authentication crash — Fixed a crash encountered when trying to purchase music from play.google.com.

Monday, Dec 23, 2013

Authentication — HTTP authentication with a webserver should now be working properly whether or not you choose to save the password in the keychain.

Wednesday, Dec 11, 2013

Crash — Fixed a crash encountered when there was an issue decoding data from a compressed HTTP response. Thanks for all the crash reports!
Fragmented gzip-encoded content — Some gzip-encoded content wasn’t loading properly depending on how its packets were split up for transmission across the wire.
Gzip-encoded content — Unexpected gzip-encoded content should once again decode properly, rather than yielding a crash (right after logging an “Unknown or unsupported data encoding” error).

Tuesday, Dec 10, 2013

Do Not Track — Added a security site preference which asks a website not to track you. Please bear in mind that this does not prevent a website from tracking you, it’s simply a request. In OmniWeb this Do Not Track request is sent by default, but as with all security site preferences you can change this default either on a site-by-site basis or globally.
Crash Logs — Updated crash reports to include the last few seconds of information from the OmniWeb error log, since those details might include a vital clue as to why OmniWeb crashed. (Note: as always, you can review and edit your crash details before sending in the report.) You can turn off this reporting by turning off the “Copy log to crash reports” checkbox in the Error Log window.
Crash — Fixed a crash encountered when loading from an empty URL.
Crash — Fixed a crash encountered when performing HTTP authentication with a website.

Sunday, Dec 8, 2013

Gzip-encoded content — Fixed a regression introduced last week where gzip-encoded content wasn’t being decoded properly. The most obvious ramification of this was that stylesheets were breaking on a number of popular websites.
Crash — Fixed the zombie crash introduced in today’s earlier build (r200159).
Crash — Fixed a crash encountered when trying to view the source of a page which failed to load.
Crash — Fixed a crash sometimes encountered when loading a page with lots of resources.

Tuesday, Dec 3, 2013

Safari 7.0 compatibility — You can now tell OmniWeb to identify itself to a website as Safari 7.0 (under Site Preferences -> Other).
Scripts Menu — Removed the obsolete Scripts menu. (It’s been replaced by the global script menu bar item which can be enabled in AppleScript Editor’s preferences.)
Cookies Regression — Fixed a regression in yesterday’s update which caused all cookies to be lost when quitting the app.
JavaScript Spoofing — When you ask OmniWeb to identify itself as another browser, this setting will now affect JavaScript identification (via the navigator object) and not just HTTP identification. (This means that if you tell OmniWeb to identify as Safari 7.0, it can once again use icloud.com.)
Global Site Preferences — Global site preferences work once again.
Redirect Loop — Fixed an issue with the rewritten HTTP code which could cause a redirect loop due to OmniWeb following the original HTTP standard behavior for 302 rather than the revised-to-match-other-browsers standard.

Monday, Dec 2, 2013

Flash Plug-In — Flash plug-in content renders once again.
Independent Cookies — OmniWeb’s cookies are once again completely independent of Safari’s, and all of OmniWeb’s cookie management controls should once again be working properly. (You should now be able to use OmniWeb and Safari to simultaneously log into different accounts on the same website.)
Show HTTP Requests — The “Show HTTP Requests” switch in the Console once again logs all HTTP requests to/from a server.
Location Bar — Pressing Return in the Location Bar will once again return focus to the web page, auto-hiding the Location Bar when appropriate.
Software Update — Moved OmniWeb over to the test software update track so it will see new builds of itself.

Sunday, Nov 10, 2013

Flash Plug-In Crash — Though Flash plug-in content doesn’t render properly yet (it just shows up as a black square), it no longer crashes OmniWeb 6.

Friday, Oct 25, 2013

System Requirements — OmniWeb 6 now requires Mavericks (10.9).
App Icon — OmniWeb 6 has a new app icon.
Text Zoom — Text Zoom has been re-implemented.
Energy Use — Enabled automatic graphics switching to reduce energy use.

Monday, May 20, 2013

64-bit — OmniWeb is now 64-bit.
Current WebKit — OmniWeb now uses the system version of WebKit.