The wiki leaves several behaviours unexplained: checkbox-like UGO rows, side-by-side entries, possible larger HTML fonts, direct links to .lst URLs and some .info resources. The unusual UGO layout may work only with index.ugo. The sole recorded direct .lst test produced a loading error. These need further investigation before a service can depend on them. [1]
| Observation | What remains unknown | Useful comparison |
|---|---|---|
| Checkbox-like controls and paired items appeared in a menu image. | Whether ordinary UGO records can request them, or whether the arrangement belongs to a special index page. | Compare an index.ugo response with a minimal menu using the same record types. |
| Some top-screen headings appear larger than the documented metadata text. | Whether an HTML attribute selects that font size. | Save the exact HTML response and vary one metadata name at a time on the same build. |
A direct .lst link was fetched, then rejected as unloadable. | The expected payload, context and parser path. | Compare ordinary list-file reads with navigation from an online page. |
.info resources occur in service paths. | Which subsystem owns them and what structure the client expects. | Pair a captured request with the original code that consumes its response. |
Keep the exact response file and application build when investigating one of these behaviours. Change one field at a time and compare both the display and the code that handles the response. A screenshot can show that a control appeared, but cannot by itself identify the record or action handler responsible. [1]
What the historical tests show
| Lead | Source evidence | Unresolved detail |
|---|---|---|
| Checkbox-like and side-by-side UGO entries | A menu screenshot linked by the wiki shows the unusual arrangement. | Its record representation and whether it is restricted to index.ugo were not established. |
| Larger text within HTML pages | The wiki points to Junya Kondo's 9 February 2010 post about the Colour Star Exchange, also called the Theme Shop, and its page-heading image. | The image suggests a size beyond ordinary body text, but does not identify an HTML font-size attribute or prove that the upper-screen title font is exposed to body content. |
| Direct navigation to a list file | A clicked URL ending in .lst was fetched and treated as a navigation attempt. | The attempt ended with a data-loading error; neither an accepted payload nor the required surrounding state was recovered. |
.info resources | The extension appears in observed paths. | The wiki did not identify its consumer or file layout. |
The source gives the UGO layout three stars for research usefulness, font sizing two, and the extension questions one. These are the authors' priorities, not confidence ratings or compatibility guarantees. To investigate further, record the response bytes, exact application build and the routine that reads them alongside the screenshot or path. [1]