Rename "scope" to "region" in drupal_add_js()

Discussion on IRC revealed that albeit "scope" allows to also place JS in theme regions, scopes are poorly named.

The scope "header" does not add to the "header" region, it actually adds to "html_head"; proper region name would probably be "head".
The scope "footer" does not add to the "footer" region, it actually adds to "closure"; proper region name would probably be "closure".

Also, this uncovered that one is not even able to add JS to the "header" or "footer" regions of a theme. So renaming "scope" to "region" in drupal_add_js()'s $options array, as well as fixing the special scope names to use proper page regions (head/closure) is badly needed.

Should it be renamed to region since the name region doesn't quite mean the same thing as region elsewhere in drupal? For example, in the theme system. If I add a region called 'blue smurf' and try to add js via drupal_add_js to the blue smurf region it won't render.

Of course, you'd have to use the internal region name, i.e. "blue_smurf".

This issue depends on #315798: JavaScript Patch #2: Weight, hence marking as postponed.

Is this still an issue?

I'm a bit baffled.

1) I don't think it makes sense to rename 'scope' for drupal_add_js(), when considering our long-term goal to "merge" JS/CSS into generic support file/page requisite helper functions.

2) Looking at how 'scope' is used, it seems that 'region' would be wrong, as 'header' and 'footer' are no regions, but special locations html.tpl.php. Specifying anything else seems to require to invoke drupal_get_js() manually for that custom scope.

I'd suggest to close this issue in favor of 1).

Any way to make page_top a scope if I need to add JS code to this region?