Oh goody, let's hide front end stuff in the back end coding!
You lot love doing this. I need my SMF siggy over here:
Anyway, I was taking a look at index.template.php and found this bit:
<div id="wrapper" class="wrapper">
<div id="upper_section"', empty($context['minmax_preferences']['upshrink']) ? '' : ' style="display: none;" aria-hidden="true"', '>';
call_template_callbacks('uc', $context['upper_content_callbacks']);
echo '
</div>';
Ok, so apparently this is done to enable people to hook in extra stuff to that area, and have it handled by the same collapse/expand function. That's my guess anyway, since I can't see any other reason to do it.
The catch is that from a themer's perspective there is no indication of what is covered by upper_content_callbacks. It's all pretty opaque, and they'd have to go digging in the back end to figure it out. Then, if they want to change something in the theme, AFAICT they would have to ditch function template_uc_news_fader() and replace it with another function to get something independent of upper_content_callbacks.
Ok, so what happens if function template_uc_news_fader() is ditched? Will anything break, due to sources expecting it to be there?