My personal take on Dan's post is why can't the SAFARI folks at Apple investigate the problem, verify the source, and, if appropriate, open up a problem with WebKit. Was some law passed while I was napping which prevents development organizations from trying to get bugs fixed in critical external components their project depends on?
I can maybe see why they'd rather someone else did their grunt work. But if their work depends on a component then I'd expect them to be pushing hard(er) to see that whatever is broken gets fixed. Who in particular is going to be doing the fixing feels more like a sub-issue. I'm just saying ... Oh, well. -irrational john -- You received this message because you are a member of G-Group, a group for those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs. The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml To post to this group, send email to g3-5-list@googlegroups.com For more options, visit this group at http://groups.google.com/group/g3-5-list To unsubscribe, reply using "remove me" as the subject.
