New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLOSED] Cursor shows up on next line after collapsing Quick Doc (with word wrap enabled) #4224
Comments
Comment by RaymondLim Raising it to medium priority since this has some confusing effect to Quick Edit and Quick Doc with incorrect line number with the following steps. After step 4 if you set the cursor in any line below the actual cursor position and use Ctrl+E or Ctrl+K, both features are using the previous line instead of the current line. If you want to show inline color editor, then you need to set the cursor one line before where the color is located before you press Ctrl+E. If you set it to the actual location, then inline color editor wo't show up. If you try with Ctrl+K, then you always see the CSS property from the previous line in Quick Doc. |
Comment by peterflynn
|
Comment by RaymondLim I'm seeing this on my win 7 even with sprint 25 build, but can't reproduce it on VM Win 8. |
Comment by RaymondLim Update: Need to open main.css in default window size with Word Wrap on. Then when you open Quick Doc on margin property, the vertical scroll bar also shows up in main editor window and line 6 will be wrapped with an extra line. I believe this extra line is the culprit of the cursor showing on next line when closing Quick Doc. |
Comment by JeffryBooher
|
Comment by peterflynn I was able to repro with other steps too:
Result: |
Comment by peterflynn Nominating for Sprint 29 -- even if it's been around a couple sprints already, any bug where CodeMirror's state is this screwy seems like cause for concern... |
Comment by lkcampbell I think this might be the same problem as issue #4318. |
Comment by RaymondLim
|
Comment by peterflynn Reviewed. Assigned |
Comment by peterflynn See also #4318 |
Comment by RaymondLim I don't think we can fix this one in Brackets since the cursor location is set from CodeMirror as it adjusts the wrapping for the vertical scrollbar. Sending back for review and suggesting to remove it from current sprint. |
Comment by peterflynn Seems not related to #4572 after all |
Comment by peterflynn
|
Comment by lkcampbell
Are you thinking an update to Chrome 28.0.1500.95 might fix this issue? Or, rather, whatever CEF version corresponds to that Chrome version? |
Comment by peterflynn
|
Comment by RaymondLim This is a Windows only issue. So I'll wait on Jeff's changes to update to CEF 1354. |
Comment by pthiess
|
Comment by njx This is still listed on the bug card--should we remove it? |
Comment by RaymondLim Yes, we should remove it. |
Comment by RaymondLim Just tested with CEF 1354 build (Chromium 29) and still not fixed. So it may not be codemirror/codemirror5#1642 or codemirror/codemirror5#1123. |
Comment by gruehle Reviewed. To |
Comment by malayhm Chrome 29 is released today and the issued is fixed from chrome side. |
Comment by njx I can't reproduce this on Mac even in Sprint 28, so maybe this is a Windows-only issue? I'll try it on my Windows machine next. |
Comment by RaymondLim Yes, this is Windows only issue and our current CEF still has the issue. |
Comment by njx Ah. Yes, I can still reproduce it in current master on Windows. |
Comment by jasonsanjose Reassigned to me. |
Comment by jasonsanjose I'm trying to reproduce it in a simpler codemirror sample, but so far, no luck http://jasonsanjose.github.io/uploads/word-wrap-bug.html. Seems to only reproduce within the Brackets layout. I still have more angles to try. |
Comment by jasonsanjose BTW, |
Comment by RaymondLim
|
Issue by RaymondLim
Wednesday Jul 24, 2013 at 23:13 GMT
Originally opened as adobe/brackets#4564
Result: Quick Doc closes, but the cursor is now showing up on the next line. If you type any letter, the letter will show up where you set in step 2. That is, it goes to the correct location.
The text was updated successfully, but these errors were encountered: