[BUG] Table overlaps with Contents column on the right and resizing left column moves the center text

[aitor-lunarg]

Describe the bug
Some tables are too big and will overlap with the Contents column on the right making it hard to read. While this can be fixed by resizing the left Vulkan Feature Description column to fit the table, resizing this column also moves the text losing the anchor where the user had the page.

To Reproduce
Steps to reproduce the behavior:

1. Go to the table in https://docs.vulkan.org/features/latest/features/proposals/VK_EXT_descriptor_heap.html#_device_properties slightly below the link location.
2. Resize left column.

Expected behavior
Table should not overlap. Resizing the left column should not move the center text.

Screenshots
https://github.com/user-attachments/assets/3949124c-8189-4a07-a46c-075935824248

Desktop (please complete the following information):

• OS: macOS 26.0.1
• Browser Firefox
• Version 147.0.2 (aarch64)

[oddhack]

@gpx1000 I think one part of this this may be in your ballpark is "Resizing the left column should not move the center text." - Marty was just experiencing that on the telecon when we were looking at the example page. Maybe that's something that could be handled in JS?

As noted on the call, there are a lot of problematic table issues in the Vulkan spec, in particular, which lie at the intersection of the amount of flexibility browsers have in doing table layout (even when supposedly fixed-width columns are specified); underspecification of the tables at the asciidoc markup level; and perhaps needing an explicit CSS role assigned to some tables or table columns, so we can modify the CSS to layout those cells without content overflowing. I have been working through this with the SPIR-V Antora port, which is an extremely table-centric spec, and will update here when I get that figured out as it is probably applicable.

[oddhack]

I created an internal tracker to work on the Vulkan spec tables. There are about 20 of them that could use modest markup and CSS improvements, of which a handful actually overflow the margins and run into navigation as @aitor-lunarg noticed and the rest have less deadly issues. This is mostly an asciidoc markup fix but a tiny addition to the UI CSS here may be needed to avoid the overflow and force text wrapping in cells, instead.