Bug 105604

Summary: [Chromium] Add methods to allow tagging specific WebLayers
Product: WebKit Reporter: Leandro Graciá Gil <leandrogracia>
Component: WebKit APIAssignee: Leandro Graciá Gil <leandrogracia>
Status: RESOLVED WONTFIX    
Severity: Normal CC: abarth, dglazkov, fishd, jamesr, nduca, tkent+wkapi, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Leandro Graciá Gil
Reported 2012-12-20 19:41:55 PST
Currently there are to unrelated features that require tagging specific WebLayer objects from WebKit so that they can be recognised and processed later in the Chromium side. This patch proposes a way to tag them in a minimalistic way in order to provide a solution to these and future features.
Attachments
Patch (1.94 KB, patch)
2012-12-20 19:50 PST, Leandro Graciá Gil 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Leandro Graciá Gil
Comment 1 2012-12-20 19:50:03 PST
Created attachment 180464 [details] Patch
WebKit Review Bot
Comment 2 2012-12-20 19:52:24 PST
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Leandro Graciá Gil
Comment 3 2012-12-20 21:13:06 PST
Suggested implementation of this API: https://codereview.chromium.org/11659004/
Leandro Graciá Gil
Comment 4 2012-12-31 05:33:40 PST
Seems we won't be needing this feature for now. However, feel free to reopen this if it becomes useful anytime later.
Eric Seidel (no email)
Comment 5 2013-01-04 00:56:14 PST
Comment on attachment 180464 [details] Patch Cleared review? from attachment 180464 [details] so that this bug does not appear in http://webkit.org/pending-review. If you would like this patch reviewed, please attach it to a new bug (or re-open this bug before marking it for review again).
Note You need to log in before you can comment on or make changes to this bug.