Okay. Here is the problem. If we have a page like this:
<chapter id="file-upload">
<title>Handling File Uploads</title>
<sect1 id="file-upload.post">
<title>POST Methods</title>
</sect1>
<sect1 id="file-upload.errors">
<title>Errors</title>
</sect1>
...
</chapter>
We make a top level page for File Upload and also put the POST content
on that page. Errors goes on another page.
Before, we would have sidebar links like this:
File Upload
- POST (This points to the file-upload.php#POST)
- Errors
Now, it's just:
File Upload
- Errors
So, the person can still get to POST, it's just linked to from File
Upload. We should probably fix it, but I don't think it's a show
stopper, so I'll look into it later.
Well, I have seen some code added by Thomas specially for this to happen, which you are against ;) The reason was that "next" nav links should not point to the same page when the 'next' chunk is integrated to the current one. This may affect the TOC builder too, as it may use the same template which blocks non-real chunks from appearing in TOCs. This made sense in connection with the top/bottom nav links.
Goba