Originally Posted by Forrest
It's in the release notes.
What release notes? All the download contained was two applications, WebKit.app and Drosera.app, and the pre-set start page is a static remote page.
Considering this board is vB, and those features seem to work fine, IMHO it must be an issue with vB that has since been fixed.
That's a possibility, but IMHO, it's still worth investigating for a variety of reasons:
- It might not have been a formal bug with vB, but simply an issue with code that just evolved away. That the bug is no longer on display doesn't mean it's not still a bug, and the bug could be with OW. Heck, the code may have even been changed to work around an OW issue (unlikely, I know).
- Even if it is a bug specific to only that version of vB, it's quite likely that a good number of sites are still running that version. Thus, if the work-around is simple enough, it may be worthwhile for the Omni folks to go ahead and do it.
- It may be a generic enough issue that it'll appear on other (non-vB) sites, as well.
- Finally, the problem is present only in OW. The site works fine in the latest release of Safari, it works fine in the latest nightly build of WebKit, and it works fine in Firefox. This pulls the finger in the direction of OW. However, I've not tried the site in the release version of OW nor in the older version of WebKit upon which SP16 is based, so I can't say definitively whether the finger points at OW. Specifically, it's possible that the site won't work in any version of OW (still a problem), or that the problem was just a temporal issue with a handful of past WebKit nightly builds (no longer a problem).