Ticket #2531204 (assigned defect)
Reporter  Luke Smith |
Opened: 09/22/11 Last modified: 03/25/13 Status: assigned Type: defect |
Owner Anthony Pipkin |
Target Release: BACKLOG Priority: P4 (low) |
|---|---|---|---|
| Summary: | Redraw artifacts in table during and after scroll | ||
| Description: | See https://skitch.com/lsmith/f58at/win7-ie9-dt-scroll-example In Scrolling DT example in IE 9. |
||
| Type: | defect | Observed in Version: | 3.4.1 PR1 |
| Component: | DataTable | Severity: | S3 (normal) |
| Assigned To: | Anthony Pipkin | Target Release: | BACKLOG |
| Location: | Example | Priority: | P4 (low) |
| Tags: | Relates To: | ||
| Browsers: | IE 9.x | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 09/23/11
|
|
Posted: 09/23/11
Tested on the native Win7/IE9 box we have, against 3.4.1PR1. I see the bug, only when scrolling up (if it matters) |
|
Posted: 09/23/11
And yet, not reproducible on VM. |
|
Posted: 09/23/11
It smells (looks?) very much like a h/w accel/gpu bug, so wouldn't be surprised if a certain client hardware/driver setup would/wouldn't see it. I tried messing with: a) Disabling H/W accel in IE9 Couldn't get rid of the bug completely, but did change it's characteristics. The artifact lines were always "row height" apart as opposed to being a pixel or two apart. It is just overflow-y:scroll? Or is there cutting edge CSS magic to keep the header fixed? |
|
Posted: 09/23/11
Artifacts exist in 3.4.0 on yuilibrary.com. I'll revisit this in 3.5.0. Interestingly, the artifacts change depending on the scroll position of the page. Seems like some bad pixel math in the UI paint algo on MS's part. |
|
Posted: 11/9/11
Bug scrub. Moving to 3.NEXT with the intention to pull into 3.6.0. 3.5.0 is all DataTable for me, so I can't afford the split bandwidth. |
|
Posted: 04/6/12
Check if this is still happening with the new scroll arch. |
|
Posted: 04/6/12
|
|
Posted: 07/24/12
Moving from 3.6.0 backlog to 3.NEXT. |
|
Posted: 09/19/12
Moving from 3.NEXT to BACKLOG. |
|
Posted: 03/25/13
|
These artifacts may be caused by the VM I'm testing in. Can someone verify this example against master?