This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Just mentioned, when editing large text the view position is often spontaneously shifted to the start of the page (up) when I use arrows to navigate the cursor position. Similarly it is impossible to edit long code row, because cursor view is shifted to the left.
I'm using 10.1pre4 on 32-bit Windows XP. I'm encountering very strange behaviour when attempting to move in the document with the down-arrow key in the WYSIWYG view. This may be triggered by the presence of an SVG object at the top of the document. I've uploaded a sample document to http://smithies.org/cpks/test/nl4.html - when I click on the "TBA" in the rightmost column of the first table, repeated down-arrows seem to go circularly through the lines of the next section, and then back again. If the cursor is located in the paragraph following "Ringing Roadshow", down-arrow causes the scrollbar to move strangely, the cursor disappears and it's difficult to recover cursor navigation. Good luck to the team in tracking this one down!
10.1 pre5 is a radical improvement. The sick lurching of the display is gone. Congratulations! (The remaining oddity, that the down-arrow key cycles bizarrely when located in a table, is a quite minor issue.)
(In reply to comment #2) > 10.1 pre5 is a radical improvement. The sick lurching of the display is gone. > Congratulations! (The remaining oddity, that the down-arrow key cycles > bizarrely when located in a table, is a quite minor issue.) > I didn't use SVG objects, but when using tables the cursor is stuck to low cells. From my point of view it is really annoying.
(In reply to comment #0) > Just mentioned, when editing large text the view position is often > spontaneously shifted to the start of the page (up) when I use arrows to > navigate the cursor position. > Similarly it is impossible to edit long code row, because cursor view is > shifted to the left. > This bug is now fixed in the CVS version. The fix will be available in pre6 and the release