Note: Don't use the amework inside webkit.app, it won't load properly use a relinked app. Just use an already relinked application LepWK and go to application LepWK.app/Contents/frameworks/, then copy amework, libgcc_s.1.dylib, libstdc++.6.dylib and libsqlite3.dylib to OmniWeb.app/Contents/frameworks/.
SHIIRA WEB BROWSER MANUAL
It doesn't even require manual relinking with install_name_tool : OmniWeb has a mechanism that prioritizes loading from its own frameworks folder before /System/Library/Frameworks/. The droplet refuses to relink OmniWeb to leopard-webkit, but if it just loads the security framework from lepWK it will support TLS 1.2 as well. It has extensive per-site preferences, ad-blocking, a very responsive UI, starts up ridiculously fast, (to me) feels more OS X-native than safari, and is badly out-of-date with current web standards. In terms of overall out-of-the-box feature set and light footprint, OmniWeb still is my rank #1. It has its own custom webkit, webcore, javascriptcore integrated inside its. There's another webkit browser that doesn't get relinked by the leopard-webkit droplet for different reasons: OmniWeb. It also means once google/youtube follows this trend, quicktime and other OS X-native players won't read videos directly from a youtube URL anymore (except rtsp:// as far as it goes). Among others, Fluid instances, Sunrise, (IIRC) demeter/shiira, and likely web pages displayed within the dashboard behave this way. That said, some "webkit shells" browsers are left out by this because they do not directly link or interact with the security framework and leave it to other system frameworks. At this point it enables support for TLS up to 1.2. iCab, Safari, Stainless, Roccat and others can get an updated security framework by means of leopard-webkit recent versions. The system frameworks in 10.4 and 10.5 support up to TLS 1.0. This hit Webkit-based OS X browsers as well. For example I can no longer connect to any of WikiMedia's domains I regularly used (Wikipedia, wiktionary, etc), nor most non-google search engines (alas, duckduckgo) using Classilla since it connects to https using TLS 1.0 and below. In contrast, Classilla 9.3.3 has been badly injured by this. Given how much attention has been paid to OS X for PowerMacs since 2010, it doesn't make that much of a difference on leopard and tiger when it comes to just web browsing. Not coming here often, though I just felt like sharing some of my experience about the new further deprecation of TLS 1.1 and below that many significant websites adopted.
0 kommentar(er)
