On 20 Sep 2007, at 12:54, Philippe Wittenbergh wrote: > I'm not so sure that relying on nightly builds is a fully accurate > testbed for what will be Safari 3 whenever it is released.
I'm not suggesting that it is; just that it's a useful way of checking to see if an existing bug has been fixed. Obviously, being a nightly, there's always a chance that a regression will make a bug reappear, so it's worth checking in a random sprinkling of nightlies if a bug still appears to be present. But if, as I did, you can confirm that the behaviour of 2.0.4 is fixed in a later build, then you know that the mistake isn't in your own code and can move straight on to finding an implementation which _is_supported correctly, rather than trying to fix code that wasn't broken in the first place. As for what _will_ work in Safari 3: we won't know until it's released. One should never trust a Beta of any product to be anything more than a rough guide to what the final version might be like. Remember, the Beta isn't released as a platform for web developers to work to, imagining that they can make sure that their sites work in Safari 3: it's so the community can test and report suspected bugs to the WebKit and Safari teams. Remember when IE 7 Beta 2 came out and people started publishing articles on their blogs about how to get things working correctly on it? Wasted effort, all of it; they should have been reporting bugs, not devising workarounds which were redundant in the finished product. It's the same with Safari 3; the time to start testing _our_ work is when the final version is released. Until that date we are testing _Apple's_ work. Regards, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
