Just a quick heads-up as I don't think anyone else has noted it yet:
Not a "real" bug. The parameter is now a "tab" (instead of a doc).
Fair enough if you assume the Safari dictionary is accurate and
document ...' still performs an action as before; it's just the
return value that's missing; e.g.:
world'" in document 1
It should throw an error, though...
No arguments there, although I think it all just reinforces what I
said earlier about the Safari 3 dictionary being a mess. If backwards
compatibility isn't an issue, they shouldn't have introduced the
redundant 'tab' class; all they had to do was make 'document' an
element of the 'window' class and add any new properties to it, and
everything would've been peachy. OTOH, if backwards compatibility is
an issue, my original example should continue to work as before.
Either way, something needs fixed.
Personally, I would strongly recommend doing away with the 'tab'
class and setting up the correct relationships between 'document' and
'window'. With a little extra finessing of object specifier
resolution, even backwards compatibility could be preserved.
Honestly, it's a five-minute job to design a sensible object model
for Safari (and any hassles implementing it is between the Safari
engineers and whoever designed Cocoa Scripting in the first place -
it shouldn't be made the user's problem though).
Anyway, thanks for the reply. I'll pass it on to the guy who reported
the problem to me for his and his users' info as well (Safari 3
breaks the Ruby-based website testing framework they developed), and
will see about filing a longer bug report in the morning.
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: