Unreviewed, rolling out r137491.
[WebKit-https.git] / Source / WebCore / ChangeLog
index f3041df..44fe3a0 100644 (file)
@@ -1,3 +1,171 @@
+2012-12-12  Sheriff Bot  <webkit.review.bot@gmail.com>
+
+        Unreviewed, rolling out r137491.
+        http://trac.webkit.org/changeset/137491
+        https://bugs.webkit.org/show_bug.cgi?id=104828
+
+        broke the builtd (Requested by rfong on #webkit).
+
+        * DerivedSources.cpp:
+        * WebCore.vcproj/WebCore.vcproj:
+        * WebCore.vcproj/WebCoreCommon.vsprops:
+        * WebCore.vcproj/copyForwardingHeaders.cmd:
+        * bindings/generic/RuntimeEnabledFeatures.cpp:
+        (WebCore):
+        * html/HTMLElementsAllInOne.cpp:
+        * platform/NotImplemented.cpp:
+        (WebCore):
+        (WebCore::notImplementedLoggingChannel):
+        * rendering/RenderingAllInOne.cpp:
+
+2012-12-12  John J. Barton  <johnjbarton@chromium.org>
+
+        Web Inspector: remove protocol-externs.js temp file after compile-front-end.py
+        https://bugs.webkit.org/show_bug.cgi?id=98799
+
+        Reviewed by Vsevolod Vlasov.
+
+        Add os.system rm for protocol-externs.js to the end of the compile script
+
+        * inspector/compile-front-end.py:
+
+2012-12-12  Robert Hogan  <robert@webkit.org>
+
+        White space between inline blocks should be affected by word-spacing property
+        https://bugs.webkit.org/show_bug.cgi?id=69072
+
+        Reviewed by Levi Weintraub.
+
+        Allow word-spacing to get added to the spaces between inline blocks in placeBoxesInInlineDirection by setting
+        needsWordSpacing to true each time an inline block is encountered. This ensures that the next space encountered
+        in a text run will be treated as a space between two words and will get word-spacing added to it if it is present
+        in the style.
+
+        Tests: fast/css/word-spacing-between-blocks.html
+               fast/css/word-spacing-between-inlines.html
+
+        * rendering/InlineFlowBox.cpp:
+        (WebCore::InlineFlowBox::placeBoxRangeInInlineDirection):
+
+2012-12-12  Xianzhu Wang  <wangxianzhu@chromium.org>
+
+        Pre-painting should not paint out-of-view fixed position elements
+        https://bugs.webkit.org/show_bug.cgi?id=104724
+
+        Reviewed by James Robinson.
+
+        Test: ManualTests/compositing/fixed-position-out-of-view-scroll-prepaint.html
+
+        * rendering/RenderLayer.cpp:
+        (WebCore::RenderLayer::paintLayer): Don't paint out-of-view fixed position elements.
+
+2012-12-11  Roger Fong  <roger_fong@apple.com>
+
+        Enable VIDEO_TRACK on Windows.
+        https://bugs.webkit.org/show_bug.cgi?id=104706.
+
+        Reviewed by Timothy Horton.
+
+        Enable VIDEO_TRACK on Windows and update project property files.
+
+        * DerivedSources.cpp:
+        * WebCore.vcproj/WebCore.vcproj:
+        * WebCore.vcproj/WebCoreCommon.vsprops:
+        * WebCore.vcproj/copyForwardingHeaders.cmd:
+        * bindings/generic/RuntimeEnabledFeatures.cpp:
+        (WebCore):
+        * html/HTMLElementsAllInOne.cpp:
+        * rendering/RenderingAllInOne.cpp:
+
+2012-12-12  James Simonsen  <simonjam@chromium.org>
+
+        [Resource Timing] Failed resources shouldn't be recorded in the buffer
+        https://bugs.webkit.org/show_bug.cgi?id=104762
+
+        Reviewed by Tony Gentilcore.
+
+        Test: http/tests/w3c/webperf/submission/resource-timing/html/test_resource_ignore_failures.html
+
+        * loader/cache/CachedResourceLoader.cpp:
+        (WebCore::CachedResourceLoader::loadDone):
+
+2012-12-12  Martin Robinson  <mrobinson@igalia.com>
+
+        [GTK] Add authentication support to DRT and fix exposed issues in the libsoup backend
+        https://bugs.webkit.org/show_bug.cgi?id=104285
+
+        Reviewed by Gustavo Noronha Silva.
+
+        Fix issues in the libsoup networking backend that were causing test
+        failures.
+
+        No new tests. This patch unskips authentication tests.
+
+        * platform/network/soup/ResourceHandleSoup.cpp:
+        (WebCore::isAuthenticationFailureStatusCode): Added this helper to catch authentication status codes
+        and use it everywhere.
+        (WebCore::applyAuthenticationToRequest): Use an early return instead of an if-statement
+        and instead of always using manually specified credentials, apply those found in the session
+        storage as well. Instead of applying the credentials to firstRequest always, accept the request
+        as a parameter, so this method can be properly used with redirects.
+        (WebCore::restartedCallback): Instead of creating the KURL directly from soup_uri_to_string
+        use soupURIToKURL, which preserves the password from the SoupURI. soup_uri_to_string doesn't
+        include the password. When calling applyAuthenticationToRequest update the new request. Before
+        applyAuthenticationToRequest always updated the firstRequest. Do not call willSendRequest for
+        instances when this method is called for authentication handling. willSendRequest should only
+        be called for server-side redirects.
+        (WebCore::createSoupRequestAndMessageForHandle): Use soup_requester_request_uri instead of
+        soup_requester_request. Request::soupURI properly creates a SoupURI with non-null empty strings
+        when either the username and password are empty.  A null username or password does not trigger
+        the URI-embedded credential override in SoupAuthenticationManager within libsoup. This is important
+        because sometimes either the username or password might empty for a request, but the other
+        part of the credential should still override the per-session credential storage.
+        (WebCore::ResourceHandle::start): We don't need to clear the username and password from the
+        internal data structure any longer. These need to be cleared in the CFNetwork backend because
+        it prevents the same failed per-request credentials from being used over and over again. In our
+        case we don't use these members during didReceiveAuthenticationChallenge, so this isn't an issue.
+        (WebCore::ResourceHandle::didReceiveAuthenticationChallenge): Don't look at the per-request
+        m_user/m_pass pair here any longer. We use these when initially creating a request, so we don't
+        want to re-use them if they fail.
+        * platform/network/soup/ResourceRequest.h:
+        (ResourceRequest): Rename urlStringForSoup to soupURI.
+        * platform/network/soup/ResourceRequestSoup.cpp:
+        (WebCore::ResourceRequest::soupURI): Instead of returning a string for the soup-bound URL
+        return a SoupURI that properly embeds empty usernames and passwords.
+
+2012-12-12  Alexey Proskuryakov  <ap@apple.com>
+
+        Make LOG() work in WebProcess and NetworkProcess
+        https://bugs.webkit.org/show_bug.cgi?id=104718
+
+        Reviewed by Tim Horton.
+
+        Split initialization function into a new InitializeLogging.h file, because it's
+        needed in WebKit, but cannot be included along with WebKit version of this file.
+        We'd have a confilct between LOG_CHANNEL_PREFIX definitions if we tried.
+
+        * WebCore.xcodeproj/project.pbxproj: Make Logging.h a project header, and
+        InitializeLogging.h a private one.
+
+        * GNUmakefile.list.am:
+        * Target.pri:
+        * platform/InitializeLogging.h: Added.
+        * platform/Logging.h:
+
+        * platform/blackberry/LoggingBlackBerry.cpp:
+        * platform/efl/LoggingEfl.cpp:
+        * platform/gtk/LoggingGtk.cpp:
+        * platform/mac/LoggingMac.mm:
+        * platform/qt/LoggingQt.cpp:
+        * platform/win/LoggingWin.cpp:
+        * platform/wx/LoggingWx.cpp:
+        Include InitializeLogging.h where this function is implemented.
+
+        * platform/NotImplemented.h:
+        * platform/NotImplemented.cpp: Added.
+        Changed to not include WebCore's Logging.h in the header, because NotImplemented.h
+        is used in WebKits, which have incompatibe logging headers.
+
 2012-12-12  Chris Fleizach  <cfleizach@apple.com>
 
         AX: aria-busy should be exposed everywhere, not just on live regions