Bug 113429 - [EFL][WK2] Rendering artifacts or a previous page when starting MiniBrowser again.
Summary: [EFL][WK2] Rendering artifacts or a previous page when starting MiniBrowser a...
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit EFL (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Joone Hur
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-27 11:28 PDT by Joone Hur
Modified: 2017-03-11 10:46 PST (History)
9 users (show)

See Also:


Attachments
Patch (1.77 KB, patch)
2013-03-27 16:47 PDT, Joone Hur
cdumez: review-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Joone Hur 2013-03-27 11:28:23 PDT
When starting MiniBrowser again, we can see artifacts or a previous page sometimes before loading a new page.
Comment 1 Joone Hur 2013-03-27 16:47:40 PDT
Created attachment 195434 [details]
Patch
Comment 2 Carsten Haitzler (Rasterman) 2013-03-29 03:58:24 PDT
no - bad. evas_norender() has nothing to do with drawing. it's basically a garbage collect cycle for evas. (evas deleted objects after rendering that have been deleted previously but are deferred to handle calculating deltas in the canvas). norender() is not something you should touch unless you have VERY special circumstances. you should NEVER call it if any canvas content could have visually changed between the last render and when you call it. it's only real use is to garbage collect objects you added and then deleted without ever showing them (e.g. you use evas as a workhorse to hold image objects and are just querying images for sizes by creating an image object, setting file path, getting size, then deleting it - it is this kind of "rare case" that norender was made to handle). your problem is elsehwere. i suspect your artifacts went away because evas lost update info for the canvas with norender and thus simply forgot about your artifacts. the source of your bug is back in the object you have that is causing the artifacts. it has uninitialized content. don't show the object until it's ready to be shown.
Comment 3 Chris Dumez 2013-05-16 12:55:55 PDT
Comment on attachment 195434 [details]
Patch

r- based on Rasterman's comments.
Comment 4 Michael Catanzaro 2017-03-11 10:46:13 PST
Closing this bug because the EFL port has been removed from trunk.

If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.