43 posts tagged “safari”
2007
(somewhat) breaking the same-origin policy by undermining dns-pinning. This is the best technical explanation of the DNS rebinding attack I’ve seen. The linked demo worked for me in Safari but not in Camino.
Yet another one more thing... a new Web Inspector! I installed the latest nightly but I couldn’t find the inspector (or work out how to turn on the debug menu). Anyone know what I’m doing wrong?
Safari Beta 3.0.1 for Windows. A nice fast turnaround on fixes for security flaws in the beta.
Safari for Windows, 0day exploit in 2 hours (via) Once again, down to handling of alternative URL protocol schemes.
Enabling the debug menu on Safari for Windows. “Turn off site-specific hacks” is one of the menu options.
Safari 3 Public Beta. Safari for Windows. Unfortunately this kills the best excuse corporate Web developers had for getting Macs (“we need to run all our supported browsers on one machine”).
Microformats Bookmarklet. Microformats bookmarklet, targetted at Safari. Uses jQuery CSS selectors for parsing, and generates .vcf vCard files using data: uris.
How to enable session saving in the new Camino 1.1a2 (via) I’ve stopped spending time in any browser that doesn’t have session saving built in—sorry Safari!
2006
So long Safari?
All browsers have bugs—especially relating to fancy JavaScript stuff. Any truly complex web application is likely to run in to browser bugs, and fixing them takes a whole bunch of time. Bugs in IE and Firefox are pretty well understood, as are the workarounds for them.
[... 317 words]2005
Safari 1.3 has a JavaScript Console
My single biggest complaint about Safari in the past has been its terrible support for JavaScript debugging. Safari 1.3 has just been released, and tucked away in the Debug menu is a brand new JavaScript console option. It’s not as good as the Firefox equivalent (it throws up far too many “Undefined value, line: 0” errors for my liking) but it’s a big step in the right direction.
Maps released. Google Maps Safari support is being worked on.
2003
Safari conditional comments
The current extended discussion over whether or not Safari should have some kind of specific CSS blocking technique built in (sparked off by Mark Pilgrim) reminds me of a relatively unpublicised feature of Internet Explorer called conditional comments. These specially crafted HTML comments allow web authors to specifically hide code from versions of IE, or alternatively to hide code from any browsers that are not a specified version of IE. Here’s how they work:
[... 198 words]Safari surprise
I dunno, you take the evening off to watch a daft Bond movie (Goldeneye was showing on ITV) and when you log on again the world is aflame with reports of Apple’s new browser, Safari. To everyone’s surprise it’s based on the KHTML engine as seen in Konqueror, rather than using Mozilla’s Gecko engine. I’ve used Konqueror a fair bit in the past few months and it really is an excellent rendering engine (I was amazed when it rendered all of my favourite CSS layout sites flawlessly) but this is still something of a shock, especially considering Apple’s recent hiring of Dave Hyatt, a key member of the Mozilla project and the guy behind the excellent Gecko-based browser Chimera.
[... 176 words]