WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
68055
[WEBKIT2] WebKitWebFrame WebKit1 style API implementation
https://bugs.webkit.org/show_bug.cgi?id=68055
Summary
[WEBKIT2] WebKitWebFrame WebKit1 style API implementation
Nayan Kumar K
Reported
2011-09-13 21:41:29 PDT
Add WebKitWebFrame WebKit1 style GTK API
Attachments
WebKitWebFrame WebKit1 style API
(9.52 KB, patch)
2011-09-13 22:06 PDT
,
Nayan Kumar K
gustavo
: commit-queue-
Details
Formatted Diff
Diff
WebKitWebFrame WebKit1 style API implementation
(18.90 KB, patch)
2011-09-14 00:04 PDT
,
Nayan Kumar K
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Nayan Kumar K
Comment 1
2011-09-13 22:06:24 PDT
Created
attachment 107285
[details]
WebKitWebFrame WebKit1 style API Draft patch illustrating the WebKitWebFrame WebKit1 style API implementation. I had to make changes in platform dependent code (LoaderClient) to know when a mainFrame is created (Similar changes might have to be done for sub frame creation as well). Right now this patch just implements didCreateMainFrame and creates WebKitWebFrame main frame object once this callback gets called.
Gustavo Noronha (kov)
Comment 2
2011-09-13 22:11:04 PDT
Comment on
attachment 107285
[details]
WebKitWebFrame WebKit1 style API
Attachment 107285
[details]
did not pass gtk-ews (gtk): Output:
http://queues.webkit.org/results/9657402
Nayan Kumar K
Comment 3
2011-09-14 00:04:29 PDT
Created
attachment 107298
[details]
WebKitWebFrame WebKit1 style API implementation Oops.. Missed git add'ing newly created files in earlier patch.
WebKit Review Bot
Comment 4
2011-09-14 00:06:36 PDT
Attachment 107298
[details]
did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebKit2/ChangeLog', u'Source/WebKit..." exit_code: 1 Source/WebKit2/UIProcess/API/gtk/WebKitWebFrame.h:47: parent_instance is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebFrame.h:54: parent_class is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebFrame.cpp:43: webkit_web_frame_init is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebFrame.cpp:49: webkit_web_frame_class_init is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Source/WebKit2/UIProcess/API/gtk/WebKitWebFrame.cpp:77: webkit_web_frame_get_web_view is incorrectly named. Don't use underscores in your identifier names. [readability/naming] [4] Total errors found: 5 in 10 files If any of these errors are false positives, please file a bug against check-webkit-style.
Alexey Proskuryakov
Comment 5
2011-09-14 10:34:11 PDT
Please don't put [GTK] in summary when a patch touches cross-platform code. The reason for such marks is that people who don't deal with a particular port can quickly skip those bugs. Cross platform changes should not be hidden from domain experts.
Sam Weinig
Comment 6
2011-09-14 12:31:37 PDT
I am not sure this makes sense with regards to the direction we would like to take WebKit2. We would like to de-emphasize frames in the UIProcess as much as possible, and will probably be remove the frame-tree aspects of frames from the UIProcess shortly.
Carlos Garcia Campos
Comment 7
2011-09-14 23:58:18 PDT
Yes, our first idea was to try to keep the same WebKi1 API for WebKit2, so that apps wouldn't need to be ported. But we recently decided to start from scratch designing a new API for WebKit2, and for now, we are not adding a WebKitWebFrame class.
Nayan Kumar K
Comment 8
2011-09-30 08:00:10 PDT
Comment on
attachment 107298
[details]
WebKitWebFrame WebKit1 style API implementation Clearing the review flag, as this bug is no longer valid.
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