summaryrefslogtreecommitdiffstats
path: root/webkit/glue/webframe_impl.cc
Commit message (Collapse)AuthorAgeFilesLines
* Extract form related classes from the guts of WebFrameImpl.darin@chromium.org2009-06-151-0/+19
| | | | | | | | | | | | | | | | | | | Instead of having WebFrameImpl generate SearchableFormData, PasswordForm, and AutofillForm classes, allow the embedder (RenderView) to do so. This is done to help minimize the dependencies WebFrameImpl has on other code, which will make it easier to move WebFrame and WebDataSource into the WebKit API. Most significant change: Now, RenderView always sets a NavigationState on WebDataSource instances. We used to only do so for browser initiated navigations. This is done so that we can store things like SearchableFormData and friends on the NavigationState. To facilitate this change, it was necessary to add a way through the WebKit API to refer to a HTMLFormElement. This CL introduces WebForm, which is like a RefPtr<HTMLFormElement>, so you can just copy a WebForm around by value and the right thing happens. Some of the other changes are about moving more things into the webkit_glue namespace. On hindsight, I probably should have done that as a separate CL. BUG=10041 TEST=none R=brettw Review URL: http://codereview.chromium.org/126083 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18395 0039d316-1c4b-4281-b951-d872f2087c98
* WebKit 44372:44405, resubmit.dimich@google.com2009-06-041-9/+5
| | | | | | | | | | | | | | | | Fixed Mac build (needed to remove a file that was removed upstream). Added expected Linux layout tests failures from the first landing attempt. Removing the chromium-specific snapshot for list-wrapping-image-crash-expected.html test because the test was incorrectly added upstream. Will fix it upstream and then re-enable in Chromium. Original code review: http://codereview.chromium.org/118215 TBR=ukai BUG=13305, 13313, 13314 (layout tests - reenable, rebaseline) TEST=none Review URL: http://codereview.chromium.org/119156 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17616 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 17601 (build break on mac)dimich@google.com2009-06-041-5/+9
| | | | | | | | TBR=ukai BUG=none TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17602 0039d316-1c4b-4281-b951-d872f2087c98
* WebKit DEP roll 44372:44405dimich@google.com2009-06-041-9/+5
| | | | | | | | | | BUG=none TEST=no compile or layout test failures. There is a change (http://trac.webkit.org/changeset/44401) here which will likely break quite a few Linux layout tests. The plan is to run the build, then add all the tests with REBASELINE keyword into test_expectations.txt for automated rebaselining. Review URL: http://codereview.chromium.org/118215 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17601 0039d316-1c4b-4281-b951-d872f2087c98
* Find in page should cause the scrollbar to repaint with tick marks.tc@google.com2009-06-031-1/+1
| | | | | | | | | | | | This method is used to invalidate the scrollbar which causes it to repaint. Enable this code to run on linux too. BUG=11706 Review URL: http://codereview.chromium.org/118089 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17504 0039d316-1c4b-4281-b951-d872f2087c98
* Add functions to glue to get the full html of the page and also to check if ↵sverrir@google.com2009-06-021-0/+10
| | | | | | | | | | | the user has selected something. This is for enhanced printing support (in progress). Review URL: http://codereview.chromium.org/119043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17427 0039d316-1c4b-4281-b951-d872f2087c98
* Have the find bar show number of matches on linux.tc@google.com2009-06-011-2/+2
| | | | | | | | | | | | We needed to enable some code in webkit/glue/webframe_impl.cc and add a line to clear the results in find_bar_gtk.cc. BUG=12955 Review URL: http://codereview.chromium.org/115960 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@17335 0039d316-1c4b-4281-b951-d872f2087c98
* Ensure we have a Cocoa NSGraphicsContext when needed.jrg@chromium.org2009-05-261-0/+2
| | | | | | | | | | | | For now we still use Cocoa so we need a NSGraphicsContext when drawing (not just a CGContext). BUG=12474 See related CL http://codereview.chromium.org/114020 Review URL: http://codereview.chromium.org/115732 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16886 0039d316-1c4b-4281-b951-d872f2087c98
* Make WebRequest be a wrapper for ResourceRequest instead of FrameLoadRequest.darin@chromium.org2009-05-221-2/+1
| | | | | | | | | | | | | It turns out that no one was ever reading the frameName field, so this change is quite trivial. BUG=10038 TEST=none R=brettw Review URL: http://codereview.chromium.org/115713 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16780 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the HistoryState property of WebRequest.darin@chromium.org2009-05-221-5/+14
| | | | | | | | | | | | | | | | | In the new WebKit API, it seems best if WebRequest is just a wrapper for WebCore::ResourceRequest since in most contexts that's what we need it to be. The solution here is to introduce a LoadHistoryState method on WebFrame that can be used to navigate to a session history item. BUG=10038 TEST=covered by existing back/forward navigation tests. R=brettw Review URL: http://codereview.chromium.org/113758 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16747 0039d316-1c4b-4281-b951-d872f2087c98
* Remove a field that is now unused. This was made obsoletedarin@chromium.org2009-05-211-13/+2
| | | | | | | | | | by the change to eliminate WebRequest::Get/SetExtraData. R=brettw Review URL: http://codereview.chromium.org/113694 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16611 0039d316-1c4b-4281-b951-d872f2087c98
* Move ExtraData from WebRequest to WebDataSource.darin@chromium.org2009-05-211-21/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a DidCreateDataSource method to WebViewDelegate, which the embedder uses to know if their LoadRequest resulted in a navigation. The embedder then associates the ExtraData with the WebDataSource at that point. The WebDataSource then proceeds to be treated as the provisional data source, possibly failing or being committed. We then inspect WebFrame::GetDataSource in DidCommitLoadForFrame to recover the ExtraData. We have to take care to handle reference fragment navigations since those do not result in a new WebDataSource being created. So, in DidChangeLocationWithinPage, we update the ExtraData associated with the WebDataSource returned by WebFrame::GetDataSource. One thing that is important to note: In DidCommitLoadForFrame, we would previously always inspect the value of GetDataSource returned from the main frame instead of looking at the frame passed to DidCommitLoadForFrame. This explains why WebFrameImpl:: LoadRequest needed to cached ExtraData on the current WebDataSource, and I think doing so is awkward and wrong. My change is to always store the ExtraData on the first WebDataSource to be created as a result of LoadRequest. Then in DidCommitLoadForFrame, I always inspect the ExtraData from the given WebFrame. This means that for history navigations that only navigate a subframe, we'll end up with ExtraData associated with the WebDataSource of a subframe. I think this is OK even though the old code was trying to avoid this scenario. See the DCHECK removed in RenderView::UpdateURL. BUG=11423 R=brettw Review URL: http://codereview.chromium.org/115575 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16580 0039d316-1c4b-4281-b951-d872f2087c98
* ScriptController.* needs to be reformatted into WebKit style.levin@chromium.org2009-05-181-1/+1
| | | | | | | | | | TEST=Scripting in the browser. This should be pretty well covered by other testing. BUG=http://crbug.com/12063 Review URL: http://codereview.chromium.org/115417 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@16315 0039d316-1c4b-4281-b951-d872f2087c98
* Re-do r15244 again.darin@chromium.org2009-05-131-13/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally reviewed at http://codereview.chromium.org/100353 Eliminate webkit/glue/webhistoryitem* in favor of adding a NavigateBackForwardSoon method WebViewDelegate. This moves all of the hacky details of how we intercept "history.{back, forward,go}" into the webkit layer. My eventual plan is to teach WebCore how to make this not hacky. In this version of the CL, TestWebViewDelegate performs the back/forward navigation directly in NavigateBackForwardSoon instead of using PostTask to delay it. I'm doing this to minimize regressions so that I can hopefully get the rest of this CL landed. I also already made the changes to WebKit to force history. {back,forward,go} to be processed asynchronously. Finally, it was necessary to move DumpBackForwardList out of webkit_glue.cc since it was using itemAtIndex to generate those results, and now that we return synthetic URLs for that function, the results were very wrong. The fix is to move DumpBackForwardList into TestShell so that it can more directly inspect the TestNavigationController. Now, it is necessary for webkit_glue.h to expose a function to dump a content state string (aka a WebCore::HistoryItem). BUG=11423 R=mpcomplete Review URL: http://codereview.chromium.org/113328 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15997 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r15940 again. Unexpected layout test failures :(darin@chromium.org2009-05-131-2/+13
| | | | | | | TBR=mpcomplete git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15942 0039d316-1c4b-4281-b951-d872f2087c98
* Re-do r15244 again.darin@chromium.org2009-05-131-13/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Originally reviewed at http://codereview.chromium.org/100353 Eliminate webkit/glue/webhistoryitem* in favor of adding a NavigateBackForwardSoon method WebViewDelegate. This moves all of the hacky details of how we intercept "history.{back, forward,go}" into the webkit layer. My eventual plan is to teach WebCore how to make this not hacky. In this version of the CL, TestWebViewDelegate performs the back/forward navigation directly in NavigateBackForwardSoon instead of using PostTask to delay it. I'm doing this to minimize regressions so that I can hopefully get the rest of this CL landed. I also already made the changes to WebKit to force history. {back,forward,go} to be processed asynchronously. BUG=11423 TBR=mpcomplete Review URL: http://codereview.chromium.org/115288 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15940 0039d316-1c4b-4281-b951-d872f2087c98
* This change makes sure we always have a valid NSGraphicsContext, a jobjrg@chromium.org2009-05-121-0/+4
| | | | | | | | | | | | | | | | | | | | normally done implicitly by Cocoa. This fixes the misspell underline problem. Briefly, this change allows any Cocoa rendering to work. I had hoped to (eventually) eliminate all Cocoa in Mac Chromium WebKit. (The Chromium renderer isn't really a Cocoa app, so it makes sense). However, that goal appears to diverge from Apple's goal of a single "Mac" port. Even if I can eliminate all Cocoa use, the long-term safe thing to do is to make sure any Cocoa drawing will "just work". The assumption is that it'll either show up randomly (and crash), or be difficult to get removed quickly (like the original misspell change). Review URL: http://codereview.chromium.org/114020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15866 0039d316-1c4b-4281-b951-d872f2087c98
* Split V8Proxy::retrieveActiveFrame() into two methods.aa@chromium.org2009-05-121-2/+13
| | | | | | | | | | | | | | | | | | We now have RetrieveFrameForCurrentContext() and RetrieveFrameForEnteredContext(). These terms means the same thing they do in V8::Context -- 'current' is the top of the js stack and 'entered' is the bottom. I needed 'entered' to fix a bug in extensions where if you call an extension API through the web inspector we get confused and think the web inspector's view is the one who called. Review URL: http://codereview.chromium.org/113085 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15828 0039d316-1c4b-4281-b951-d872f2087c98
* Move WebKit API to src/webkit/api.darin@chromium.org2009-05-101-5/+5
| | | | | | | | R=dglazkov Review URL: http://codereview.chromium.org/113186 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15739 0039d316-1c4b-4281-b951-d872f2087c98
* There are cases where a Frame may outlive its associated Page. Get thedarin@chromium.org2009-05-061-16/+29
| | | | | | | | | | | | | | | | WebViewImpl by accessing it indirectly through the Frame's Page so that we don't have to worry about cleaning up the WebFrameImpl -> WebViewImpl pointer. WebCore already clears the Frame's Page pointer when the Page is destroyed by the WebViewImpl. Patch by Marshall Greenblatt R=darin Review: http://codereview.chromium.org/99283 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15458 0039d316-1c4b-4281-b951-d872f2087c98
* Chrome changes for WebKit merge 43114:43242darin@chromium.org2009-05-051-0/+1
| | | | | | | | R=dglazkov Review URL: http://codereview.chromium.org/109042 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15338 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r15278. More unexpected test failures :(darin@chromium.org2009-05-051-2/+13
| | | | | | | | TBR=mpcomplete Review URL: http://codereview.chromium.org/108005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15279 0039d316-1c4b-4281-b951-d872f2087c98
* Re-do r15244: Fix crash in ~TestWebViewDelegate caused bydarin@chromium.org2009-05-051-13/+2
| | | | | | | | | | | | | | | | | | shell_ being null. Moved the RevokeDragDrop call to the TestShell destructor instead. Eliminate webkit/glue/webhistoryitem* in favor of adding a NavigateBackForwardSoon method WebViewDelegate. This moves all of the hacky details of how we intercept "history.{back, forward,go}" into the webkit layer. My eventual plan is to teach WebCore how to make this not hacky. BUG=11423 R=mpcomplete Review URL: http://codereview.chromium.org/108004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15278 0039d316-1c4b-4281-b951-d872f2087c98
* Fix bug 9812: Remove current RSS code in favor of new more generalizedfinnur@chromium.org2009-05-041-63/+0
| | | | | | | | | | | | PageAction code that serves the same purpose (and more). BUG=9812 TEST=No test needed, this shouldn't result in any noticable difference since the RSS parsing was disabled. Review URL: http://codereview.chromium.org/100356 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15247 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r15244. Failed tests :(darin@chromium.org2009-05-041-2/+13
| | | | | | | | TBR=mpcomplete Review URL: http://codereview.chromium.org/99370 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15246 0039d316-1c4b-4281-b951-d872f2087c98
* Eliminate webkit/glue/webhistoryitem* in favor of adding adarin@chromium.org2009-05-041-13/+2
| | | | | | | | | | | | | | NavigateBackForwardSoon method WebViewDelegate. This moves all of the hacky details of how we intercept "history.{back, forward,go}" into the webkit layer. My eventual plan is to teach WebCore how to make this not hacky. BUG=11423 R=mpcomplete Review URL: http://codereview.chromium.org/100353 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@15244 0039d316-1c4b-4281-b951-d872f2087c98
* Rev 12100 changed the way that we spool and render printed output, most notablymaruel@chromium.org2009-04-271-0/+14
| | | | | | | | | | | | | | | | | | | | introducing use of the PrintContext class. The existing PrintContext::spoolPage() method applies a webkit scaling factor before rendering output to the graphics context. ChromePrintContext::spoolPage() (in webframe_impl.cc), which is used by chromium instead of PrintContext::spoolPage(), does not apply this scaling factor, but instead eventually returns the scaling factor via WebFrame::PrintPage(). This is a problem for the Chromium Embedded Framework (CEF) because, unlike chromium, the CEF renders directly to the printer device context. It is therefore important for CEF that we retrieve and apply the webkit scaling factor before calling PrintPage(). In order to support this capability the following adds a WebFrame::GetPrintPageShrink() method. Patch contributed by Marshall Greenblatt <magreenblatt@gmail.com> Review: http://codereview.chromium.org/99058 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14639 0039d316-1c4b-4281-b951-d872f2087c98
* More linux ifdef tweaks. This reverts my earlier change (13503).sky@chromium.org2009-04-271-1/+1
| | | | | | | | BUG=none TEST=none Review URL: http://codereview.chromium.org/100046 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14628 0039d316-1c4b-4281-b951-d872f2087c98
* Add transparency support to RenderWidgetHostView.aa@chromium.org2009-04-231-0/+3
| | | | | | | | | | | | This is used to make the background behind toolstrips 'shine through' them. It isn't possible to make them really transparent due to cleartype (cleartype must know the pixels behind the text to work), so instead we paint the background we want behind the transparent webview. Review URL: http://codereview.chromium.org/88076 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14378 0039d316-1c4b-4281-b951-d872f2087c98
* Merge: chromium side [42671:42725]levin@chromium.org2009-04-231-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Rebaselines: http://trac.webkit.org/changeset/42722 resulted in LayoutTests/editing/inserting/insert-3907422-fix.html LayoutTests/editing/pasteboard/paste-text-015.html LayoutTests/editing/style/font-family-with-space.html http://trac.webkit.org/changeset/42723 resulted in LayoutTests/editing/selection/select-all-iframe.html LayoutTests/svg/custom/pointer-events-path.svg http://trac.webkit.org/changeset/42716 resulted in LayoutTests/fast/dom/HTMLSelectElement/named-options.html http://trac.webkit.org/changeset/42725 Broke the close event behavior and resulted in disabling these ui tests: * BrowserCloseBeforeUnloadOK and * BrowserCloseBeforeUnloadCancel Review URL: http://codereview.chromium.org/92051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14291 0039d316-1c4b-4281-b951-d872f2087c98
* Rename AllowCrossOriginAccessHack to GrantUniversalAccess, and move the HACKmpcomplete@google.com2009-04-171-1/+1
| | | | | | | warnings to the callsite. Review URL: http://codereview.chromium.org/79028 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13953 0039d316-1c4b-4281-b951-d872f2087c98
* Fix 10573: Dismissing Find-in page doesn't set focusfinnur@chromium.org2009-04-171-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | to the link found. We no longer use the selection controller to highlight the active match. Before this change, the focus would not be set if the user had changed the selection. After this change, the focus will be set unless the user has selected something on the page. I also wrote an in-browser unit test for this to catch this regression in the future, but it is disabled due to problem with running multiple in-process browser tests in a row (teardown problem). BUG=10573 TEST=Covered by in process browser test now, see bug for repro steps. Review URL: http://codereview.chromium.org/79024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13945 0039d316-1c4b-4281-b951-d872f2087c98
* Chrome changes to support WebKit API changes.darin@chromium.org2009-04-161-50/+2
| | | | | | | | | | | | | | | Also, I removed the GetWebFrame method on WebDataSource since it is not actually needed. Removed some dead-code from webframe_impl.cc. Removed some bogus null-checking of WebCore::Frame::loader(). R=dglazkov Review URL: http://codereview.chromium.org/67169 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13844 0039d316-1c4b-4281-b951-d872f2087c98
* Add a hack to enable cross-origin XHR for all pages with a "chrome-extension"mpcomplete@google.com2009-04-151-0/+7
| | | | | | | | URL as the toplevel frame. This is a temporary workaround until we can do it the proper way, which requires a webkit refactoring in progress by Alexei. Review URL: http://codereview.chromium.org/67153 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13790 0039d316-1c4b-4281-b951-d872f2087c98
* Let WebKit draw the active highlight for FindInPage,finnur@chromium.org2009-04-101-11/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | instead of using the SelectionController. This fixes a couple of bugs, such as: Active match highlighting disappears when mouse selection is made within the page and selection color is orange (6145). and Selection color becomes orange in some cases on tabs that don't have a Find box open. and Gmail jumping to the first match if on FindNext if Find box is closed and reopened (9795). NOTE: This patch depends on my patch to WebKit that just got accepted. See: https://bugs.webkit.org/show_bug.cgi?id=25102 BUG=6145, 9795 TEST=Find something on a page that results in multiple matches being found. Highlight another word that is not currently highlighted. You should see both active and inactive highlights (orange and yellow) and a blue colored selection highlight. Review URL: http://codereview.chromium.org/66016 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13510 0039d316-1c4b-4281-b951-d872f2087c98
* Adds some ifdefs so that test_shell can be compiled on linuxsky@chromium.org2009-04-101-1/+1
| | | | | | | | | | | | | without GTK. I had to recreate this patch as my workspace for various resonds. UGH! BUG=none TEST=none Review URL: http://codereview.chromium.org/67024 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13503 0039d316-1c4b-4281-b951-d872f2087c98
* Switch to using WebPoint, WebRect, and WebSize in more of the gluedarin@chromium.org2009-04-091-23/+24
| | | | | | | | | | | | | | | | | layer interface. This will help when we move those interfaces into the WebKit API. This is a second attempt at r13381, which was already reviewed here: http://codereview.chromium.org/63126 The only change between that CL and this one is in render_view.h, where I needed to change a parameter type from gfx::Rect to WebRect. TBR=dglazkov Review URL: http://codereview.chromium.org/64005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13424 0039d316-1c4b-4281-b951-d872f2087c98
* Reverting dfisher changes 133386 and 13381cpu@google.com2009-04-081-23/+20
| | | | | | | | | | TBR=darin Review URL: http://codereview.chromium.org/58018 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13387 0039d316-1c4b-4281-b951-d872f2087c98
* Switch to using WebPoint, WebRect, and WebSize in more of the gluedarin@chromium.org2009-04-081-20/+23
| | | | | | | | | | | layer interface. This will help when we move those interfaces into the WebKit API. R=dglazkov Review URL: http://codereview.chromium.org/63126 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13381 0039d316-1c4b-4281-b951-d872f2087c98
* Adds new messages and widens some existing messages between the renderer and ↵michaeln@google.com2009-04-071-1/+37
| | | | | | | | browser processes to support an implementation of the HTML5AppCache spec with most of the logic running in the browser process. The gist of most of the changes are to indicate which frame each resource request is coming from, and to indicate which appcache each response was retrieved from (if any).See https://docs.google.com/a/google.com/Doc?docid=agv6ghfsqr_15f749cgt3&hl=en Review URL: http://codereview.chromium.org/9712 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13258 0039d316-1c4b-4281-b951-d872f2087c98
* Stop serializing WebString over IPC. The new rule is that only POD (plain olddarin@chromium.org2009-04-061-29/+35
| | | | | | | | | | | | | data) types from WebKit API are allowed to be used in the browser process. I added a big note about this to webkit_param_traits.h to explain the details of this decision. R=dglazkov Review URL: http://codereview.chromium.org/62032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13181 0039d316-1c4b-4281-b951-d872f2087c98
* Callbacks through ChromeClient->RenderView->RenderViewHost for ↵rafaelw@chromium.org2009-04-041-0/+10
| | | | | | | | ContentsDidChangeSize so that extensions can change their toolbar size when the contained contents changes size. Review URL: http://codereview.chromium.org/56122 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13130 0039d316-1c4b-4281-b951-d872f2087c98
* - Added support for keeping track of load times.davemoore@chromium.org2009-04-031-1/+0
| | | | | | | | | | | | | | | | | For each document loaded we record the time the page was requested by the user (or as close as we can get to that), the time the load process started, the time the document and it's dependent resources (scripts) have been loaded (before onload()) and the time all the document's resources have been loaded. We use this data for two things: 1) We histogram the deltas between the time marks 2) We expose the times to javascript running on the page which was loaded Review URL: http://codereview.chromium.org/42527 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13116 0039d316-1c4b-4281-b951-d872f2087c98
* Use WebConsoleMessage instead of ConsoleMessageLevel.darin@chromium.org2009-03-311-8/+9
| | | | | | | | R=dglazkov Review URL: http://codereview.chromium.org/57073 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12916 0039d316-1c4b-4281-b951-d872f2087c98
* Use WebScriptSource and WebFindInPageRequest from the WebKit API.darin@chromium.org2009-03-311-23/+27
| | | | | | | | | | | | | | | | | | This change introduces some helper functions in glue_util.cc for efficient conversion between WebString and WebCore::String when inside the implementation of webkit/glue. This is a temporary change since eventually all code in glue that uses WebCore will be moved into the WebKit API implementation. Instead of making the Chrome automation use WebFindInPageRequest, I decided to introduce AutomationMsg_Find_Params as a copy of the old FindInPageRequest structure. That preserves the IPC protocol and avoids making the automation library depend on WebKit. R=dglazkov Review URL: http://codereview.chromium.org/57060 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12881 0039d316-1c4b-4281-b951-d872f2087c98
* Update our webframe_impl to use loadURLIntoChildFrame().playmobil@google.com2009-03-311-31/+4
| | | | | | Review URL: http://codereview.chromium.org/57061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12867 0039d316-1c4b-4281-b951-d872f2087c98
* Chrome side of WebKit merge 42026:42115playmobil@google.com2009-03-311-0/+1
| | | | | | Review URL: http://codereview.chromium.org/57033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12861 0039d316-1c4b-4281-b951-d872f2087c98
* Add basic infrastructure for sending async browser API request and receiving ↵aa@chromium.org2009-03-241-0/+9
| | | | | | | | results. Review URL: http://codereview.chromium.org/42262 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12347 0039d316-1c4b-4281-b951-d872f2087c98
* Convert FindInPage wstrings to string16.tc@google.com2009-03-191-4/+4
| | | | | | | Review URL: http://codereview.chromium.org/42408 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12158 0039d316-1c4b-4281-b951-d872f2087c98
* Remove code duplicated from webcore and use the common PrintContext facility.maruel@chromium.org2009-03-191-88/+70
| | | | | | Review URL: http://codereview.chromium.org/20470 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@12100 0039d316-1c4b-4281-b951-d872f2087c98