WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
Bug 90298
Add new CSS property "-webkit-widget-region" to expose dashboard region support for other port
https://bugs.webkit.org/show_bug.cgi?id=90298
Summary
Add new CSS property "-webkit-widget-region" to expose dashboard region suppo...
Jian Li
Reported
2012-06-29 10:59:19 PDT
In Chromium port, we're working on supporting frameless windows for extensions, that allow the web contents to have complete control of the window. Frameless windows do not have the standard frame and the web contents cover the whole window. Thus we need to provide a way to let the web contents denote which part of the content area can be used to drag the window. For example, the web contents draw the custom titlebar with the icon, title, close button and etc. We want to let the user be able to drag the titlebar in order to move the window around. WebKit has already implemented the dashboard region support and exposed a special CSS property -webkit-dashboard-region that lets you specify regions for certain purpose, i.e. being excluded from dragging. The syntax of this property is: -webkit-dashboard-region: dashboard-region(label geometry-type offset-top offset-right offset-bottom offset-left) We would like to introduce another CSS property "-webkit-widget-region", that is essentially a synonym of "-webkit-dashboard-region", since we do not want to get confused with dashboard region support in Apple/WebKit. -webkit-widget-region: region(label geometry-type offset-top offset-right offset-bottom offset-left) Currently the existing dashboard region codes are wrapped inside the feature guard ENABLE(DASHBOARD_SUPPORT). We would like to put this new CSS property in a new feature guard, ENABLE(WIDGET_REGION_SUPPORT) such that "-webkit-dashboard-region" is only provided under ENABLE(DASHBOARD_SUPPORT) as it is now and "-webkit-widget-region" is only exposed under ENABLE(WIDGET_REGION_SUPPORT).
Attachments
Proposed Patch
(44.58 KB, patch)
2012-06-29 11:41 PDT
,
Jian Li
dimich
: review-
jianli
: commit-queue-
Details
Formatted Diff
Diff
Proposed Patch
(65.76 KB, patch)
2012-07-23 13:11 PDT
,
Jian Li
abarth
: review+
jianli
: commit-queue-
Details
Formatted Diff
Diff
Patch after sync
(66.46 KB, patch)
2012-07-31 15:47 PDT
,
Jian Li
no flags
Details
Formatted Diff
Diff
Patch with GTK fix
(68.01 KB, patch)
2012-07-31 17:41 PDT
,
Jian Li
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Jian Li
Comment 1
2012-06-29 11:41:40 PDT
Created
attachment 150230
[details]
Proposed Patch
Gustavo Noronha (kov)
Comment 2
2012-06-29 12:31:06 PDT
Comment on
attachment 150230
[details]
Proposed Patch
Attachment 150230
[details]
did not pass gtk-ews (gtk): Output:
http://queues.webkit.org/results/13107507
Jian Li
Comment 3
2012-07-02 15:15:28 PDT
Darin, could you please take a look at this patch? Or if you know someone else who can review this, please let me know. Thanks. I've sent our proposal to webkit-dev. So far I have not received any objection.
http://lists.webkit.org/pipermail/webkit-dev/2012-June/021257.html
Jian Li
Comment 4
2012-07-19 10:51:24 PDT
(In reply to
comment #3
)
> Darin, could you please take a look at this patch? Or if you know someone else who can review this, please let me know. Thanks. > > I've sent our proposal to webkit-dev. So far I have not received any objection. >
http://lists.webkit.org/pipermail/webkit-dev/2012-June/021257.html
Darin, any comment on this patch? Thanks.
Dmitry Titov
Comment 5
2012-07-19 12:03:37 PDT
Comment on
attachment 150230
[details]
Proposed Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=150230&action=review
I quickly looked at the patch itself... It seems it doesn't build on GTK (see EWS failure). Also, it adds a CSS property but does not have tests that verify that it is actually exposed. Could you add a test or is the plan to not enable the feature now and enable it in builds with a test as a subsequent patch? It seems ok to use the existing support that was implemented for Dashboard Widgets (if not, I hope Apple folks will chime in) - but it seems, on a cursory look, that test support for this is thin. If we are to use this mechanism, we'll need to add way more layout tests. Can be done in other patches, of course.
> Source/WebCore/css/CSSParser.cpp:4252 > +#if ENABLE(DASHBOARD_SUPPORT)
This makes DASHBOARD_SUPPORT and WIDGET_REGION mutually exclusive, when they should not be, or we can't have a build with both enabled...
Jian Li
Comment 6
2012-07-23 13:11:29 PDT
Created
attachment 153849
[details]
Proposed Patch This path made both defines not mutually exclusive.
Adam Barth
Comment 7
2012-07-31 14:31:15 PDT
Comment on
attachment 153849
[details]
Proposed Patch Ok. Once the System Applications working group finishes booting up, we should take this proposal to the CSS working group.
Jian Li
Comment 8
2012-07-31 15:47:41 PDT
Created
attachment 155654
[details]
Patch after sync
Jian Li
Comment 9
2012-07-31 17:41:29 PDT
Created
attachment 155691
[details]
Patch with GTK fix
WebKit Review Bot
Comment 10
2012-07-31 17:45:04 PDT
Comment on
attachment 155654
[details]
Patch after sync Cleared Adam Barth's review+ from obsolete
attachment 155654
[details]
so that this bug does not appear in
http://webkit.org/pending-commit
.
WebKit Review Bot
Comment 11
2012-08-01 17:14:46 PDT
Comment on
attachment 155691
[details]
Patch with GTK fix Clearing flags on attachment: 155691 Committed
r124389
: <
http://trac.webkit.org/changeset/124389
>
Kent Tamura
Comment 12
2012-08-01 19:04:29 PDT
Jian, would you update
http://trac.webkit.org/wiki/FeatureFlags
please?
Ahmad Saleem
Comment 13
2022-10-05 17:00:44 PDT
This seems to have landed and didn't back out:
https://github.com/WebKit/WebKit/commit/c6b05e305a47e41ab9bde4ffe8e5cb7c43430e29
Marking this as "RESOLVED FIXED". Thanks!
Radar WebKit Bug Importer
Comment 14
2022-10-05 17:01:30 PDT
<
rdar://problem/100830051
>
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