Quick Tour - Main Index links 10-19 broken

[Coldfirex]

Howdy, In the Quick Tour within the Index the links of 10-19 are broken. They reference: "​file:///boot/system/documentation/welcome/en/quicktour.html finished" R1 Beta 2 hrev54154+115 64bit.

[nielx]

@Humdinger: could you have a look at this?

[humdinger]

This is caused by some error in the HTML structure. I cannot pin it down exactly, but it has to do with the index block being right aligned to the "The Deskbar" block. The non-working links in the index table start where the "Deskbar" block starts. (The "Welcome to Haiku's Quick Tour" block is in the same div-block as the index).

If you make the window really narrow, so that the index table glides above the "Welcome" block, all links are working.

For a solution, I'll have to defer to a more HTML savvy collegue, I'm afraid...

[Coldfirex]

Since I am new to this, where can I find the HTML source to examine?

[Coldfirex]

It seems to do better when I make the following changes: Replace all "<acronym "with "<abbr " as well as also replace these:

<h1><a id="start" name="start">Welcome to Haiku's Quick Tour</a></h1>

with

<h1><a id="start" >Welcome to Haiku's Quick Tour</a></h1>

[madmax]

Not really the HTML structure, but yep, the right "alignment" of the index block.

The index table floats right, so it is "out of the flow". Its container (div#content > div) is then the height of the welcome paragraphs. The div#content > div.topic that follow are placed over the lower part of the box "shadowing" the links. The text doesn't get into the table, but the element itself expands to the right margin, getting the mouse events.

Setting aside the issue of using a table for a list of links, it seems that adding position: relative and a high z-index to the the table.index CSS rules works.

Another possibility is to start the topics only after the end of the table. You can do that adding clear: both to the style of the first topic or that of a dummy div at the end of the table container. Or in a saner ::after rule for that same container.

[waddlesplash]

Fixed on the Userguide translation server, it will appear in the next export.

[nielx]

Assign fix to milestone:R1/beta3, as it looks like this fix will be part of that release.

As we started with the previous beta, we would like to use the Milestone field for fixed tickets to log from which release the improvement will be out. Therefore it is very much appreciated to assign the milestone when closing a ticket as fixed.