I'm not sure what "the titlebar of a site to drop all the images" means.
I remember the early browsers (we're talking Mosaic and Netscape .9 here) having support for "navigational links" (although Wikipedia only talks about the link element, and doesn't have much information on this) rendered as a list of buttons across the top of the rendering frame. The only place I remember seeing this heavily used was on some site that Eolas (http://eolas.com/, yes, the plug-in patent Eolas, who I was tangentially involved with back in the mid-90s). I don't think it caught on because, really, internal, embedded links are more a more valuable, user-friendly, and web-page UI component. Additionally, I don't think many designers (or whatever you called people who built web pages back then) used them because it was kind of an obscure feature and it didn't get you as much control over the display as even a simple list of links did back then. It's really something that should be brought back, but it would most likely get abused anyway. The limited space used in the original rendering would make navigation more difficult, as the site author would consider different things to be important to navigate to than actual users would (for example, how often do you actually need instant access to the "about us" page?).
I find it tremendously useful to have a site's shitty design, layout and navigation help indicate early on, before I get frustrated with it, if the site is even worth visiting or coming back to. "Well, the person behind this site obviously doesn't want me to find anything on it, time to head somewhere else".
I remember the early browsers (we're talking Mosaic and Netscape .9 here) having support for "navigational links" (although Wikipedia only talks about the link element, and doesn't have much information on this) rendered as a list of buttons across the top of the rendering frame. The only place I remember seeing this heavily used was on some site that Eolas (http://eolas.com/, yes, the plug-in patent Eolas, who I was tangentially involved with back in the mid-90s). I don't think it caught on because, really, internal, embedded links are more a more valuable, user-friendly, and web-page UI component. Additionally, I don't think many designers (or whatever you called people who built web pages back then) used them because it was kind of an obscure feature and it didn't get you as much control over the display as even a simple list of links did back then. It's really something that should be brought back, but it would most likely get abused anyway. The limited space used in the original rendering would make navigation more difficult, as the site author would consider different things to be important to navigate to than actual users would (for example, how often do you actually need instant access to the "about us" page?).
I find it tremendously useful to have a site's shitty design, layout and navigation help indicate early on, before I get frustrated with it, if the site is even worth visiting or coming back to. "Well, the person behind this site obviously doesn't want me to find anything on it, time to head somewhere else".