…n startup, not subsequent ones. oops. bug #268
…e installer screen with no scrolling
… because recent versions of WebKit have a scrolling bug that cause the video to be unviewable, unfortunately -- see bug #263
…imone's 0.40/0.25 and the previous 0.50/0.35).
… are correct since we don't overwrite permissions when installing
…t the 'staff' group
…stallation has failed and left behind a ClickToFlash plugin in /tmp that a non-admin user cannot overwrite
… (see the console output from Installer when perform an unprivileged installation).
…at the heck
…ution.dist file, we'll probably need a working .pmdoc file around, sorry @rentzsch
…ickToFlash to their OWN FRIGGIN' HOME DIRECTORY because we have to support 10.4 and because non-admin users can't write to the Receipts directory; fix involves creating TWO packages, one requiring admin privs, one not, and then creating a friggin' METAPKG which chooses which one to use based on whether the user is an admin and whether a receipt already exists, so that a password is required only when ABSOLUTELY needed; the updated script also replaces the bom and pax.gz files in one of the installers with a symbolic links to the respective files of the other installer, so we aren't having users unnecessarily download stuff; FRIGGIN' APPLE FIX YOUR INSTALLER TECHNOLOGY ALREADY, JESUS H. M. CHRIST
-RapidWeaver requires this for Flash slideshows in preview mode. -LittleSnapper requires this when Flash is required capturing a webpage, using the built-in browser or exporting websnaps to PDF. Signed-off-by: Jonathan 'Wolf' Rentzsch <firstname.lastname@example.org>
This makes sure we don't mess up previously-existing layouts if we replace videos with percent heights, e.g. on YouTube video pages.
Apparently, WebKits built on Tiger get a prefixed digit 4, and ones on Leopard get 5. Then there are custom-built WebKits that get no prefix at all: Normalize them and check against the resulting 3-digit code. Tested on Safari 4.0.3, 3.2.1, 3.1.2 and 3.0.4, and OmniWeb.
No functional difference, only a cosmetic one.
…Safari 3.0. When running on a WebKit that's more recent than the one in Safari 3.1 (WebKit bundle version 5525.x) use <video>, otherwise fall back to the QuickTime plugin.
…lms. Embedding QuickTime player in a web page results in ugly element overlaps when z-indexes are involved: Breakage we can avoid if we use the <video> element. Besides, this is the way of the future (-: This change requires a recent WebKit (Tested in Safari 4).