> I just ran into a *serious* issue in Safari 2.0 using this hack > (*property:value)
> I had to switch to selector, (property:value) but I'd like to know if I > missed anything(?) I thought that filter was *safe* to use. As a follow up: selector (*property:value) fails but selector (*property:value;) works the trailing semicolon is the fix here... Thanks to Gamaiel (from another list) for suggesting this -- Regards, Thierry | http://www.TJKDesign.com ______________________________________________________________________ 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/
