commit | effb05858ad9a624bf44cc77a351566a2a1952e6 | [log] [tgz] |
---|---|---|
author | darin@apple.com <darin@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sat Jun 29 21:50:00 2019 +0000 |
committer | darin@apple.com <darin@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sat Jun 29 21:50:00 2019 +0000 |
tree | e1b507b8373ea2506a4e988c2b230ce855a0f961 | |
parent | 251db284cb071a7f00d52256989a604428b30e6d [diff] |
Streamline some string code, focusing on functions that were using substringSharingImpl https://bugs.webkit.org/show_bug.cgi?id=198898 Reviewed by Daniel Bates. Source/WebCore: * css/CSSComputedStyleDeclaration.cpp: (WebCore::CSSComputedStyleDeclaration::CSSComputedStyleDeclaration): Take a StringView instead of a String argument for the pseudo-element name. This prevents us from having to use substringSharingImpl to strip off leading colons. (WebCore::CSSComputedStyleDeclaration::create): Moved this function in here since it's no longer being inlined. * css/CSSComputedStyleDeclaration.h: Moved the create function to no longer be inlined, since it's better to have the constructor be inlined in the create function instead. Changed the pseudo-element name argument to be a StringView rather than a String. Also initialize m_refCount in the class definition. * css/CSSSelector.cpp: (WebCore::CSSSelector::parsePseudoElementType): Take a StringView instead of a String. * css/CSSSelector.h: Updated for the above change. * css/SelectorPseudoTypeMap.h: Change both parse functions to take StringView. Before one took a StringImpl and the other used const StringView&, which is not as good as StringView. * css/makeSelectorPseudoClassAndCompatibilityElementMap.py: Use StringView, not const StringView&. * css/makeSelectorPseudoElementsMap.py: Use StringView rather than StringImpl. * css/parser/CSSParserImpl.cpp: (WebCore::CSSParserImpl::parsePageSelector): Use a StringView for the pseudo-element name. It was already computed as a StringView, but the old code converted it to an AtomicString. * css/parser/CSSParserSelector.cpp: (WebCore::CSSParserSelector::parsePagePseudoSelector): Take a StringView, and return a std::unique_ptr. (WebCore::CSSParserSelector::parsePseudoElementSelector): Renamed to not mention StringView in function name. Take a StringView, not a StringView&. Do the lowercasing inside this function rather than having it be a caller responsibility. Don't convert from a StringView to an AtomicString before starting to parse; only do it in the "unknown/custom" case. Return a std::unique_ptr. (WebCore::CSSParserSelector::parsePseudoClassSelector): Ditto. * css/parser/CSSParserSelector.h: Make the three parse functions all take a StringView and all return a std::unique_ptr. They were already creating objects, but before callers just had to know to adopt. * css/parser/CSSSelectorParser.cpp: (WebCore::CSSSelectorParser::consumePseudo): Updated to use improved parse functions above. * page/DOMWindow.cpp: (WebCore::DOMWindow::getMatchedCSSRules const): Updated to use the new parsePseudoElementType above and use StringView::substring instead of String::substringSharingImpl. * platform/Length.cpp: (WebCore::newCoordsArray): Local string that is "spacified" can't have any non-Latin-1 characters, so use LChar instead of UChar. * rendering/RenderText.cpp: (WebCore::convertNoBreakSpaceToSpace): Renamed for clarity. Also use constexpr instead of inline since this is a pure function. (WebCore::capitalize): Tighten up logic a bit. Source/WTF: * wtf/URLHelpers.cpp: (WTF::URLHelpers::applyHostNameFunctionToURLString): Change code using substringSharingImpl so it could call String::find to call StringView::contains instead. Also rewrote lambdas to be simpler and likely more efficient. Rewrote another case using substringSharingImpl so it could call String::find to call StringView::find instead. * wtf/text/StringView.cpp: (WTF::StringView::startsWith const): Added. * wtf/text/StringView.h: Tweaked style a bit, and added an overload of StringView::contains that takes a CodeUnitMatchFunction and an overload of startsWith that cakes a UChar. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@246951 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.