Static resource content area not showing

I can't seem to get static resources to show the content area. It doesn't matter if I set it to static ahead of selecting a file, or if I select a file. All I get is the file name and the resource border just below this with no content area.

So since this is a static conversion with just a few resources, I went ahead and x'd the installation and reinstalled. Same result.

When I search, Google shows me a result from the rtfm that says if you have missing content, let us know. New rtfm does not have this text. Regardless, perhaps someone has seen this before. If not, as searching is coming up with nothing in the forums, I suppose I submit a bug report.

Did you also set the Media Source to Filesystem?

If so, check the settings of that Media Source in Tools -> Media Sources.

Yes, it's set by default on install, but I went in and clicked the revert to default and saved it anyway. No joy.

Have seen this intermittently on other sites but I can't nail down when and where. Most other sites have been switched to document so it's not an issue, but this one is still in templating.

I suppose you've tried turning off compress_js and compress_css and clearing the cache and the browser cache and cookies. If so, I'm out of ideas.

Yep, yep... yep, and yep. Amongst other things. Dangit.

Wait, do you mean that you don't see the Static Resource's content in the Manager or when viewing the Resource in the front end?

I think not seeing it in the Manager is normal (unlike static elements).

Correct. A static resource's content is not displayed; its content is the path. Elements have both a content field and a static_file field for the path.

To elaborate... static resources can have their content in a file, or they can actually represent a file, such as a .pdf file. A link to the static resource will (if given a custom content type and a content disposition of attachment) product a download dialog rather than displaying the resource's content. They can point to files of any type, from images to text, in or out of the web root. So having the content of the file they're pointing to displayed in the editing form would not even be possible in many cases.