⚠ Archived content — this site is no longer maintained.   Current WebKit documentation is at docs.webkit.org.

Timeline



Jun 30, 2018:

11:52 PM Changeset in webkit [233408] by abarth@webkit.org
  • 7 edits in trunk

Port JavaScriptCore to OS(FUCHSIA)
​https://bugs.webkit.org/show_bug.cgi?id=187223

Reviewed by Daniel Bates.

.:

  • Source/cmake/OptionsJSCOnly.cmake: Add back ICU.

Source/JavaScriptCore:

  • assembler/ARM64Assembler.h:

(JSC::ARM64Assembler::cacheFlush): Call zx_cache_flush to flush cache.

  • runtime/MachineContext.h: Fuchsia has the same mcontext_t as glibc.

(JSC::MachineContext::stackPointerImpl):
(JSC::MachineContext::framePointerImpl):
(JSC::MachineContext::instructionPointerImpl):
(JSC::MachineContext::argumentPointer<1>):
(JSC::MachineContext::llintInstructionPointer):

Source/WTF:

  • wtf/Platform.h: Fuchsia uses mcontext_t to provide machine context.
11:00 PM Changeset in webkit [233407] by dbates@webkit.org
  • 2 edits in trunk/Tools

test-webkitpy never rebuilds lldbWebKitTester
​https://bugs.webkit.org/show_bug.cgi?id=187229

Reviewed by David Kilzer.

Have test-webkitpy always call script build-lldbwebkittester to build lldbWebKitTester, if needed.

Currently test-webkitpy only calls script build-lldbwebkittester if lldbWebKitTester does not
exist in the build products directory for the active configuration (e.g. Debug); => we do not
build lldbWebKitTester again if its source changes (say, as a result of hacking on lldbWebKitTester).
Instead we should have test-webkitpy unconditionally call build-lldbwebkittester to ensure
that we have an up-to-date build of lldbWebKitTester.

  • Scripts/webkitpy/test/main.py:

(Tester._run_tests):
(_find_lldb_webkit_tester): Deleted.

7:12 PM Changeset in webkit [233406] by ddkilzer@apple.com
  • 2 edits in trunk/Source/WebCore

Follow-up: Fix clang static analyzer warnings: Garbage return value
<​https://webkit.org/b/187224>

Address review feedback from Eric Carlson.

  • platform/mediastream/MediaConstraints.h:

(WebCore::NumericConstraint::valueForCapabilityRange const):

  • Use brace initialization for more local variables.
6:49 PM Changeset in webkit [233405] by Michael Catanzaro
  • 2 edits in trunk/Source/WebCore

Asan false positive: stack use after scope under WebCore::ApplyPropertyBorderImageModifier in WebCore::Length::Length(WebCore::Length&&)
​https://bugs.webkit.org/show_bug.cgi?id=186980
<rdar://problem/41409838>

Reviewed by Oliver Hunt.

We believe that we have found a bug in GCC's address sanitizer. It is blocking work on other
issues, so work around it by changing a temporary into a local variable.

  • css/StyleBuilderCustom.h:

(WebCore::ApplyPropertyBorderImageModifier::applyInitialValue):

6:16 PM WebKitGTK/2.20.x edited by Michael Catanzaro
(diff)
6:15 PM Changeset in webkit [233404] by Michael Catanzaro
  • 3 edits in trunk/Source/ThirdParty

Fix off-by-one error in xdg_mime_get_simple_globs
​https://bugs.webkit.org/show_bug.cgi?id=186554

Reviewed by Daniel Bates.

We have an off-by-one error here in some code that was added for WebKit. (This is not an
issue with upstream xdgmime.)

No new tests. This problem is caught by TestDownloads, but only when running with ASan
enabled.

  • xdgmime/src/xdgmimecache.c:

(get_simple_globs):

  • xdgmime/src/xdgmimeglob.c:

(get_simple_globs):

5:06 PM Changeset in webkit [233403] by ddkilzer@apple.com
  • 8 edits in trunk/Source

Fix clang static analyzer warnings: Garbage return value
<​https://webkit.org/b/187224>

Reviewed by Eric Carlson.

Source/JavaScriptCore:

  • bytecode/UnlinkedCodeBlock.cpp:

(JSC::UnlinkedCodeBlock::lineNumberForBytecodeOffset):

  • Use brace initialization for local variables.
  • debugger/DebuggerCallFrame.cpp:

(class JSC::LineAndColumnFunctor):

  • Use class member initialization for member variables.

Source/WebCore:

  • platform/mediastream/MediaConstraints.h:

(WebCore::NumericConstraint::valueForCapabilityRange const):

  • Use brace initialization for local variables.

Source/WebKit:

  • WebProcess/WebCoreSupport/WebPlatformStrategies.cpp:

(WebKit::WebPlatformStrategies::changeCount):
(WebKit::WebPlatformStrategies::addTypes):
(WebKit::WebPlatformStrategies::setTypes):
(WebKit::WebPlatformStrategies::setBufferForType):
(WebKit::WebPlatformStrategies::setPathnamesForType):
(WebKit::WebPlatformStrategies::setStringForType):
(WebKit::WebPlatformStrategies::getNumberOfFiles):
(WebKit::WebPlatformStrategies::getPasteboardItemsCount):
(WebKit::WebPlatformStrategies::writeCustomData):

  • WebProcess/WebCoreSupport/mac/WebEditorClientMac.mm:

(WebKit::WebEditorClient::substitutionsPanelIsShowing):

  • Use brace initialization for local variables.
2:07 PM Changeset in webkit [233402] by Michael Catanzaro
  • 2 edits in trunk/Tools

[CMake] build-webkit should be able to enable address sanitizer
​https://bugs.webkit.org/show_bug.cgi?id=187222

Reviewed by Daniel Bates.

If 'set-webkit-configuration --asan' has been run, then build-webkit should pass
-DENABLE_ADDRESS_SANITIZER=ON to CMake, so that it actually does something.

This also works for build-jsc.

  • Scripts/webkitdirs.pm:

(generateBuildSystemFromCMakeProject):

1:53 PM Changeset in webkit [233401] by abarth@webkit.org
  • 9 edits
    2 adds in trunk/Source/WTF

Port WTF to OS(FUCHSIA)
​https://bugs.webkit.org/show_bug.cgi?id=187221

Reviewed by Yusuke Suzuki.

  • wtf/FastMalloc.cpp: Fuchsia does not have resource.h

(WTF::fastMallocStatistics): Skip collecting stats without resource.h

  • wtf/InlineASM.h: Fuchsia uses ELF
  • wtf/Platform.h: Define OS(FUCHSIA) as an OS(UNIX) variant
  • wtf/RandomDevice.cpp: Call zx_cprng_draw for crypographic randomness

(WTF::RandomDevice::cryptographicallyRandomValues):

  • wtf/ThreadingPthreads.cpp: Fuchsia does not have pthread_setschedparam

(WTF::Thread::changePriority):

  • wtf/unix/CPUTimeFuchsia.cpp: Added.
11:44 AM Changeset in webkit [233400] by Michael Catanzaro
  • 2 edits in trunk/Source/WebKit

Unreviewed, add missing PLATFORM(COCOA) guard after r233207
​https://bugs.webkit.org/show_bug.cgi?id=186788
<rdar://problem/41094167>

  • WebProcess/InjectedBundle/API/c/WKBundle.cpp:

(WKBundleExtendClassesForParameterCoder):

11:07 AM Changeset in webkit [233399] by Alan Bujtas
  • 2 edits in trunk/Source/WebCore

[LFC] Do not add the containing block's offset while computing the out-of-flow static position.
​https://bugs.webkit.org/show_bug.cgi?id=187202

Reviewed by Antti Koivisto.

The static position for an out-of-flow elements is

  1. the distance from the parent's border box.
  2. climbing up on the containing block chain and offset the containers until we reach the out-of-flow element's containing block.
  • layout/FormattingContextGeometry.cpp:

(WebCore::Layout::staticVerticalPositionForOutOfFlowPositioned):
(WebCore::Layout::staticHorizontalPositionForOutOfFlowPositioned):

11:06 AM Changeset in webkit [233398] by Alan Bujtas
  • 2 edits in trunk/Source/WebCore

[LFC] If the top and bottom margins of a box are adjoining, then it is possible for margins to collapse through it.
​https://bugs.webkit.org/show_bug.cgi?id=187220

Reviewed by Antti Koivisto.

  • layout/blockformatting/BlockMarginCollapse.cpp:

(WebCore::Layout::isMarginBottomCollapsedThrough):
(WebCore::Layout::BlockFormattingContext::MarginCollapse::collapsedMarginTopFromFirstChild):
(WebCore::Layout::BlockFormattingContext::MarginCollapse::marginTop):
(WebCore::Layout::BlockFormattingContext::MarginCollapse::marginBottom):
(WebCore::Layout::BlockFormattingContext::MarginCollapse::isMarginBottomCollapsedWithParent):
(WebCore::Layout::BlockFormattingContext::MarginCollapse::collapsedMarginBottomFromLastChild):

11:04 AM Changeset in webkit [233397] by Alan Bujtas
  • 2 edits in trunk/Source/WebCore

[LFC] Adjust final out-of-flow position with the computed margin value.
​https://bugs.webkit.org/show_bug.cgi?id=187219

Reviewed by Antti Koivisto.

  • layout/FormattingContext.cpp:

(WebCore::Layout::FormattingContext::computeOutOfFlowVerticalGeometry const):
(WebCore::Layout::FormattingContext::computeOutOfFlowHorizontalGeometry const):

10:11 AM Changeset in webkit [233396] by mitz@apple.com
  • 2 edits in trunk/Source/WebKit

Added a missing availability attribute.

  • WebProcess/InjectedBundle/API/mac/WKWebProcessPlugIn.h:
7:24 AM Changeset in webkit [233395] by commit-queue@webkit.org
  • 2 edits in trunk/Tools

Make check_flatpak() not verbose when only trying to run command inside flatpak
​https://bugs.webkit.org/show_bug.cgi?id=187187

Patch by Thibault Saunier <​tsaunier@igalia.com> on 2018-06-30
Reviewed by Michael Catanzaro.

  • flatpak/flatpakutils.py:

(run_in_sandbox_if_available):

6:43 AM Changeset in webkit [233394] by graouts@webkit.org
  • 10 edits in trunk

[Web Animations] Make WPT test at timing-model/timelines/document-timelines.html pass reliably
​https://bugs.webkit.org/show_bug.cgi?id=186507
<rdar://problem/41000257>

Reviewed by Dean Jackson.

LayoutTests/imported/w3c:

Record WPT test progressions.

  • web-platform-tests/web-animations/timing-model/timelines/document-timelines-expected.txt:

Source/WebCore:

The Web Animations spec, along with the HTML5 event loop spec, specify some assumptions on the time reported by
document.timeline.currentTime:

  • it should only increase once per frame
  • it should have the same value as the timestamp passed to requestAnimationFrame() callbacks

The WPT test at web-platform-tests/web-animations/timing-model/timelines/document-timelines.html relies on these
assumptions to be true so that we check that the start time of a new animation is not the same as the timeline time
when it was created, since it will be in the "play-pending" state for a frame.

In order to support this, we add two new methods on DocumentAnimationScheduler. First, when a scheduled display update
fires, we record the timestamp and expose it via lastTimestamp() such that DocumentTimeline and ScriptedAnimationController
can use the same value when updating animations. Then, to know whether code is run as a result of a display update, we
expose isFiring().

Now, within DocumentTimeline::currentTime(), we can cache the current time this way:

  • if we're in the middle of a display update, use the value returned by lastTimestamp().
  • otherwise, compute what would have been the ideal number of frames (at 60fps or less if throttled) and add those to

the lastTimestamp() value.

Then, we remove this cached current time when both currently-running JavaScript has completed and all animation update
code has completed by waiting on the invalidation task to run.

  • animation/DocumentAnimationScheduler.cpp:

(WebCore::DocumentAnimationScheduler::displayRefreshFired):

  • animation/DocumentAnimationScheduler.h:

(WebCore::DocumentAnimationScheduler::lastTimestamp):
(WebCore::DocumentAnimationScheduler::isFiring const):

  • animation/DocumentTimeline.cpp:

(WebCore::DocumentTimeline::currentTime):
(WebCore::DocumentTimeline::performInvalidationTask):
(WebCore::DocumentTimeline::maybeClearCachedCurrentTime):

  • animation/DocumentTimeline.h:
  • dom/ScriptedAnimationController.cpp:

(WebCore::ScriptedAnimationController::serviceScriptedAnimations):
(WebCore::ScriptedAnimationController::documentAnimationSchedulerDidFire):

LayoutTests:

This test now passes reliably.

6:04 AM Changeset in webkit [233393] by graouts@webkit.org
  • 2 edits in trunk/LayoutTests

[Web Animations] Make imported/mozilla/css-transitions/test_event-dispatch.html pass reliably
​https://bugs.webkit.org/show_bug.cgi?id=183843

Unreviewed.

This test is no longer flaky, the fix for webkit.org/b/183834 fixed the issue.

  • platform/ios/TestExpectations:
12:08 AM Changeset in webkit [233392] by commit-queue@webkit.org
  • 5 edits in trunk

Unreviewed, rolling out r233391.
​https://bugs.webkit.org/show_bug.cgi?id=187217

This patch broke Windows ports (Requested by fredw on
#webkit).

Reverted changeset:

"WTF's internal std::optional implementation should abort() on
bad optional access"
​https://bugs.webkit.org/show_bug.cgi?id=186536
​https://trac.webkit.org/changeset/233391

Jun 29, 2018:

11:42 PM Changeset in webkit [233391] by commit-queue@webkit.org
  • 5 edits in trunk

WTF's internal std::optional implementation should abort() on bad optional access
​https://bugs.webkit.org/show_bug.cgi?id=186536

Patch by Frederic Wang <​fwang@igalia.com> on 2018-06-29
Reviewed by Michael Catanzaro.

Source/WTF:

Currently, some ports built with recent compilers will cause the program to abort when one
tries to access the value of an unset std:optional (i.e. std::nullopt) as specified by C++17.
However, most ports still use WTF's internal std::optional implementation, which does not
verify illegal access. Hence it's not possible for developers working on these ports to
detect issues like bugs #186189, #186535, #186752, #186753, #187139 or #187145. WTF's version
of std::optional was introduced in bug #164199 but it was not possible to verify the
availability of the value inside constexpr member functions because the assert might involve
asm declarations. This commit introduces a new RELEASE_ASSERT_UNDER_CONSTEXPR_CONTEXT macro
(a simplified version of RELEASE_ASSERT that can be used in constexpr context) and uses it in
WTF's implementation of std::optional.

  • wtf/Assertions.h: Define RELEASE_ASSERT_UNDER_CONSTEXPR_CONTEXT as a version of

RELEASE_ASSERT that can be used in constexpr context (in particular avoids asm declarations).

  • wtf/Optional.h:

(std::optional::operator ->): Add an assert to ensure the optional value is available.
(std::optional::operator *): Ditto.
(std::optional::value const): Ditto.
(std::optional::value): Ditto.
(std::optional<T::value const): Ditto.

LayoutTests:

10:40 PM Changeset in webkit [233390] by n_wang@apple.com
  • 3 edits
    2 adds in trunk

Crash under WebCore::AXObjectCache::handleMenuItemSelected
​https://bugs.webkit.org/show_bug.cgi?id=186918
<rdar://problem/41365984>

Reviewed by Chris Fleizach.

Source/WebCore:

When a node is being destroyed, we deregister it from the AX cache through the Node's destructor.
But we did not remove the corresponding entry from the m_deferredFocusedNodeChange list. It would
then lead to a crash if we try to access the deleted node from m_deferredFocusedNodeChange.
Fixed it by removing the entry if the newly focused node is being destroyed.

Test: accessibility/accessibility-crash-focused-element-change.html

  • accessibility/AXObjectCache.cpp:

(WebCore::AXObjectCache::remove):

LayoutTests:

  • accessibility/accessibility-crash-focused-element-change-expected.txt: Added.
  • accessibility/accessibility-crash-focused-element-change.html: Added.
8:02 PM Changeset in webkit [233389] by Antti Koivisto
  • 3 edits
    2 adds in trunk

REGRESSION (r232806): Facebook login fields have blue fill background instead of white
​https://bugs.webkit.org/show_bug.cgi?id=187207
Source/WebCore:

<rdar://problem/41606349>

Reviewed by Tim Horton.

This happens because a 'prefers-dark-interface' media query on UA sheet always evaluates to true in dark mode.

Tests: fast/forms/input-background-ua-media-query.html

  • css/MediaQueryEvaluator.cpp:

(WebCore::prefersDarkInterfaceEvaluate):

Make prefers-dark-interface media query match only when using system appearance.

LayoutTests:

Reviewed by Tim Horton.

  • fast/forms/input-background-ua-media-query-expected.html: Added.
  • fast/forms/input-background-ua-media-query.html: Added.
7:12 PM Changeset in webkit [233388] by dbates@webkit.org
  • 2 edits in trunk/Tools

build-webkit: Perl "use of uninitialized value $previousContents"
​https://bugs.webkit.org/show_bug.cgi?id=185776

Reviewed by Michael Catanzaro.

Fixes an issue where reading an empty cached argument file would cause
Perl "uninitialized value" warnings of the form:

Use of uninitialized value $previousContents in chomp at C:/WebKit-BuildWorker/wincairo-wkl-debug/build/Tools/Scripts/webkitdirs.pm line 1969.
Use of uninitialized value $previousContents in string ne at C:/WebKit-BuildWorker/wincairo-wkl-debug/build/Tools/Scripts/webkitdirs.pm line 1972.

  • Scripts/webkitdirs.pm:

(isCachedArgumentfileOutOfDate):

7:11 PM Changeset in webkit [233387] by dbates@webkit.org
  • 3 edits
    5 adds in trunk

REGRESSION (r230921): Cannot log in to forums.swift.org using GitHub account
​https://bugs.webkit.org/show_bug.cgi?id=187197
<rdar://problem/40420821>

Reviewed by Brent Fulgham.

Source/WebCore:

Fixes an issue where a Same-Site cookies are not sent with any child window load if the
load is cross-origin with respect to the window's opener. One example where this issue
manifest itself was in the GitHub sign in flow on forums.swift.org.

Currently we always consider the origin of the window's opener (if we have one) when
determining whether a frame load request is same-origin and hence should send Same-Site
cookies when performing the request. So, when page A.com opens a child window to B.com and
then a person clicks a hyperlink or submits a form to B.com/b2 then we do not send Same-
Site cookies with the request to B.com/b2 (because its origin, B.com, is cross-origin
with its opener, A.com). But we should send Same-Site cookies with the request to B.com/b2
because it is same-origin with the page that initiated the request, B.com. Instead of
always considering the origin the window's opener for every frame load we should only
consider it for the first non-empty document load.

Tests: http/tests/cookies/same-site/fetch-in-about-blank-popup.html

http/tests/cookies/same-site/post-from-cross-site-popup.html

  • loader/FrameLoader.cpp:

(WebCore::FrameLoader::addExtraFieldsToRequest):

LayoutTests:

Add tests to ensure that Same-Site cookies are sent in a subsequent same-origin form submission
from a child window that is cross-origin with its opener. Also add a test to ensure that Same-Site
cookies are visible to an about:blank pop-up window (as about:blank is Same-Site with its opener
by definition of being same-origin with it).

  • http/tests/cookies/same-site/fetch-in-about-blank-popup-expected.txt: Added.
  • http/tests/cookies/same-site/fetch-in-about-blank-popup.html: Added.
  • http/tests/cookies/same-site/post-from-cross-site-popup-expected.txt: Added.
  • http/tests/cookies/same-site/post-from-cross-site-popup.html: Added.
  • http/tests/cookies/same-site/resources/post-from-popup.html: Added.
7:06 PM Changeset in webkit [233386] by dbates@webkit.org
  • 4 edits in trunk/Tools

Perl uninitialized value $isEnabled when running build-jsc using a CMake build
​https://bugs.webkit.org/show_bug.cgi?id=187208

Reviewed by Tim Horton.

Share logic for computing the feature flags to enable in CMake with both script
build-webkit and script build-jsc instead of duplicating it. This also fixes a
bug in the version of this logic in build-jsc that was inadvertently not updated
in r222394. In r222394 we removed the notion of a default value for a feature flag
listed in webkitperl::FeatureList.

We keep the current behavior of build-jsc and leave it up to the build system
to determine whether to enable or disable ENABLE_EXPERIMENTAL_FEATURES.

  • Scripts/build-jsc:

(buildMyProject):
(cMakeArgsFromFeatures): Deleted.

  • Scripts/build-webkit:

(cMakeArgsFromFeatures): Deleted; moved to webkitdirs.pm.

  • Scripts/webkitdirs.pm:

(cmakeArgsFromFeatures): Moved code from script build-webkit so that it can be shared
with build-jsc.

6:20 PM Changeset in webkit [233385] by timothy_horton@apple.com
  • 6 edits in trunk/Tools

Add -apple-color-filter and system appearance toggles to MiniBrowser
​https://bugs.webkit.org/show_bug.cgi?id=187210

Reviewed by Simon Fraser.

  • MiniBrowser/mac/AppDelegate.m:

(defaultConfiguration):

  • MiniBrowser/mac/SettingsController.h:
  • MiniBrowser/mac/SettingsController.m:

(-[SettingsController _populateMenu]):
(-[SettingsController validateMenuItem:]):
(-[SettingsController toggleAppleColorFilterEnabled:]):
(-[SettingsController appleColorFilterEnabled]):
(-[SettingsController toggleUseSystemAppearance:]):
(-[SettingsController useSystemAppearance]):

  • MiniBrowser/mac/WK1BrowserWindowController.m:

(-[WK1BrowserWindowController didChangeSettings]):

  • MiniBrowser/mac/WK2BrowserWindowController.m:

(-[WK2BrowserWindowController didChangeSettings]):

6:07 PM Changeset in webkit [233384] by wilander@apple.com
  • 2 edits in trunk/Source/WebKit

Resource Load Statistics: Make network process calls only for the process pool that the page belongs to
​https://bugs.webkit.org/show_bug.cgi?id=187206
<rdar://problem/41659160>

Reviewed by Chris Dumez.

Instead of iterating over all process pools, we should resolve which
process pool the page belongs to and call the network process only for
that pool. This is especially important since we use WTFMove for the
completion handlers.

This patch also renames "callback" to "completionHandler" for
the functions touched.

A FIXME comment is added to WebsiteDataStore::getAllStorageAccessEntries()
where we currently don't have a page ID to do the lookup with.

  • UIProcess/WebsiteData/WebsiteDataStore.cpp:

(WebKit::WebsiteDataStore::updatePrevalentDomainsToPartitionOrBlockCookies):
(WebKit::WebsiteDataStore::hasStorageAccessForFrameHandler):
(WebKit::WebsiteDataStore::getAllStorageAccessEntries):
(WebKit::WebsiteDataStore::grantStorageAccessHandler):
(WebKit::WebsiteDataStore::hasStorageAccess):
(WebKit::WebsiteDataStore::requestStorageAccess):
(WebKit::WebsiteDataStore::grantStorageAccess):

5:55 PM Changeset in webkit [233383] by sbarati@apple.com
  • 2 edits in trunk/Source/JavaScriptCore

Unreviewed. Try to fix Windows build after r233377

  • builtins/BuiltinExecutables.cpp:

(JSC::BuiltinExecutables::createExecutable):

5:43 PM Changeset in webkit [233382] by Ryan Haddad
  • 2 edits in trunk/LayoutTests

Skip media/picture-in-picture-interruption.html on iOS since it relies on 'runWithKeyDown'.
​https://bugs.webkit.org/show_bug.cgi?id=187181

Unreviewed test gardening.

  • platform/ios/TestExpectations:
5:35 PM Changeset in webkit [233381] by Chris Dumez
  • 4 edits in trunk/Source/WebKit

Add utility methods to WebResourceLoadStatisticsStore to hop back and forth between threads
​https://bugs.webkit.org/show_bug.cgi?id=187200

Reviewed by Brent Fulgham.

Add utility methods to WebResourceLoadStatisticsStore to hop back and forth between threads,
in order the simplify the code a little bit.

  • UIProcess/ResourceLoadStatisticsMemoryStore.cpp:

(WebKit::ResourceLoadStatisticsMemoryStore::ResourceLoadStatisticsMemoryStore):

  • UIProcess/WebResourceLoadStatisticsStore.cpp:

(WebKit::WebResourceLoadStatisticsStore::setNotifyPagesWhenDataRecordsWereScanned):
(WebKit::WebResourceLoadStatisticsStore::setShouldClassifyResourcesBeforeDataRecordsRemoval):
(WebKit::WebResourceLoadStatisticsStore::setShouldSubmitTelemetry):
(WebKit::WebResourceLoadStatisticsStore::WebResourceLoadStatisticsStore):
(WebKit::WebResourceLoadStatisticsStore::postTask):
(WebKit::WebResourceLoadStatisticsStore::postTaskReply):
(WebKit::WebResourceLoadStatisticsStore::flushAndDestroyPersistentStore):
(WebKit::WebResourceLoadStatisticsStore::setResourceLoadStatisticsDebugMode):
(WebKit::WebResourceLoadStatisticsStore::scheduleStatisticsAndDataRecordsProcessing):
(WebKit::WebResourceLoadStatisticsStore::resourceLoadStatisticsUpdated):
(WebKit::WebResourceLoadStatisticsStore::hasStorageAccess):
(WebKit::WebResourceLoadStatisticsStore::requestStorageAccess):
(WebKit::WebResourceLoadStatisticsStore::requestStorageAccessUnderOpener):
(WebKit::WebResourceLoadStatisticsStore::grantStorageAccess):
(WebKit::WebResourceLoadStatisticsStore::performDailyTasks):
(WebKit::WebResourceLoadStatisticsStore::submitTelemetry):
(WebKit::WebResourceLoadStatisticsStore::logFrameNavigation):
(WebKit::WebResourceLoadStatisticsStore::logUserInteraction):
(WebKit::WebResourceLoadStatisticsStore::logNonRecentUserInteraction):
(WebKit::WebResourceLoadStatisticsStore::clearUserInteraction):
(WebKit::WebResourceLoadStatisticsStore::hasHadUserInteraction):
(WebKit::WebResourceLoadStatisticsStore::setLastSeen):
(WebKit::WebResourceLoadStatisticsStore::setPrevalentResource):
(WebKit::WebResourceLoadStatisticsStore::setVeryPrevalentResource):
(WebKit::WebResourceLoadStatisticsStore::isPrevalentResource):
(WebKit::WebResourceLoadStatisticsStore::isVeryPrevalentResource):
(WebKit::WebResourceLoadStatisticsStore::isRegisteredAsSubFrameUnder):
(WebKit::WebResourceLoadStatisticsStore::isRegisteredAsRedirectingTo):
(WebKit::WebResourceLoadStatisticsStore::clearPrevalentResource):
(WebKit::WebResourceLoadStatisticsStore::setGrandfathered):
(WebKit::WebResourceLoadStatisticsStore::isGrandfathered):
(WebKit::WebResourceLoadStatisticsStore::setSubframeUnderTopFrameOrigin):
(WebKit::WebResourceLoadStatisticsStore::setSubresourceUnderTopFrameOrigin):
(WebKit::WebResourceLoadStatisticsStore::setSubresourceUniqueRedirectTo):
(WebKit::WebResourceLoadStatisticsStore::setSubresourceUniqueRedirectFrom):
(WebKit::WebResourceLoadStatisticsStore::setTopFrameUniqueRedirectTo):
(WebKit::WebResourceLoadStatisticsStore::setTopFrameUniqueRedirectFrom):
(WebKit::WebResourceLoadStatisticsStore::scheduleCookiePartitioningUpdate):
(WebKit::WebResourceLoadStatisticsStore::scheduleCookiePartitioningUpdateForDomains):
(WebKit::WebResourceLoadStatisticsStore::scheduleClearPartitioningStateForDomains):
(WebKit::WebResourceLoadStatisticsStore::scheduleCookiePartitioningStateReset):
(WebKit::WebResourceLoadStatisticsStore::scheduleClearInMemory):
(WebKit::WebResourceLoadStatisticsStore::scheduleClearInMemoryAndPersistent):
(WebKit::WebResourceLoadStatisticsStore::setTimeToLiveUserInteraction):
(WebKit::WebResourceLoadStatisticsStore::setTimeToLiveCookiePartitionFree):
(WebKit::WebResourceLoadStatisticsStore::setMinimumTimeBetweenDataRecordsRemoval):
(WebKit::WebResourceLoadStatisticsStore::setGrandfatheringTime):
(WebKit::WebResourceLoadStatisticsStore::setMaxStatisticsEntries):
(WebKit::WebResourceLoadStatisticsStore::setPruneEntriesDownTo):
(WebKit::WebResourceLoadStatisticsStore::resetParametersToDefaultValues):

  • UIProcess/WebResourceLoadStatisticsStore.h:
5:23 PM Changeset in webkit [233380] by Darin Adler
  • 4 edits
    4 moves
    1 add in trunk/Source/WTF

[Cocoa] reduce unnecessary use of .mm source files in WTF, spruce up some implementation details
​https://bugs.webkit.org/show_bug.cgi?id=186924

Reviewed by Anders Carlsson.

  • WTF.xcodeproj/project.pbxproj: Update for file and directory renames, file type changes,

and deletions.

  • wtf/MemoryPressureHandler.cpp:

(WTF::MemoryPressureHandler::holdOff): Deleted empty placeholder; this one is not needed.

  • wtf/PlatformMac.cmake: Update for file and directory renames, file type changes,

and deletions.

  • wtf/cocoa/CPUTimeCocoa.cpp: Renamed from Source/WTF/wtf/cocoa/CPUTimeCocoa.mm.
  • wtf/text/cocoa/StringImplCocoa.mm: Renamed from Source/WTF/wtf/text/mac/StringImplMac.mm.

Also removed an unneeded include.

  • wtf/text/cocoa/StringViewCocoa.mm: Renamed from Source/WTF/wtf/text/mac/StringViewObjC.mm.
  • wtf/text/cocoa/TextBreakIteratorInternalICUCocoa.cpp: Renamed from

Source/WTF/wtf/text/mac/TextBreakIteratorInternalICUMac.mm.

5:06 PM Changeset in webkit [233379] by commit-queue@webkit.org
  • 9 edits
    2 adds in trunk

[macOS] Do not crash if there is an attempt to copy a file URL to the clipboard
​https://bugs.webkit.org/show_bug.cgi?id=187183

Patch by Aditya Keerthi <Aditya Keerthi> on 2018-06-29
Reviewed by Wenson Hsieh.

Source/WebKit:

r210683 introduced logic to prevent file URLs from being copied to the clipboard
in unexpected cases. The current logic always crashes the WebProcess if
webProcessProxy->checkURLReceivedFromWebProcess returns false. Instead of
crashing, we can fail silently and not copy anything to the clipboard.

  • UIProcess/Cocoa/WebPasteboardProxyCocoa.mm:

(WebKit::WebPasteboardProxy::setPasteboardPathnamesForType): Removed call to markCurrentlyDispatchedMessageAsInvalid() which was causing the process to crash.

Tools:

Added a 'runSingly' option to the TestOptions struct. Setting this option to true
will force a new PlatformWebView to be created before running a test. This ensures
that any state set by previous tests are not preserved.

One example of the importance of having this ability is in the case where we want
to test functionality that deals with read access to files. If a test were to
load a valid file URL, universal read access will be granted in WebProcessProxy.
This prevents us from testing cases that rely on us not have universal read
access. Now, if we write the test using the 'runSingly' option, any state set
by previous tests is cleared. Consequently, our test will behave as expected.

  • WebKitTestRunner/PlatformWebView.h:

(WTR::PlatformWebView::viewSupportsOptions const):

  • WebKitTestRunner/TestController.cpp:

(WTR::updateTestOptionsFromTestHeader):

  • WebKitTestRunner/TestOptions.h:

(WTR::TestOptions::hasSameInitializationOptions const):

LayoutTests:

Added a test to ensure that the WebProcess does not crash if we attempt to copy a
file URL to the clipboard. The test also ensures the clipboard content remains
unchanged.

  • TestExpectations:
  • http/tests/security/pasteboard-file-url-expected.txt: Added.
  • http/tests/security/pasteboard-file-url.html: Added.
  • platform/mac-wk2/TestExpectations:
5:05 PM Changeset in webkit [233378] by sbarati@apple.com
  • 5 edits in trunk/Source/JavaScriptCore

Don't use tracePoints in JS/Wasm entry
​https://bugs.webkit.org/show_bug.cgi?id=187196

Reviewed by Mark Lam.

This puts VM entry and Wasm entry tracePoints behind a runtime
option. This is a ~4x speedup on a soon to be released Wasm
benchmark. tracePoints should basically never run more than 50
times a second. Entering the VM and entering Wasm are user controlled,
and can happen hundreds of thousands of times in a second. Depending
on how the Wasm/JS code is structured, this can be disastrous for
performance.

  • runtime/Options.h:
  • runtime/VMEntryScope.cpp:

(JSC::VMEntryScope::VMEntryScope):
(JSC::VMEntryScope::~VMEntryScope):

  • wasm/WasmBBQPlan.cpp:

(JSC::Wasm::BBQPlan::compileFunctions):

  • wasm/js/WebAssemblyFunction.cpp:

(JSC::callWebAssemblyFunction):

4:40 PM Changeset in webkit [233377] by sbarati@apple.com
  • 19 edits
    2 adds in trunk

We shouldn't recurse into the parser when gathering metadata about various function offsets
​https://bugs.webkit.org/show_bug.cgi?id=184074
<rdar://problem/37165897>

Reviewed by Mark Lam.

JSTests:

  • microbenchmarks/try-get-by-id-basic.js:

(const.bench.f.const.fooPlusBar.createBuiltin):

  • microbenchmarks/try-get-by-id-polymorphic.js:

(fooPlusBar.createBuiltin):

  • stress/array-push-with-force-exit.js:
  • stress/dont-crash-on-stack-overflow-when-parsing-builtin.js: Added.

(f):

  • stress/dont-crash-on-stack-overflow-when-parsing-default-constructor.js: Added.

(foo):
(prototype.runNearStackLimit):

  • stress/is-constructor.js:
  • stress/tailCallForwardArguments.js:

(putFuncToPrivateName.createBuiltin):

Source/JavaScriptCore:

Prior to this patch, when we made a builtin, we had to make an UnlinkedFunctionExecutable
for that builtin. This required calling into the parser. However, the parser
may throw a stack overflow. We were not able to recover from that. The only
reason we called into the parser here is that we were gathering text offsets
and various metadata for things in the builtin function. This patch writes a
mini parser that figures this information out without calling into the full
parser. (I've also added a debug assert that verifies the mini parser stays in
sync with the full parser.) The result of this is that BuiltinExecutbles::createExecutable
always succeeds.

  • builtins/AsyncFromSyncIteratorPrototype.js:

(globalPrivate.createAsyncFromSyncIterator):
(globalPrivate.AsyncFromSyncIteratorConstructor):

  • builtins/BuiltinExecutables.cpp:

(JSC::BuiltinExecutables::createExecutable):

  • builtins/GlobalOperations.js:

(globalPrivate.getter.overriddenName.string_appeared_here.speciesGetter):
(globalPrivate.speciesConstructor):
(globalPrivate.copyDataProperties):
(globalPrivate.copyDataPropertiesNoExclusions):

  • builtins/PromiseOperations.js:

(globalPrivate.newHandledRejectedPromise):

  • builtins/RegExpPrototype.js:

(globalPrivate.hasObservableSideEffectsForRegExpMatch):
(globalPrivate.hasObservableSideEffectsForRegExpSplit):

  • builtins/StringPrototype.js:

(globalPrivate.hasObservableSideEffectsForStringReplace):
(globalPrivate.getDefaultCollator):

  • parser/Nodes.cpp:

(JSC::FunctionMetadataNode::FunctionMetadataNode):
(JSC::FunctionMetadataNode::operator== const):
(JSC::FunctionMetadataNode::dump const):

  • parser/Nodes.h:
  • parser/Parser.h:

(JSC::parse):

  • parser/ParserError.h:

(JSC::ParserError::type const):

  • parser/ParserTokens.h:

(JSC::JSTextPosition::operator== const):
(JSC::JSTextPosition::operator!= const):

  • parser/SourceCode.h:

(JSC::SourceCode::operator== const):
(JSC::SourceCode::operator!= const):
(JSC::SourceCode::subExpression const):
(JSC::SourceCode::subExpression): Deleted.

4:33 PM Changeset in webkit [233376] by n_wang@apple.com
  • 4 edits
    2 adds in trunk

AX: [iOS] VoiceOver scroll position is jumpy in frames
​https://bugs.webkit.org/show_bug.cgi?id=186956

Reviewed by Simon Fraser.

Source/WebCore:

iOS is using delegate scrolling and we should not take into account
the scroll offset when converting rects.

Also fixed a issue where we want to scroll the element into view even
if it's partially visible.

Test: fast/scrolling/ios/iframe-scroll-into-view.html

  • accessibility/AccessibilityObject.cpp:

(WebCore::AccessibilityObject::scrollToMakeVisible const):

  • platform/ScrollView.cpp:

(WebCore::ScrollView::contentsToContainingViewContents const):

LayoutTests:

  • fast/scrolling/ios/iframe-scroll-into-view-expected.html: Added.
  • fast/scrolling/ios/iframe-scroll-into-view.html: Added.
4:17 PM Changeset in webkit [233375] by dbates@webkit.org
  • 2 edits in trunk/Tools

[lldb-webkit] Non-empty strings may be pretty-printed as empty
​https://bugs.webkit.org/show_bug.cgi?id=187185

Reviewed by Simon Fraser.

For some reason lldb(1) sometimes has an issue accessing members of WTF::StringImplShape
via a WTF::StringImpl pointer (why?). Explicitly casting a WTF::StringImpl* to a
WTF::StringImplShape* before accessing such members makes LLDB happy.

I tried writing a test for this both for the LLVM project and to add to our lldb_webkit unit
tests to no avail. I have only been able to reproduce this bug sporadically during my WebCore/WebKit
debugging sessions so far.

  • lldb/lldb_webkit.py:

(WTFStringImplProvider.init): Explicitly cast the WTF::StringImpl* to WTF::StringImplShape*.
(WTFStringImplProvider.get_data8): Update code now that we are directly accessing WTF::StringImplShape*.
(WTFStringImplProvider.get_data16): Ditto.

3:56 PM Changeset in webkit [233374] by Chris Dumez
  • 5 edits
    1 add in trunk

WebKitLegacy: Can trigger recursive loads triggering debug assertions
​https://bugs.webkit.org/show_bug.cgi?id=187121
<rdar://problem/41259430>

Reviewed by Brent Fulgham.

Source/WebCore:

In order to support asynchronous policy delegates, r229722 added a call to
FrameLoader::clearProvisionalLoadForPolicyCheck() when starting a navigation
policy decision in PolicyChecker::checkNavigationPolicy(). This calls
stopLoading() on the current provisional loader if there is one, and potentially
calls the didFailProvisionalLoadWithError cleint delegate. This delegate call
is synchronous on WebKit1, so the client may start a new load from this delegate
and re-enter Webcore. This happens in practive with Quickens 2017 / 2018 on Mac.

Before r229722, this was not an issue because pending loads were canceled after
the (asynchronous) navigation policy decision, via FrameLoader::stopAllLoaders().
FrameLoader::stopAllLoaders() sets a m_inStopAllLoaders flag and we return early
in FrameLoader::loadRequest() when this flag is set to prevent recursive loads.

To maintain shipping behavior as much as possible, this patch introduces a similar
inClearProvisionalLoadForPolicyCheck which gets set during
FrameLoader::clearProvisionalLoadForPolicyCheck() and we prevent new loads while
this flag is set.

I have verified that Quickens 2017 / 2018 works again after this change and I added
API test coverage for this behavior.

  • loader/FrameLoader.cpp:

(WebCore::FrameLoader::loadURL):
(WebCore::FrameLoader::load):
(WebCore::FrameLoader::clearProvisionalLoadForPolicyCheck):

  • loader/FrameLoader.h:

Tools:

Add API test coverage.

  • TestWebKitAPI/TestWebKitAPI.xcodeproj/project.pbxproj:
  • TestWebKitAPI/Tests/mac/StartLoadInDidFailProvisionalLoad.mm: Added.

(-[StartLoadInDidFailProvisionalLoadDelegate webView:didFailProvisionalLoadWithError:forFrame:]):
(-[StartLoadInDidFailProvisionalLoadDelegate webView:didFinishLoadForFrame:]):
(TestWebKitAPI::TEST):

3:51 PM Changeset in webkit [233373] by Lucas Forschler
  • 2 edits in trunk/Tools

Teach bisect-builds to retrieve supported platforms from the rest api.

2:17 PM Changeset in webkit [233372] by keith_miller@apple.com
  • 2 edits in trunk/Tools

run-jsc should print when jsc exits with non-zero status
​https://bugs.webkit.org/show_bug.cgi?id=187192

Reviewed by Saam Barati.

  • Scripts/run-jsc:
2:00 PM Changeset in webkit [233371] by Chris Dumez
  • 2 edits in trunk/Source/WebKit

Regression(r233359): Caused ITP tests to be flaky
​https://bugs.webkit.org/show_bug.cgi?id=187189

Reviewed by Youenn Fablet.

r233359 started using m_resolvedConfiguration.resourceLoadStatisticsDirectory instead of
m_configuration.resourceLoadStatisticsDirectory for the ITP path. This is consistent
with what we do for other database paths so that things like '~' in paths get resolved.

This introduced flakiness because the resourceLoadStatisticsDirectory was never getting
resolved and m_resolvedConfiguration.resourceLoadStatisticsDirectory was not set.
Update the WebsiteDataStore so that m_resolvedConfiguration.resourceLoadStatisticsDirectory
properly gets set to the resolved version of m_configuration.resourceLoadStatisticsDirectory.

  • UIProcess/WebsiteData/WebsiteDataStore.cpp:

(WebKit::WebsiteDataStore::resolveDirectoriesIfNecessary):
(WebKit::WebsiteDataStore::enableResourceLoadStatisticsAndSetTestingCallback):

1:59 PM Changeset in webkit [233370] by Ryan Haddad
  • 2 edits in trunk/LayoutTests

Layout Test webrtc/datachannel/mdns-ice-candidates.html is flaky
​https://bugs.webkit.org/show_bug.cgi?id=187180

Unreviewed test gardening.

Patch by Truitt Savell <Truitt Savell> on 2018-06-29

1:47 PM Changeset in webkit [233369] by Ryan Haddad
  • 3 edits in trunk/LayoutTests

Layout Test js/error-should-not-strong-reference-global-object.html is flaky on macOS
​https://bugs.webkit.org/show_bug.cgi?id=187103

Unreviewed test gardening

Patch by Truitt Savell <Truitt Savell> on 2018-06-29

  • platform/mac-wk2/TestExpectations:
  • platform/mac/TestExpectations:
1:25 PM Changeset in webkit [233368] by aakash_jain@apple.com
  • 3 edits in trunk/Tools

[ews-build] Add timeout to webkitpy and webkitperl tests
​https://bugs.webkit.org/show_bug.cgi?id=187191

Reviewed by Lucas Forschler.

  • BuildSlaveSupport/ews-build/steps.py:

(RunWebKitPerlTests.init): Set timeout of 2 minutes.
(RunWebKitPyTests.init): Ditto.

  • BuildSlaveSupport/ews-build/steps_unittest.py: Updated unit-tests.
1:11 PM Changeset in webkit [233367] by wilander@apple.com
  • 6 edits in trunk/Source/WebKit

Resource Load Statistics: Don't create a WebResourceLoadStatisticsStore for ephemeral sessions
​https://bugs.webkit.org/show_bug.cgi?id=187154
<rdar://problem/41487250>

Reviewed by Brent Fulgham and Chris Dumez.

Most of the changes in this patch remove the boolean parameter for tracking
ephemeral sessions and the IsReadOnly enum.

  • UIProcess/API/Cocoa/WKWebsiteDataStore.mm:

(-[WKWebsiteDataStore _setResourceLoadStatisticsTestingCallback:]):

Now returns early for ephemeral sessions.

  • UIProcess/ResourceLoadStatisticsPersistentStorage.cpp:

(WebKit::ResourceLoadStatisticsPersistentStorage::ResourceLoadStatisticsPersistentStorage):
(WebKit::ResourceLoadStatisticsPersistentStorage::writeMemoryStoreToDisk):
(WebKit::ResourceLoadStatisticsPersistentStorage::scheduleOrWriteMemoryStore):

  • UIProcess/ResourceLoadStatisticsPersistentStorage.h:
  • UIProcess/WebResourceLoadStatisticsStore.cpp:

(WebKit::WebResourceLoadStatisticsStore::WebResourceLoadStatisticsStore):

  • UIProcess/WebResourceLoadStatisticsStore.h:
  • UIProcess/WebsiteData/WebsiteDataStore.cpp:

(WebKit::WebsiteDataStore::setResourceLoadStatisticsEnabled):

Now returns early for ephemeral sessions.

(WebKit::WebsiteDataStore::enableResourceLoadStatisticsAndSetTestingCallback):

12:24 PM Changeset in webkit [233366] by Said Abou-Hallawa
  • 4 edits
    2 adds in trunk

Infinite loop if a <use> element references its ancestor and the DOMNodeInserted event handler of one its ancestor's descents updates the document style
​https://bugs.webkit.org/show_bug.cgi?id=186925

Reviewed by Antti Koivisto.

Source/WebCore:

This patches fixes two issues:
-- SVGTRefTargetEventListener should not assume it has to be attached to
target when its handleEvent() is called.
Because SVGTRefTargetEventListener::handleEvent() references the target
element, we just return if the listener is detached.

-- The <use> element should not clone its shadow tree if it references one
of its ancestors. The DOMNodeInserted of any node in the target element
tree may issue a document command. This document command will cause the
shadow tree to be re-cloned so this will cause infinite loop to happen.

Test: svg/dom/svg-use-infinite-loop-cloning.html

  • svg/SVGTRefElement.cpp:

(WebCore::SVGTRefTargetEventListener::handleEvent):

  • svg/SVGUseElement.cpp:

(WebCore::SVGUseElement::updateShadowTree):

LayoutTests:

  • svg/dom/svg-use-infinite-loop-cloning-expected.txt: Added.
  • svg/dom/svg-use-infinite-loop-cloning.html: Added.
11:54 AM Changeset in webkit [233365] by Manuel Rego Casasnovas
  • 4 edits in trunk

[WPE] Three CSS Grid Layout tests crash due to valueless std::optional access
​https://bugs.webkit.org/show_bug.cgi?id=186752

Reviewed by Frédéric Wang.

Source/WebCore:

This is a simple fix for the crash we're getting on WPE
in IndefiniteSizeStrategy::freeSpaceForStretchAutoTracksStep().

Covered by existent tests, just remove them from TestExpectations file.

  • rendering/GridTrackSizingAlgorithm.cpp:

(WebCore::IndefiniteSizeStrategy::freeSpaceForStretchAutoTracksStep const):
Check if minSize is null before trying to access it's value.

LayoutTests:

as they're passing now.

11:12 AM Changeset in webkit [233364] by clopez@igalia.com
  • 2 edits in trunk/Tools

[WPE]: Fix exception handling when flatpak is not installed
​https://bugs.webkit.org/show_bug.cgi?id=186771

Unreviewed followup-fix after r233362

This was causing failures when flatpak is not installed.

  • flatpak/flatpakutils.py:

(check_flatpak):

10:55 AM Changeset in webkit [233363] by Ross Kirsling
  • 5 edits in trunk

[JSCOnly] Restore Windows build.
​https://bugs.webkit.org/show_bug.cgi?id=187127

Reviewed by Michael Catanzaro.

.:

  • Source/cmake/OptionsJSCOnly.cmake:

Don't forget to set -DUCHAR_TYPE=wchar_t for ICU on Windows.
Use bin64/lib64 on Windows (for consistency with full WebKit build).

Tools:

  • Scripts/build-jsc:

Fix condition for disabling FTL JIT on Windows.

  • Scripts/webkitdirs.pm:

(executableProductDir):
JSCOnly should still use bin64 on Windows (for consistency with full WebKit build).
(determineIsWin64):
JSCOnly already defaults to 64-bit on Windows with Ninja -- ensure that this is true even with MSBuild.

10:47 AM Changeset in webkit [233362] by commit-queue@webkit.org
  • 15 edits
    16 adds in trunk

[GTK][WPE]: Add a way to setup our development environment inside flatpak
​https://bugs.webkit.org/show_bug.cgi?id=186771

Patch by Thibault Saunier <​tsaunier@igalia.com> on 2018-06-29
Reviewed by Carlos Alberto Lopez Perez.

Tools:

This patch introduce a way to setup the development environment inside flatpak[0]
removing the need for jhbuild when doing so. Anything needed to build/run minibrowser/ run
layout tests is provided either but the org.gnome.Sdk runtime or built with flatpak-builder.

The workflow is very similar to the "jhbuild based" one except that you should use update-webkit$PORTNAME-flatpak instead
of update-webkit$PORTNAME-libs and that script requires to specify a build configuration (--release is default).

Our scripts have been updated to be able to run inside that new build environment.

Since everything runs inside a flatpak sandbox, gdb needs to be run from within the sandbox, the script exposes a way to do it
easily with the --gdb option:

$ webkit-flatpak --gdb [-m COREDUMPCTL MATCHES]

The Layout test GDBCrashLogGenerator has been taugth how to use that and is able to retrieve stacktrace as with the jhbuild based workflow.

[0] ​http://flatpak.org

  • Scripts/build-webkit:
  • Scripts/generate-jsc-bundle:

(main):

  • Scripts/run-gtk-tests:
  • Scripts/run-minibrowser:
  • Scripts/run-webdriver-tests:
  • Scripts/run-webkit-tests:
  • Scripts/run-wpe-tests:
  • Scripts/update-webkitgtk-libs:
  • Scripts/update-webkitwpe-libs:
  • Scripts/webkit-flatpak: Added.
  • Scripts/webkitdirs.pm:

(getJhbuildPath):
(getFlatpakPath):
(inFlatpakSandbox):
(runInFlatpak):
(runInFlatpakIfAvalaible):
(wrapperPrefixIfNeeded):
(shouldUseFlatpak):

  • Scripts/webkitpy/port/base.py:

(Port._path_to_apache):
(Port._is_flatpak):
(Port._apache_config_file_name_for_platform):
(Port._should_use_flatpak):
(Port):
(Port._in_flatpak_sandbox):
(Port._should_use_jhbuild):

  • Scripts/webkitpy/port/gtk.py:

(GtkPort.setup_environ_for_server):

  • Scripts/webkitpy/port/linux_get_crash_log.py:

(GDBCrashLogGenerator._get_trace_from_systemd):
(GDBCrashLogGenerator.generate_crash_log):

  • Scripts/webkitpy/port/wpe.py:

(WPEPort.setup_environ_for_server):

  • Scripts/webkitpy/w3c/wpt_runner.py:

(main):

  • flatpak/files/default.xkm: Added.
  • flatpak/files/httpd-autogen.sh: Added.
  • flatpak/flatpakutils.py: Added.

(Colors):
(Console):
(Console.message):
(remove_extension_points):
(remove_comments):
(remove_comments._replacer):
(load_manifest):
(expand_manifest):
(FlatpakObject):
(FlatpakObject.init):
(FlatpakObject.flatpak):
(FlatpakPackages):
(FlatpakPackages.init):
(FlatpakPackages.detect_packages):
(FlatpakPackages.detect_packages.in):
(FlatpakPackages.detect_runtimes):
(FlatpakPackages.detect_apps):
(FlatpakPackages.iter):
(FlatpakRepos):
(FlatpakRepos.init):
(FlatpakRepos.update):
(FlatpakRepos.add):
(FlatpakRepo):
(FlatpakRepo.init):
(FlatpakRepo.repo_file):
(FlatpakPackage):
(FlatpakPackage.init):
(FlatpakPackage.str):
(FlatpakPackage.is_installed):
(FlatpakPackage.install):
(FlatpakPackage.update):
(WebkitFlatpak):
(WebkitFlatpak.load_from_args):
(WebkitFlatpak.init):
(WebkitFlatpak.check_flatpak):
(WebkitFlatpak.check_flatpak.comparable_version):
(WebkitFlatpak.clean_args):
(WebkitFlatpak.run_in_sandbox):
(WebkitFlatpak.run):
(WebkitFlatpak.has_environment):
(WebkitFlatpak.setup_dev_env):
(WebkitFlatpak.install_all):
(WebkitFlatpak.run_gdb):
(WebkitFlatpak.update_all):
(is_sandboxed):
(run_in_sandbox_if_available):

  • flatpak/org.webkit.GTK.yaml: Added.
  • flatpak/org.webkit.WPE.yaml: Added.
  • flatpak/org.webkit.WebKit.yaml: Added.
  • flatpak/patches/httpd-0001-configure-use-pkg-config-for-PCRE-detection.patch: Added.
  • flatpak/patches/xvfb-0001-HACK-Avoid-compiling-a-kbm-file.patch: Added.

LayoutTests:

  • http/conf/flatpak-httpd.conf: Added. Apache configuration file to be used inside flaptak.
10:42 AM Changeset in webkit [233361] by david_fenton@apple.com
  • 8 edits
    3 deletes in trunk

Unreviewed, rolling out r233349.

caused 42 crashes on iOS GuardMalloc and iOS ASan tests

Reverted changeset:

"[Web Animations] Using a Web Animation leaks the Document"
​https://bugs.webkit.org/show_bug.cgi?id=187088
​https://trac.webkit.org/changeset/233349

10:15 AM Changeset in webkit [233360] by jer.noble@apple.com
  • 6 edits
    2 adds in trunk

Returning PiP'd video to fullscreen while playing leaves video muted.
​https://bugs.webkit.org/show_bug.cgi?id=187181
<rdar://problem/41408335>

Reviewed by Eric Carlson.

Source/WebCore:

Test: media/picture-in-picture-interruption.html

Don't reset the media session's state at the end of an interruption if it wasn't changed an the beginning of one.

  • platform/audio/PlatformMediaSession.cpp:

(WebCore::PlatformMediaSession::endInterruption):

  • testing/Internals.cpp:

(WebCore::Internals::mediaSessionState):

  • testing/Internals.h:
  • testing/Internals.idl:

LayoutTests:

  • media/picture-in-picture-interruption-expected.txt: Added.
  • media/picture-in-picture-interruption.html: Added.
9:54 AM Changeset in webkit [233359] by Chris Dumez
  • 5 edits in trunk/Source/WebKit

Stop using lambdas for WebResourceLoadStatisticsStore to interact with its WebsiteDataStore
​https://bugs.webkit.org/show_bug.cgi?id=187165

Reviewed by Brent Fulgham.

Stop using lambdas for WebResourceLoadStatisticsStore to interact with its WebsiteDataStore. Instead,
WebResourceLoadStatisticsStore now holds a weak pointer to its WebsiteDataStore and is able to call
methods on it directly. Reducing the indirection makes the code less complex and more understandable.

  • UIProcess/WebResourceLoadStatisticsStore.cpp:

(WebKit::WebResourceLoadStatisticsStore::WebResourceLoadStatisticsStore):
(WebKit::WebResourceLoadStatisticsStore::callHasStorageAccessForFrameHandler):
(WebKit::WebResourceLoadStatisticsStore::callGrantStorageAccessHandler):
(WebKit::WebResourceLoadStatisticsStore::removeAllStorageAccess):
(WebKit::WebResourceLoadStatisticsStore::callUpdatePrevalentDomainsToPartitionOrBlockCookiesHandler):
(WebKit::WebResourceLoadStatisticsStore::callRemoveDomainsHandler):

  • UIProcess/WebResourceLoadStatisticsStore.h:
  • UIProcess/WebsiteData/WebsiteDataStore.cpp:

(WebKit::WebsiteDataStore::enableResourceLoadStatisticsAndSetTestingCallback):

8:24 AM Changeset in webkit [233358] by Ryan Haddad
  • 2 edits in trunk/Source/bmalloc

Unreviewed, rolling out r233347.

Causes crashes during WK1 tests.

Reverted changeset:

"Disable IsoHeaps when Gigacage is off"
​https://bugs.webkit.org/show_bug.cgi?id=187160
​https://trac.webkit.org/changeset/233347

8:20 AM Changeset in webkit [233357] by Alan Bujtas
  • 2 edits in trunk/Source/WebCore

[LFC] When the formatting root is also a containing block for out-of-flow elements.
​https://bugs.webkit.org/show_bug.cgi?id=187179

Reviewed by Antti Koivisto.

Out-of-flow descendants' layout requires their containing block height to be computed. This patch takes care of the case
when the containing block is also a formatting context root (e.g. relative positioned with overflow other than visible).

  • layout/Verification.cpp:

(WebCore::Layout::LayoutContext::verifyAndOutputMismatchingLayoutTree const):

  • layout/blockformatting/BlockFormattingContext.cpp:

(WebCore::Layout::BlockFormattingContext::layoutFormattingContextRoot const):

7:47 AM Changeset in webkit [233356] by Alan Bujtas
  • 2 edits in trunk/Source/WebCore

[LFC] Do not skip the next inflow sibling after finishing a formatting context root layout.
​https://bugs.webkit.org/show_bug.cgi?id=187178

Reviewed by Antti Koivisto.

Since the block formatting layout is based on pre-order traversal, after finishing a formatting
context layout (which takes care of its entire subtre), we need to visit the next (in-flow)sibling.

  • layout/blockformatting/BlockFormattingContext.cpp:

(WebCore::Layout::BlockFormattingContext::layout const):

7:17 AM Changeset in webkit [233355] by pvollan@apple.com
  • 2 edits in trunk/LayoutTests

Layout Test imported/mozilla/css-animations/test_animation-starttime.html is failing.
​https://bugs.webkit.org/show_bug.cgi?id=186807

Unreviewed test gardening.

  • platform/win/TestExpectations:
7:10 AM Changeset in webkit [233354] by pvollan@apple.com
  • 2 edits in trunk/LayoutTests

Layout Test fast/text/mark-matches-broken-line-rendering.html is failing
​https://bugs.webkit.org/show_bug.cgi?id=187177

Unreviewed test gardening.

  • platform/win/TestExpectations:
7:00 AM WebKitGTK/2.20.x edited by Adrian Perez de Castro
(diff)
6:52 AM Changeset in webkit [233353] by magomez@igalia.com
  • 2 edits in trunk/Source/WebKit

[WPE] Some frames are dropped when using rAF to animate an element
​https://bugs.webkit.org/show_bug.cgi?id=187175

Always call renderNextFrame in ThreadedCompositor::requestDisplayRefreshMonitorUpdate()
so we have to process any pending layer flush request.

Reviewed by Žan Doberšek.

  • Shared/CoordinatedGraphics/threadedcompositor/ThreadedCompositor.cpp:

(WebKit::ThreadedCompositor::handleDisplayRefreshMonitorUpdate):

5:35 AM Changeset in webkit [233352] by graouts@webkit.org
  • 2 edits in trunk/LayoutTests

Layout Test compositing/animation/layer-for-filling-animation.html is a flaky failure
​https://bugs.webkit.org/show_bug.cgi?id=187163

Unreviewed.

This test needed to be modified to account for the pending state being updated at a different time,
so we just wait a frame to ensure the animation is ended. See r233325.

  • compositing/animation/layer-for-filling-animation.html:
5:34 AM Changeset in webkit [233351] by graouts@webkit.org
  • 4 edits in trunk/LayoutTests

[mac][wk2] REGRESSION (Tiled Drawing): Some css3/ tests fail with fringing around tiled background-images that intersect tile boundaries
​https://bugs.webkit.org/show_bug.cgi?id=122235

Unreviewed. This test has not been flaky on all ports by GTK for a long time.

  • platform/ios-wk1/TestExpectations:
  • platform/mac-wk2/TestExpectations:
  • platform/wincairo/TestExpectations:
12:55 AM Changeset in webkit [233350] by Alan Bujtas
  • 8 edits in trunk/Source/WebCore

[LFC] The static position for an out-of-flow box should include the previous sibling's collapsed margin
​https://bugs.webkit.org/show_bug.cgi?id=187169

Reviewed by Antti Koivisto.

When computing the static position of an absolutely positioned box, we need to look at the previous sibling's bottom margin.
If the previous sibling happens to collapse its bottom margin with the parent's bottom margin, we still need to account for it
and compute the static vertical position as if the bottom margin was not collapsed.

  • layout/FormattingContext.cpp:

(WebCore::Layout::FormattingContext::computeFloatingHeightAndMargin const):
(WebCore::Layout::FormattingContext::computeOutOfFlowVerticalGeometry const):

  • layout/FormattingContextGeometry.cpp:

(WebCore::Layout::staticVerticalPositionForOutOfFlowPositioned):

  • layout/LayoutContext.cpp:

(WebCore::Layout::LayoutContext::initializeRoot):

  • layout/Verification.cpp:

(WebCore::Layout::outputMismatchingBoxInformationIfNeeded):

  • layout/blockformatting/BlockFormattingContext.cpp:

(WebCore::Layout::BlockFormattingContext::computeInFlowHeightAndMargin const):

  • layout/displaytree/DisplayBox.cpp:

(WebCore::Display::Box::nonCollapsedMarginBox const):

  • layout/displaytree/DisplayBox.h:

(WebCore::Display::Box::setHasValidVerticalNonCollapsedMargin):
(WebCore::Display::Box::setVerticalMargin):
(WebCore::Display::Box::setVerticalNonCollapsedMargin):
(WebCore::Display::Box::nonCollapsedMarginTop const):
(WebCore::Display::Box::nonCollapsedMarginBottom const):

Note: See TracTimeline for information about the timeline view.