WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
92813
[chromium] Make WebKit API support draggable region change update
https://bugs.webkit.org/show_bug.cgi?id=92813
Summary
[chromium] Make WebKit API support draggable region change update
Jian Li
Reported
2012-07-31 16:41:33 PDT
We need to make WebKit API for chromium support draggable region change update.
Attachments
Proposed Patch
(10.46 KB, patch)
2012-07-31 17:08 PDT
,
Jian Li
jianli
: commit-queue-
Details
Formatted Diff
Diff
Proposed Patch
(10.45 KB, patch)
2012-07-31 17:21 PDT
,
Jian Li
abarth
: review+
jianli
: commit-queue-
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Jian Li
Comment 1
2012-07-31 17:08:12 PDT
Created
attachment 155681
[details]
Proposed Patch
WebKit Review Bot
Comment 2
2012-07-31 17:18:00 PDT
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
.
WebKit Review Bot
Comment 3
2012-07-31 17:18:19 PDT
Attachment 155681
[details]
did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/Platform/ChangeLog', u'Source/Platf..." exit_code: 1 Source/WebKit/chromium/src/WebDocument.cpp:248: draggable_regions is incorrectly named. Don't use underscores in your identifier names. [readability/naming/underscores] [4] Total errors found: 1 in 9 files If any of these errors are false positives, please file a bug against check-webkit-style.
Jian Li
Comment 4
2012-07-31 17:21:33 PDT
Created
attachment 155685
[details]
Proposed Patch
Adam Barth
Comment 5
2012-08-01 11:05:26 PDT
Comment on
attachment 155685
[details]
Proposed Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=155685&action=review
> Source/Platform/chromium/public/WebDraggableRegion.h:40 > +struct WebDraggableRegion {
This looks like a wrapper for DashboardRegionValue, which is a WebCore concept, not a WebCore/platform concept. Therefore, this header should be in WebKit/chromium/public rather than in Platform.
> Source/Platform/chromium/public/WebDraggableRegion.h:44 > + int type;
Is this really an enum? Should we create an API for the enum values so we can COMPILE_ASSERT that they match their WebCore counterparts?
> Source/WebKit/chromium/public/WebViewClient.h:384 > + // Draggable regions ----------------------------------------------------
Two blank lines before section headings.
Jian Li
Comment 6
2012-08-01 15:51:38 PDT
(In reply to
comment #5
)
> (From update of
attachment 155685
[details]
) > View in context:
https://bugs.webkit.org/attachment.cgi?id=155685&action=review
> > > Source/Platform/chromium/public/WebDraggableRegion.h:40 > > +struct WebDraggableRegion { > > This looks like a wrapper for DashboardRegionValue, which is a WebCore concept, not a WebCore/platform concept. Therefore, this header should be in WebKit/chromium/public rather than in Platform.
Will fix it at landing time.
> > > Source/Platform/chromium/public/WebDraggableRegion.h:44 > > + int type; > > Is this really an enum? Should we create an API for the enum values so we can COMPILE_ASSERT that they match their WebCore counterparts?
WebCore counterparts also use int type. For now, I am going to keep int type for our version. I am thinking of ignoring the type information (rectangular or circular). We will extract the shape information from the element when CSS shape is fully supported and then update this struct.
> > > Source/WebKit/chromium/public/WebViewClient.h:384 > > + // Draggable regions ---------------------------------------------------- > > Two blank lines before section headings.
Will fix it at landing time.
Adam Barth
Comment 7
2012-08-01 16:27:12 PDT
> WebCore counterparts also use int type. For now, I am going to keep int type for our version. I am thinking of ignoring the type information (rectangular or circular). We will extract the shape information from the element when CSS shape is fully supported and then update this struct.
Just a bare int doesn't make any sense in the API. Perhaps we should omit it for now and add it later when we need it?
Jian Li
Comment 8
2012-08-01 16:30:14 PDT
(In reply to
comment #7
)
> > WebCore counterparts also use int type. For now, I am going to keep int type for our version. I am thinking of ignoring the type information (rectangular or circular). We will extract the shape information from the element when CSS shape is fully supported and then update this struct. > > Just a bare int doesn't make any sense in the API. Perhaps we should omit it for now and add it later when we need it?
Sounds good.
Jian Li
Comment 9
2012-08-01 17:29:00 PDT
Committed as
http://trac.webkit.org/changeset/124394
.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug