Bug 103155
| Summary: | [EFL][WK2] Whole page flicks after final update/rendering | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Jesus Sanchez-Palencia <jesus> |
| Component: | WebKit EFL | Assignee: | Kalyan <kalyan.kondapally> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | kalyan.kondapally, kenneth, laszlo.gombos, lucas.de.marchi, ostap73, rafael.lobo, yael |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 103522 | ||
| Bug Blocks: | 103105 | ||
Jesus Sanchez-Palencia
Run Minibrowser, open http://maps.google.com. Now do some double tap to zoom and you will see that after the animation ends, whole page flicks.
Sometimes you see the flick only inside the map area, some times you see it flickering entirely (keep your eyes at the Google logo and do some zoom in/out and you will be able to experience it).
It happens not only with double tap to zoom, but also with wheel zooming and clicking on the + or - buttons that the map provides.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Kenneth Rohde Christiansen
This might be caused by the same that causes https://bugs.webkit.org/show_bug.cgi?id=103271
Kalyan
(In reply to comment #1)
> This might be caused by the same that causes https://bugs.webkit.org/show_bug.cgi?id=103271
We can still see this. It seems a synchronization issue. Looks like we dont handle all the sync requests in LayerTreeCoordinatorProxy
Kalyan
(In reply to comment #2)
> (In reply to comment #1)
> > This might be caused by the same that causes https://bugs.webkit.org/show_bug.cgi?id=103271
>
> We can still see this. It seems a synchronization issue. Looks like we dont handle all the sync requests in LayerTreeCoordinatorProxy
103522 might be a similar issue to this. Trying the attached patch in 103522 to verify if it solves this issue too
Kalyan
The attached patch in 103522 seems to fix this too. Not marking this as duplicate since this issue cannot be reproduced with Qt port.
Jesus Sanchez-Palencia
(In reply to comment #4)
> The attached patch in 103522 seems to fix this too. Not marking this as duplicate since this issue cannot be reproduced with Qt port.
Yep, it seems to fix. I will leave this bug open until we can confirm that.
Kenneth Rohde Christiansen
This seems fixed in trunk now, can someone confirm?
Kalyan
(In reply to comment #6)
> This seems fixed in trunk now, can someone confirm?
Yes, this is fixed in trunk now. Changing the status to resolved.
Jesus Sanchez-Palencia
Sorry for the late response, yep, it is fixed.