commit | 6c397f0069c7ed0aac4af432786e03debfc7e810 | [log] [tgz] |
---|---|---|
author | commit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Oct 23 22:06:46 2019 +0000 |
committer | commit-queue@webkit.org <commit-queue@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Wed Oct 23 22:06:46 2019 +0000 |
tree | fc9b83cd388b93f0f2376ad808d079dc1db9004a | |
parent | 8ae089bfb4ea20b548bc5df72e3095ab96aeef07 [diff] |
Implement dumpResourceLoadStatistics in SQLite ITP Database https://bugs.webkit.org/show_bug.cgi?id=203224 <rdar://problem/56482165> Patch by Kate Cheney <katherine_cheney@apple.com> on 2019-10-23 Reviewed by John Wilander. Source/WebKit: This patch implements dumpResourceLoadStatistics() in the ITP database store. This function required a boolean flag isScheduledForWebsiteDataRemoval that now must be stored in the database, resulting in a small schema change. Because of the schema change, this patch also compares any existing database file against the new schema, and deletes the existing file if the schema is not current. * NetworkProcess/Classifier/ResourceLoadStatisticsDatabaseStore.cpp: The logic for topFrameLinkDecorationsFromQuery was the opposite of all other "xyzFrom" queries. When merging data from the memory store, the load statistic being inserted holds a list of topFrames which it has been redirected to from. I think it makes more sense to also organize the table this way. (WebKit::ObservedDomainsTableSchemaV1): (WebKit::ObservedDomainsTableSchemaV1Alternate): For support on both iOS and MacOS, there are two CREATE TABLE queries to compare to, depending on whether the query result contains quotes around the table name. (WebKit::ResourceLoadStatisticsDatabaseStore::ResourceLoadStatisticsDatabaseStore): (WebKit::ResourceLoadStatisticsDatabaseStore::openITPDatabase): (WebKit::ResourceLoadStatisticsDatabaseStore::openAndDropOldDatabaseIfNecessary): The code to check for the current schema was adapted from SQLiteIDBBackingStore.cpp (WebKit::ResourceLoadStatisticsDatabaseStore::prepareStatements): (WebKit::ResourceLoadStatisticsDatabaseStore::insertObservedDomain): (WebKit::ResourceLoadStatisticsDatabaseStore::ensureAndMakeDomainList): The previous naming of the list parameter in this function was confusing because it is used by many different relationships not just subframes under top frames. (WebKit::ResourceLoadStatisticsDatabaseStore::insertDomainRelationshipList): topFrameLinkDecorationsFrom were never inserted into the database. (WebKit::ResourceLoadStatisticsDatabaseStore::insertDomainRelationships): (WebKit::ResourceLoadStatisticsDatabaseStore::merge): (WebKit::ResourceLoadStatisticsDatabaseStore::mergeStatistic): Since the statement to get all data for a given domain is now used in multiple places, I stored the query as a constexpr auto. (WebKit::ResourceLoadStatisticsDatabaseStore::logCrossSiteLoadWithLinkDecoration): Matched the memory store functionality, which calls the boolean "gotLinkDecorationFromPrevalentResource." I thought isScheduledForWebsiteDataRemoval would be more clear of a name, because this flag gets cleared even when prevalent top frame link decorations for this domain still exist in the table. (WebKit::ResourceLoadStatisticsDatabaseStore::dumpResourceLoadStatistics): (WebKit::ResourceLoadStatisticsDatabaseStore::setIsScheduledForWebsiteDataRemoval): (WebKit::ResourceLoadStatisticsDatabaseStore::prevalentDomains): Deleted. (WebKit::ResourceLoadStatisticsDatabaseStore::domains): To match memory store functionality, the check for website data to delete should check all domains, not just prevalent ones. (WebKit::ResourceLoadStatisticsDatabaseStore::hasHadUnexpiredRecentUserInteraction): (WebKit::ResourceLoadStatisticsDatabaseStore::shouldRemoveAllWebsiteDataFor): This now needs to check if the resource is prevalent, because it is no longer guaranteed. (WebKit::ResourceLoadStatisticsDatabaseStore::shouldRemoveAllButCookiesFor): (WebKit::ResourceLoadStatisticsDatabaseStore::registrableDomainsToRemoveWebsiteDataFor): (WebKit::ResourceLoadStatisticsDatabaseStore::getDomainStringFromDomainID): (WebKit::ResourceLoadStatisticsDatabaseStore::getSubStatisticStatement): (WebKit::ResourceLoadStatisticsDatabaseStore::appendSubStatisticList): (WebKit::ResourceLoadStatisticsDatabaseStore::resourceToString): This functionality matches the toString function in ResourceLoadStatistics.cpp. (WebKit::CompletionHandler<void): * NetworkProcess/Classifier/ResourceLoadStatisticsDatabaseStore.h: LayoutTests: Migrated tests from the memory store to be used to test dumping for database store. Both tests are almost identical to the memory store tests except they set the useITPDatabase flag to true and log-cross-site-load-with-link-decoration-database.html tests one additional domain to be sure that listing multiple domains in a category works in the database store. * http/tests/resourceLoadStatistics/log-cross-site-load-with-link-decoration-database-expected.txt: Added. * http/tests/resourceLoadStatistics/log-cross-site-load-with-link-decoration-database.html: Added. * http/tests/resourceLoadStatistics/website-data-removal-for-site-navigated-to-with-link-decoration-database-expected.txt: Added. * http/tests/resourceLoadStatistics/website-data-removal-for-site-navigated-to-with-link-decoration-database.html: Added. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@251501 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
or
git clone https://git.webkit.org/git/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
If you don‘t want to use Git, run the following command to check out WebKit’s Subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within Xcode.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.