Thread:Feedback/Edit textbox annoyance

When a user creates or edits a post, to the right of the text is a "live" index of the sections etc in the markup. That's fine.

There's a rendering point that's disproportionately annoying. The text box initially shows without this data. A while later, once the markup loads, the live index is created -- and the textbox reformats, scrolls as needed, etc. Annoying since it happens right at the end, when it looks like one can start editing and I've often begun editing, only to have the entire text box change midway, as the live index is set up and added to the HTML.

The request is simple. Can the "box" where the live index appears, be created at the start, as part of the text box itself, with a pre-defined (fixed but draggable?) width, so that when the page has loaded, the box is filled, but it doesn't need to suddenly "pop into existence" changing how the existing rendered textbox and content look, and disrupting the user who may already be typing in many cases (long page, slow network or PC, user may not realize page still loading and begin to type).

A major problem is when this happens, the user's typing may cease to be interpreted as textbox input and start being recognized as browser window input (search, or browser commands, etc). I've had it that I was typing content into a textbox and deleting some, and suddenly the browser started to interpret backspace key presses as "browser page back" commands and go back several page views.

Hope this makes sense! Not sure how better to describe it.

I guess essentially, can the initial HTML for the form include that "live index box" so it's there on initial HTML load (and later is only filled), rather than adding it into the HTML at a later stage.