Fixing an asyncronous loading issue.

[Retread]

I had a plugin submission rejected from the Library.

Your plugin "Easy Google Translate" has been rejected for the following reason:
This plugin breaks the ProBoards Developer Guidelines.

- Codes which rely on external code to work properly. Note that using external data is acceptable, so long as that data is loaded asynchronously.

I'll spare you all the convoluted css in the plugin and get to the core. It uses this in the Global Header:
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en', layout: google.translate.TranslateElement.InlineLayout.SIMPLE, multilanguagePage: true}, 'google_translate_element');
}
</script><script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>


Would adding async defer likely be enough to correct the issue or am I wasting someone's time if I resubmit with the following changes:
<script async defer type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en', layout: google.translate.TranslateElement.InlineLayout.SIMPLE, multilanguagePage: true}, 'google_translate_element');
}
</script><script async defer type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>


[Brian]

The plugin would still be rejected on the basis that it's reliant on the Google Translate JS file on the last line.

Plugins submitted to the library cannot be reliant on external code as there's no guarantee the file located at that URL will remain there indefinitely, never change, or never be substituted for a script containing harmful or malicious code.

[Retread]

Thanks for the speedy reply, Brian.