Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361157

Summary: [WebKit] Editing caret does not go to start of line when zoomed in
Product: [ECD] Orion Reporter: Mark Macdonald <mamacdon>
Component: EditorAssignee: Project Inbox <orion.editor-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: eclipse.felipe, john.arthorne, Silenio_Quarti
Version: 0.3   
Target Milestone: 4.0 M1   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Mark Macdonald CLA 2011-10-17 11:18:38 EDT
Orion 0.3RC2 at orion.eclipse.org

1. Create a new .js file with this content:

var foo = function() {
    var bar;
};

2. Put the caret at "var bar" and press Home (or press LeftArrow several times).
3. The caret is not drawn in Column 1. It remains in the previous column.
Comment 1 Felipe Heidrich CLA 2011-10-17 11:59:06 EDT
(In reply to comment #0)
> Orion 0.3RC2 at orion.eclipse.org
> 
> 1. Create a new .js file with this content:
> 
> var foo = function() {
>     var bar;
> };
> 
> 2. Put the caret at "var bar" and press Home (or press LeftArrow several
> times).

before or after ?

> 3. The caret is not drawn in Column 1. It remains in the previous column.

It is working for me on Chrome, what browser and OS are you testing ?
Comment 2 Felipe Heidrich CLA 2011-10-17 11:59:21 EDT
anything in the console ?
Comment 3 Mark Macdonald CLA 2011-10-17 12:41:53 EDT
(In reply to comment #1)
> before or after ?
Shouldn't matter -- whenever you approach column 1 using LeftArrow or Home, it behaves the same way.

> It is working for me on Chrome, what browser and OS are you testing ?

Oops, I didn't notice this when I opened the bug, but I was running the editor at Zoom = 120%. At Zoom = 100%, you won't see the bug. 

I'm using Chrome 15 on Windows 7.
Comment 4 John Arthorne CLA 2011-11-18 11:37:39 EST
Seeing the same thing. Chrome 15, 120% zoom.
Comment 5 Silenio Quarti CLA 2013-08-12 15:21:16 EDT
This problem should be fixed after the changes for bug#412697. Please reopen if you still can reproduce it.