Martin, being conservative for the Moodle part is the best way to go.
But developersd/designers can and do use YUI for added interface enhancements or flexibility. These efforts should be supported because they add the opportunity that Moodle will benefit from YUI much faster. If these projects work with all A-Grade Browsers they should be possible in Moodle too.
A way around this dilemma - as I see it in the moment - would be to rework the loading function in a way that:
1) YUI is used for Moodle core functionality like Drag&Drop with Moodle tested Browser support
2) YUI can transparently be used from developers/designers without any Moodle internal filtering for all A-Grade Browsers
One solution may be that the Moodle Ajax option works only for the Moodle Drag&Drop and other internal Ajax.
What do you think?
And Safari 2 is an A-Grad Browser and is rejcted when I read the function right. Safari 2 should be allowed too.