@59.aditya: Could you please provide us any sample html/JS file to triage the issue from test team end.

Thank you!

59....@ 

I wrote this example as you described it. I don't see a jump
http://jsbin.com/pupijo/edit?html,css,js,output

Hi,
Sorry I missed your  email.

This is happening in one of my apps.

The jist of the issue is:

I've are developing a javascript editor.We have a span that has a scroll
which holds all the dom for the editor. We also had a text area with width
1px and height 3px. This is used to store data of the editor

Usually the focus is with the text area and equivalently a cursor blinks in
the  span.

For some reason the focus went to the span. The textarea was located on a
bottom scroll page and page was scrolled to the bottom. when I tried to
focus on texrarea it jumped to top of the page.

Sadly I am not able to give a smaller reproduction steps since I  am not
able to reproduce this with a small example. The workaround that worked was
making width 3px. This started happening in newest version of  chrome.

You can close the issue if you are not able to reproduce this since it's
difficult for me to share the code of the editor and I m not able to
replicate it with a small version of code.


Summary: Take a span which is big enough for page to scroll. Have a text
area inside it which always has focus. One time the span had focus. Now
make sure the text area is at bottom of span and page is scrolled. Take
focus from span to editor programmatically.

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

#0/#4: We could try our best but as you said, what we can do is very limited without being able to reproduce the issue. If you could share the reproducible files, small is better but large is ok too, it is very helpful for us.

I'll let our focus experts to see if there were something we can do with the information in this issue.

59...@: Could you make the jsbin given in comment#3 reproduce the problem
by modifying it?  If it's difficult, then we'd like to give up with this one.

Without clear reproduction case, we can't be sure we fixed the problem.

Let me try that. I'll try to do that over the weekend and update you guys.
Thanks for looking into it. If I am not able to reproduce it, then you can
probably close it.

Thank you for providing more feedback. Adding requester "kochi@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@ 59.aditya : Could you please update on comment #9.

Thank you!

I tried but was not able to reproduce the issue. For now you can close the
ticket and I will get back to you guys once I discover a way to reproduce

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Mark it as WontFix as per comment #12 provided by reporter.Feel free to raise a new issue if sill facing.

Thank You!