With layer ordering, in most conventional GIS, the top layer is the one that is "on top", but this is the other way around in GeoServer's "layer groups". While this is documented, I'd suggest that use of this grouping should be "intuitive" - I figured it was before I started wondering why layers weren't showing. This would help usability.
While inverting the ordering would be preferable, I don't see that happening. Instead I'd suggest some text on the layers list which states at the top clearly "Bottom Layer" and at the bottom "Topmost layer" or something to that effect. Maybe as a couple of gray rows in the table itself.
CodeHaus Comment From: jratike80 - Time: Thu, 10 Jan 2013 10:50:45 -0600
<p>For my mind the current behaviour is OK because Geoserver is a WMS server and WMS standard says:
'A WMS shall render the requested layers by drawing the leftmost in the list bottommost, the next
one over that, and so on.'</p>
<p>Leftmost projects better to the top of the vertical list than to the bottom. IMHO, flipping the order is at least not so much and absolutely better alternative that it would be worth the mess it would cause for the old Geoserver users.</p>
CodeHaus Comment From: jonathan_wcc - Time: Thu, 10 Jan 2013 10:59:43 -0600
<p>Yep, I figured flipping wouldn't go down well for that reason. Assuming the current behaviour is left, I think it could be improved by making it clear where the "top" layer is and where the bottom one is.</p>
<p>Remember that most users won't have read every word of the GeoServer documentation, and certainly won't have read the WMS spec. That's why I suggested putting some text into the UI itself to make it clear to the users which layers will be "on top".</p>
Mass closing all resolved issues not modified in the last 4 weeks