This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Random reset display position on long lines.
I don't know what you mean by this. Please provide some more info. Add exact steps how to reproduce, and you can also provide source file where it can be reproduced. Then simply reopen. Thanks.
Created attachment 145906 [details] File with issue Try to edit largest comment or attribute
Created attachment 145907 [details] Step 1
Created attachment 145908 [details] Step 2
Sorry for unclear bug report. Steps to reproduce: on step-1.png start position of cursor under "CCS" then i made some changes in attribute (typed "some changes") Next combination of key will be set display as step-2.png "Down" -> "Up"
If I understand correctly, this issue is about XML support. Please evaluate, thanks.
Yes, i can't reproduce it on other file types.
Editor view hierarchy issue, IMHO. During my debugging, it happened that the call newCaretBounds = c.getUI().modelToView( c, offset, Position.Bias.Forward); in BaseCaret::updateCaretBounds() produced newCaretBounds.x == 0 although the offset clearly didn't correspond to any line start. It seems that the culprit is DocumentViewChildren::modelToViewChecked method, the optimization from rev. b6041b6ecd29; I suspect that the documetview children are null because of some invalidation. Anyway, the returned rectagle has always x == 0, which seems inconsistent with the optimization turned off. If not fixable, please suggest another way how to compute screen bounds allocated for the given document offset.
Fixed in http://hg.netbeans.org/jet-main/rev/a62cc2a6e342
Integrated into 'main-silver', will be available in build *201508200002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/a62cc2a6e342 User: Miloslav Metelka <mmetelka@netbeans.org> Log: #242743 - Random reset display position on long lines.
*** Bug 247079 has been marked as a duplicate of this bug. ***
*** Bug 240494 has been marked as a duplicate of this bug. ***