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.

Bug 228758

Summary: Selection outline delayed when scrolling
Product: web Reporter: Vladimir Riha <vriha>
Component: InspectionAssignee: Jan Stola <jstola>
Status: RESOLVED WONTFIX    
Severity: normal CC: mfukala
Priority: P4    
Version: 7.4   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:

Description Vladimir Riha 2013-04-19 11:49:42 UTC
Please check this video [1] (from Android device-Chrome), if you select some element and scroll on page, all highlights and outlines created by NetBeans are a bit delayed over scrolling. It is less apparent on this video, but If you try it with device, it is easily reproducible. It seems as if the position of highlights is updated once in a time.

I'm not sure if the issue is caused by Chrome itself or it could be fixed.I've found some blog post about it [2] and it seems to be general issue with mobile browsers


[1] https://docs.google.com/file/d/0B6Sd5ov8j7IUblJkS19ta0k4WDQ/edit?usp=sharing
[2] http://tjvantoll.com/2012/08/19/onscroll-event-issues-on-mobile-browsers/


Product Version: NetBeans IDE Dev (Build web-main-10336-on-20130419)
Java: 1.7.0_21; Java HotSpot(TM) Client VM 23.21-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_21-b11
System: Linux version 3.2.0-40-generic-pae running on i386; UTF-8; en_US (nb)
Comment 1 Vladimir Riha 2013-05-16 12:57:30 UTC
works for me now
Comment 2 Vladimir Riha 2013-05-16 12:58:54 UTC
Sorry, wrong issue
Comment 3 Jan Becicka 2013-06-06 07:04:38 UTC
Reassigning to Honza for evaluation. How do you draw highlights? Thanks
Comment 4 Jan Stola 2013-06-20 11:14:41 UTC
The repainting during scrolling works very well in desktop Chrome and it works reasonably well (just with a very small delay) on my mobile Chrome 27.0 (on Android 4.2.2). The repainting during scrolling is based on 'scroll' event, of course. If there are platforms where this event is not delivered (or delivered with a significant delay) then there is not much that we can do (especially, because there is no obvious workaround according to the mentioned blog post).