Bug 111419

Summary: Web Inspector: identify reflection layers in LayerTreeAgent
Product: WebKit Reporter: Antoine Quint <graouts>
Component: Web Inspector (Deprecated)Assignee: Antoine Quint <graouts>
Status: RESOLVED FIXED    
Severity: Normal CC: apavlov, joepeck, keishi, loislo, pfeldman, pmuellr, timothy, vsevik, web-inspector-bugs, webkit-bug-importer, webkit.review.bot, yurys
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch
none
Patch for landing none

Antoine Quint
Reported 2013-03-05 03:56:20 PST
Some layers are created to provide the reflection of an element, as provided by the CSS property -webkit-box-reflect. Since these layers' renderer is not directly associated to a Node and we'll probably want to identify as such in the UI, we should clearly identify such layers as reflection layers.
Attachments
Patch (13.52 KB, patch)
2013-03-05 06:01 PST, Antoine Quint 		no flags
DetailsFormatted DiffDiff
Patch for landing (13.52 KB, patch)
2013-03-05 14:09 PST, Antoine Quint 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2013-03-05 03:56:45 PST
<rdar://problem/13346525>
Antoine Quint
Comment 2 2013-03-05 06:01:26 PST
Created attachment 191480 [details] Patch
Dean Jackson
Comment 3 2013-03-05 12:27:09 PST
Comment on attachment 191480 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=191480&action=review > Source/WebCore/ChangeLog:10 > + id, since there is no node per-se directly associated to this layer. s/to/with
Antoine Quint
Comment 4 2013-03-05 14:09:07 PST
Created attachment 191559 [details] Patch for landing
WebKit Review Bot
Comment 5 2013-03-05 14:50:58 PST
Comment on attachment 191559 [details] Patch for landing Clearing flags on attachment: 191559 Committed r144824: <http://trac.webkit.org/changeset/144824>
WebKit Review Bot
Comment 6 2013-03-05 14:51:02 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.