UNCONFIRMED59690
Div is moving on drag
https://bugs.webkit.org/show_bug.cgi?id=59690
Summary Div is moving on drag
satya
Reported 2011-04-28 04:17:47 PDT
Created attachment 91469 [details] Chrome drag A Div has a sibling with mode width and extra width got hidden by the property "overflow:hidden" on its parent. While dragging inside a Div element(should have a vertical scroll), left part is getting hidden. Actually it is trying to the hidden part sibling div. Please find the attached test page to reproduce the problem.
Attachments
Chrome drag (1.15 KB, text/html)
2011-04-28 04:17 PDT, satya
no flags
satya
Comment 1 2011-04-28 04:28:29 PDT
**Corrected the comment** A Div has a sibling with more width and the extra width got hidden by the property "overflow:hidden" on its parent. While dragging inside a Div element(should have a vertical scroll), left part is getting hidden. Actually it is trying to show the hidden part sibling div. Please find the attached test page to reproduce the problem.
satya
Comment 2 2011-05-02 22:22:02 PDT
Can you please give update on the issue.. It was breaking in critical scenarios.
satya
Comment 3 2011-05-03 22:12:04 PDT
Making to blocker to get the attention.
Alexey Proskuryakov
Comment 4 2011-05-04 00:51:04 PDT
Please don't. If you know that this is significantly affecting users of existing sites, please provide the information.
satya
Comment 5 2011-05-04 03:33:30 PDT
When can we expect the update on this defect?
satya
Comment 6 2011-05-05 06:17:58 PDT
We are direct partners with Google and providing Cloud platform. As we largely depend on the drag and drop of elements, it was failing in lot of customer scenarios. Please provide a urgent fix.
Alexey Proskuryakov
Comment 7 2011-05-05 09:28:00 PDT
Please read <https://bugzilla.mozilla.org/page.cgi?id=etiquette.html>. If you think that Google owes you an urgent fix, please tell your Google representative. WebKit contributors have no obligation to investigate this issue on your schedule.
satya
Comment 8 2012-10-25 03:14:40 PDT
Any update on the issue?
Note You need to log in before you can comment on or make changes to this bug.