Unreviewed, rolling out r137491.
[WebKit-https.git] / Source / WebCore / ChangeLog
index 077e2f9..44fe3a0 100644 (file)
+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
+        https://bugs.webkit.org/show_bug.cgi?id=104814
+
+        Reviewed by Anders Carlsson.
+
+        The aria-busy attribute should be exposed on all elements. 
+        This isn't entirely clear in the ARIA spec, but that will be fixed with
+        ARIA1.1 (ISSUE-538).
+
+        Existing tests that dump attributes cover this new behavior.
+
+        * accessibility/mac/WebAccessibilityObjectWrapper.mm:
+        (-[WebAccessibilityObjectWrapper additionalAccessibilityAttributeNames]):
+
+2012-12-12  Gavin Peters  <gavinp@chromium.org>
+
+        [chromium] Add destructor to WebPrerender
+        https://bugs.webkit.org/show_bug.cgi?id=104820
+
+        Reviewed by James Robinson.
+
+        When making WebPrerender default constructible and assignable, the destructor should have been moved out of WEBKIT_IMPLEMENTATION.
+
+        Existing WebKit unit tests should test this, as do chromium browser tests.
+
+        * platform/chromium/support/WebPrerender.cpp:
+        (WebKit::WebPrerender::toPrerender):
+        (WebKit::WebPrerender::reset):
+
+2012-12-12  Allan Sandfeld Jensen  <allan.jensen@digia.com>
+
+        [Qt] Animation fails on large layers
+        https://bugs.webkit.org/show_bug.cgi?id=104538
+
+        Reviewed by Noam Rosenthal.
+
+        The backing tiles had no upper limit defined for the non-GL backend, which could cause them
+        to allocate pixmaps widier or higher than what the underlying graphics systems can handle.
+
+        On top of that GraphicsLayerTextureMapper::prepareBackingStore() would allocate an intermediate
+        pixmap the size of the dirty rect, which would at least on the first paint be the size of the
+        entire layer, again causing allocation of pixmaps with dimensions outside of platform bounds.
+
+        This patch introduces a limit to the size of image buffer tiles, and adds an alternative path
+        for painting where the GraphicsLayer paints directly to the tile instead of over an intermediate
+        pixmap. This alternative path can also be useful later to minimize the amount of pixel copying
+        happening in full repaints.
+
+        * platform/graphics/texmap/GraphicsLayerTextureMapper.cpp:
+        (WebCore::GraphicsLayerTextureMapper::prepareBackingStore):
+        * platform/graphics/texmap/GraphicsLayerTextureMapper.h:
+        (GraphicsLayerTextureMapper):
+        * platform/graphics/texmap/TextureMapper.cpp:
+        (WebCore::BitmapTexture::updateContents):
+        * platform/graphics/texmap/TextureMapper.h:
+        (BitmapTexture):
+        (TextureMapper):
+        * platform/graphics/texmap/TextureMapperBackingStore.cpp:
+        (WebCore::TextureMapperTile::updateContents):
+        (WebCore::TextureMapperTiledBackingStore::updateContents):
+        * platform/graphics/texmap/TextureMapperBackingStore.h:
+        (TextureMapperTile):
+        (TextureMapperTiledBackingStore):
+        * platform/graphics/texmap/TextureMapperImageBuffer.cpp:
+        (WebCore::BitmapTextureImageBuffer::updateContents):
+        (WebCore::TextureMapperImageBuffer::maxTextureSize):
+        * platform/graphics/texmap/TextureMapperImageBuffer.h:
+        (BitmapTextureImageBuffer):
+
+2012-12-12  Aaron Colwell  <acolwell@chromium.org>
+
+        Remove MediaSource 'ended' to 'open' transition when seeking.
+        https://bugs.webkit.org/show_bug.cgi?id=104583
+
+        Reviewed by Eric Carlson.
+
+        Remove the 'ended' to 'open' transition on a seek.
+
+        No new tests. The following tests were updated to reflect the new behavior.
+          http/tests/media/media-source/video-media-source-seek.html
+          http/tests/media/media-source/video-media-source-state-changes.html
+
+        * html/HTMLMediaElement.cpp:
+        (WebCore::HTMLMediaElement::seek):
+
+2012-12-12  Julien Chaffraix  <jchaffraix@webkit.org>
+
+        [CSS Grid Layout] Implement CSS parsing and handling for min-content and max-content
+        https://bugs.webkit.org/show_bug.cgi?id=104747
+
+        Reviewed by Alexis Menard.
+
+        This change adds -webkit-min-content and -webkit-max-content to our <track-breadth> parsing.
+        The rendering is not plugged in and will probably depend on bug 103311.
+
+        Tests: fast/css-grid-layout/grid-columns-rows-get-set-multiple.html:
+               fast/css-grid-layout/grid-columns-rows-get-set.html:
+
+        * css/CSSParser.cpp:
+        (WebCore::CSSParser::parseGridBreadth):
+        * css/StyleResolver.cpp:
+        (WebCore::createGridTrackBreadth):
+        Straight-forward extension of the new code. We were already serializing back properly
+        so no need to touch CSSComputedStyleDeclaration.
+
+2012-12-12  Ryosuke Niwa  <rniwa@webkit.org>
+
+        Copying text with ruby inserts new lines around rt elements
+        https://bugs.webkit.org/show_bug.cgi?id=104765
+
+        Reviewed by Dan Bernstein.
+
+        Don't emit new lines before and after rt.
+
+        Test: editing/pasteboard/copy-paste-ruby-text.html
+
+        * editing/TextIterator.cpp:
+        (WebCore::shouldEmitNewlinesBeforeAndAfterNode):
+
+2012-12-12  Krzysztof Czech  <k.czech@samsung.com>
+
+        [EFL] Possibility to turn off accessibility feature for WebKit-EFL.
+        https://bugs.webkit.org/show_bug.cgi?id=103036
+
+        Reviewed by Laszlo Gombos.
+
+        Guard dependencies for accessibility (ATK), so that they can be turned off.
+
+        No new tests as there is no new functionality.
+
+        * PlatformEfl.cmake:
+        * accessibility/AccessibilityObject.cpp:
+        (WebCore::AccessibilityObject::AccessibilityObject):
+        * accessibility/AccessibilityObject.h:
+        (AccessibilityObject):
+
+2012-12-12  Justin Novosad  <junov@google.com>
+
+        Use render box background over border draw strategy in cases with background-image
+        https://bugs.webkit.org/show_bug.cgi?id=103409
+
+        Reviewed by Simon Fraser.
+
+        The BackgroundOverBorderBleedAvoidance mode was not being used in
+        cases where the background is an opaque image. It was also not
+        being used in cases with multiple layers. The multiple layer
+        case is now safe with respect to color bleeding if the top layer
+        is opaque, thank to the recent addition of layer occlusion culling
+        in r135629.
+
+        No new tests. Testing already covered by the following tests:
+        fast/backgrounds/background-opaque-images-over-color.html
+        fast/backgrounds/gradient-background-leakage-2.html
+
+        * rendering/RenderBox.cpp:
+        (WebCore::RenderBox::determineBackgroundBleedAvoidance):
+        (WebCore::RenderBox::backgroundHasOpaqueTopLayer):
+        * rendering/RenderBox.h:
+        (RenderBox):
+
+2012-12-12  Ilya Tikhonovsky  <loislo@chromium.org>
+
+        Web Inspector: instrument static parts of RenderBlock and RenderBox
+        https://bugs.webkit.org/show_bug.cgi?id=104660
+
+        Reviewed by Yury Semikhatsky.
+
+        Plain vanilla instrumentation.
+
+        * dom/WebCoreMemoryInstrumentation.cpp:
+        (WebCore):
+        (WebCore::WebCoreMemoryInstrumentation::reportMemoryUsage):
+        * dom/WebCoreMemoryInstrumentation.h:
+        (WebCoreMemoryTypes):
+        (WebCoreMemoryInstrumentation):
+        (WebCore):
+        * inspector/InspectorMemoryAgent.cpp:
+        (WebCore::InspectorMemoryAgent::getProcessMemoryDistribution):
+        * rendering/RenderBlock.cpp:
+        (WebCore::RenderBlock::reportStaticMembersMemoryUsage):
+        (WebCore):
+        * rendering/RenderBlock.h:
+        (RenderBlock):
+        * rendering/RenderBox.cpp:
+        (WebCore::RenderBox::reportStaticMembersMemoryUsage):
+        (WebCore):
+        * rendering/RenderBox.h:
+        (RenderBox):
+
+2012-12-12  Ilya Tikhonovsky  <loislo@chromium.org>
+
+        Web Inspector: Native Memory Instrumentation: remove fake root MemoryObjectInfo.
+        https://bugs.webkit.org/show_bug.cgi?id=104796
+
+        Reviewed by Yury Semikhatsky.
+
+        It was not a good idea to introduce a fake root MemoryObjectInfo.
+        It makes a problem when we visit an object without its own MemoryObjectType.
+
+        Example: RenderBox has a global pointer to a hash map.
+        HashMap doesn't have its own object type because it is a generic container.
+        It will inherit object type from the fake root memory object info.
+        The same could happen for another container in another class with other MemoryObjectType.
+
+        This fact forces me to create custom process method for root objects
+        because they need to have their own MemoryObjectInfo with customisable memory object type.
+
+        Drive by fix: InstrumentedPointer* was replaced with Wrapper* because actually it is using
+        for instrumented and not instrumented object classes.
+
+        * inspector/MemoryInstrumentationImpl.cpp:
+        (WebCore::MemoryInstrumentationImpl::processDeferredObjects):
+        (WebCore::MemoryInstrumentationImpl::deferObject):
+        (WebCore::MemoryInstrumentationImpl::reportMemoryUsage):
+        * inspector/MemoryInstrumentationImpl.h:
+        (MemoryInstrumentationImpl):
+
+2012-12-12  Kondapally Kalyan  <kalyan.kondapally@intel.com>
+
+        [EFL [WebGL] [Wk2] Resizing the canvas breaks WebGL.
+        https://bugs.webkit.org/show_bug.cgi?id=104535.
+
+        Reviewed by Kenneth Rohde Christiansen.
+
+        GraphicsContext3DEfl does not re-create the surface on canvas resize, this
+        conflicted with the logic in coordinated graphics Layer.
+        CoordinatedGraphicsLayer checks for GraphicsSurfaceToken to decide if the surface
+        in UI-Process should be recreated or not. With this
+        patch we also check for size of the platform Layer.
+
+        * platform/graphics/efl/GraphicsContext3DEfl.cpp:
+        (WebCore::GraphicsContext3D::createGraphicsSurfaces):
+        * platform/graphics/efl/GraphicsContext3DPrivate.cpp:
+        (GraphicsContext3DPrivate::didResizeCanvas):
+        (GraphicsContext3DPrivate::platformLayerSize):
+        * platform/graphics/efl/GraphicsContext3DPrivate.h:
+        (GraphicsContext3DPrivate):
+
+2012-12-12  Antoine Quint  <graouts@apple.com>
+
+        Web Inspector: Crash in InspectorDOMAgent::pushNodePathToFrontend when inspecting document with CSS generated content
+        https://bugs.webkit.org/show_bug.cgi?id=104780
+
+        Reviewed by Pavel Feldman.
+
+        The pushNodePathForRenderLayerToFrontend() method added to InspectorDOMAgent naively assumed
+        that all RenderLayers have a Node associated to them. However, in the case of CSS generated
+        content, that will not be the case and we would call into pushNodePathToFrontend() with a 0
+        parameter that would hit the first ASSERT in this method. We're now checking that we indeed
+        have an associated node for the provided RenderLayer and return 0 in case we don't, without
+        calling into pushNodePathToFrontend().
+
+        Test: inspector-protocol/layer-tree-generated-content.html
+
+        * inspector/InspectorDOMAgent.cpp:
+        (WebCore::InspectorDOMAgent::pushNodePathForRenderLayerToFrontend):
+
+2012-12-12  Alexander Pavlov  <apavlov@chromium.org>
+
+        Web Inspector: [Crash] Clear cached stylesheet rules in InspectorStyleSheet::deleteRule()
+        https://bugs.webkit.org/show_bug.cgi?id=104806
+
+        Reviewed by Vsevolod Vlasov.
+
+        Cached rules (m_flatRules) should get cleared whenever a rule is deleted.
+
+        Test: inspector/styles/undo-add-rule-crash.html
+
+        * inspector/InspectorStyleSheet.cpp:
+        (WebCore::InspectorStyleSheet::deleteRule):
+
+2012-12-12  Stephen White  <senorblanco@chromium.org>
+
+        Unreviewed, rolling out r136975.
+        http://trac.webkit.org/changeset/136975
+        https://bugs.webkit.org/show_bug.cgi?id=90405
+
+        Correctness issues.
+
+        * dom/Element.cpp:
+        * dom/Element.h:
+        (Element):
+        * dom/ElementRareData.h:
+        (ElementRareData):
+        (WebCore::ElementRareData::ElementRareData):
+        * platform/graphics/texmap/TextureMapperImageBuffer.cpp:
+        (WebCore::BitmapTextureImageBuffer::applyFilters):
+        * rendering/FilterEffectRenderer.cpp:
+        (WebCore::createCustomFilterEffect):
+        (WebCore::FilterEffectRenderer::buildReferenceFilter):
+        (WebCore::FilterEffectRenderer::build):
+        * rendering/FilterEffectRenderer.h:
+        (FilterEffectRenderer):
+        * rendering/RenderLayer.cpp:
+        (WebCore::RenderLayer::updateOrRemoveFilterEffectRenderer):
+        * rendering/RenderObject.cpp:
+        (WebCore::RenderObject::willBeDestroyed):
+        * rendering/svg/RenderSVGResourceContainer.cpp:
+        (WebCore::RenderSVGResourceContainer::registerResource):
+        * rendering/svg/SVGResources.cpp:
+        (WebCore::SVGResources::buildCachedResources):
+        * rendering/svg/SVGResourcesCache.cpp:
+        (WebCore::SVGResourcesCache::addResourcesFromRenderObject):
+        (WebCore::SVGResourcesCache::clientStyleChanged):
+        (WebCore::SVGResourcesCache::resourceDestroyed):
+        * svg/SVGDocumentExtensions.cpp:
+        (WebCore::SVGDocumentExtensions::addPendingResource):
+        (WebCore::SVGDocumentExtensions::isElementPendingResources):
+        (WebCore::SVGDocumentExtensions::isElementPendingResource):
+        (WebCore::SVGDocumentExtensions::removeElementFromPendingResources):
+        (WebCore::SVGDocumentExtensions::removeElementFromPendingResourcesForRemoval):
+        * svg/SVGDocumentExtensions.h:
+        (WebCore):
+        (SVGDocumentExtensions):
+        * svg/SVGElement.cpp:
+        (WebCore::SVGElement::hasPendingResources):
+        (WebCore):
+        (WebCore::SVGElement::setHasPendingResources):
+        (WebCore::SVGElement::clearHasPendingResourcesIfPossible):
+        * svg/SVGElement.h:
+        (SVGElement):
+        (WebCore::SVGElement::buildPendingResource):
+        * svg/SVGElementRareData.h:
+        (WebCore::SVGElementRareData::SVGElementRareData):
+        (WebCore::SVGElementRareData::hasPendingResources):
+        (WebCore::SVGElementRareData::setHasPendingResources):
+        (SVGElementRareData):
+        * svg/SVGStyledElement.cpp:
+        (WebCore::SVGStyledElement::buildPendingResourcesIfNeeded):
+
+2012-12-12  Stephen White  <senorblanco@chromium.org>
+
+        Unreviewed, rolling out r137022.
+        http://trac.webkit.org/changeset/137022
+
+        Precursor to rollout of 136975.
+
+        * rendering/svg/SVGResources.cpp:
+        (WebCore::SVGResources::buildCachedResources):
+
+2012-12-12  Stephen White  <senorblanco@chromium.org>
+
+        Unreviewed, rolling out r137027.
+        http://trac.webkit.org/changeset/137027
+
+        Precursor to rollout of 136975.
+
+        * dom/ElementRareData.h:
+        (ElementRareData):
+
+2012-12-12  Alexei Filippov  <alph@chromium.org>
+
+        Web Inspector: add memory used by memory allocator itself to NMI
+        https://bugs.webkit.org/show_bug.cgi?id=93372
+
+        Make native memory instrumentation report memory retained
+        for the memory allocator internal purposes.
+
+        Reviewed by Yury Semikhatsky.
+
+        * inspector/front-end/NativeMemorySnapshotView.js:
+        (WebInspector.MemoryBlockViewProperties._initialize):
+        * platform/chromium/MemoryUsageSupportChromium.cpp:
+        (WebCore::MemoryUsageSupport::memoryUsageByComponents):
+
+2012-12-12  Sheriff Bot  <webkit.review.bot@gmail.com>
+
+        Unreviewed, rolling out r137438.
+        http://trac.webkit.org/changeset/137438
+        https://bugs.webkit.org/show_bug.cgi?id=104798
+
+        assertion reached when removing tile (Requested by tmpsantos
+        on #webkit).
+
+        * page/Frame.cpp:
+        (WebCore::Frame::setTiledBackingStoreEnabled):
+        * platform/graphics/TiledBackingStore.cpp:
+        (WebCore::TiledBackingStore::TiledBackingStore):
+        (WebCore::TiledBackingStore::setTileCreationDelay):
+        (WebCore::TiledBackingStore::coverWithTilesIfNeeded):
+        (WebCore::TiledBackingStore::updateTileBuffers):
+        (WebCore::TiledBackingStore::createTiles):
+        (WebCore::TiledBackingStore::isTileBufferUpdatesSuspended):
+        (WebCore::TiledBackingStore::startTileBufferUpdateTimer):
+        (WebCore::TiledBackingStore::tileBufferUpdateTimerFired):
+        (WebCore::TiledBackingStore::startBackingStoreUpdateTimer):
+        (WebCore::TiledBackingStore::backingStoreUpdateTimerFired):
+        * platform/graphics/TiledBackingStore.h:
+        (TiledBackingStore):
+        (WebCore::TiledBackingStore::tileCreationDelay):
+        * platform/graphics/TiledBackingStoreClient.h:
+        (WebCore::TiledBackingStoreClient::tiledBackingStoreUpdatesAllowed):
+
+2012-12-12  Csaba Osztrogonác  <ossy@webkit.org>
+
+        [Qt] Unreviewed typo fix after r137446.
+
+        * WebCore.pri:
+
+2012-12-12  Zan Dobersek  <zandobersek@gmail.com>
+
+        [GTK] Remove the last of unnecessary configuration options in configure.ac
+        https://bugs.webkit.org/show_bug.cgi?id=104793
+
+        Reviewed by Martin Robinson.
+
+        Remove the feature define overriding that's based on the automake variables which are
+        not set anymore due to the corresponding configuration options being removed.
+
+        No new tests - no new functionality.
+
+        * GNUmakefile.am:
+
+2012-12-12  Simon Hausmann  <simon.hausmann@digia.com>
+
+        [Qt] Fix build on Mac
+
+        Reviewed by Csaba Osztrogonác.
+
+        On Mac OS X we have sqlite as a system library available.
+
+        * WebCore.pri:
+
+2012-12-12  Simon Hausmann  <simon.hausmann@digia.com>
+
+        [Qt] Fix linkage against SQLite
+        https://bugs.webkit.org/show_bug.cgi?id=104781
+
+        Reviewed by Csaba Osztrogonác.
+
+        Detect SQLite either through pkg-config, from the SQLITE3SRCDIR
+        environment variable or from qtbase via a qt5.git build. Bail out early
+        with an error message if neither option applies.
+
+        This removes the usage of $$QT.core.sources and the dependency on Qt's
+        system-sqlite configure setting. We should always favour a system
+        library over a copy in Qt.
+
+        * Target.pri:
+        * WebCore.pri:
+
+2012-12-12  Allan Sandfeld Jensen  <allan.jensen@digia.com>
+
+        [TexMap] Uninitialized m_context pointer in TextureMapper
+        https://bugs.webkit.org/show_bug.cgi?id=104785
+
+        Reviewed by Kenneth Rohde Christiansen.
+
+        * platform/graphics/texmap/TextureMapper.cpp:
+        (WebCore::TextureMapper::TextureMapper):
+        * platform/graphics/texmap/TextureMapperGL.cpp:
+        (WebCore::TextureMapperGL::TextureMapperGL):
+
+2012-12-12  Tommy Widenflycht  <tommyw@google.com>
+
+        MediaStream API: Change the data channel descriptor pattern to a handler pattern
+        https://bugs.webkit.org/show_bug.cgi?id=104543
+
+        Reviewed by Kent Tamura.
+
+        In short the code is refactured to use the Handler/Client pattern (see RTCPeerConnectionHandler)
+        instead of the Descriptor pattern.
+        This will fix lifetime/memory/code structure issues in the chromium port.
+
+        Existing tests cover this patch.
+
+        * CMakeLists.txt:
+        * GNUmakefile.list.am:
+        * Modules/mediastream/RTCDataChannel.cpp:
+        (WebCore::RTCDataChannel::create):
+        (WebCore::RTCDataChannel::RTCDataChannel):
+        (WebCore::RTCDataChannel::~RTCDataChannel):
+        (WebCore::RTCDataChannel::label):
+        (WebCore::RTCDataChannel::reliable):
+        (WebCore::RTCDataChannel::readyState):
+        (WebCore::RTCDataChannel::bufferedAmount):
+        (WebCore::RTCDataChannel::send):
+        (WebCore::RTCDataChannel::close):
+        (WebCore::RTCDataChannel::didChangeReadyState):
+        (WebCore::RTCDataChannel::didReceiveStringData):
+        (WebCore::RTCDataChannel::didReceiveRawData):
+        (WebCore::RTCDataChannel::didDetectError):
+        (WebCore::RTCDataChannel::stop):
+        * Modules/mediastream/RTCDataChannel.h:
+        (WebCore):
+        (RTCDataChannel):
+        * Modules/mediastream/RTCPeerConnection.cpp:
+        (WebCore::RTCPeerConnection::didAddRemoteDataChannel):
+        * Modules/mediastream/RTCPeerConnection.h:
+        (RTCPeerConnection):
+        * WebCore.gypi:
+        * platform/chromium/support/WebRTCDataChannel.cpp: Removed.
+        * platform/mediastream/RTCDataChannelDescriptor.h: Removed.
+        * platform/mediastream/RTCDataChannelHandler.h: Copied from Source/WebCore/platform/mediastream/RTCDataChannelDescriptor.cpp.
+        (WebCore):
+        (RTCDataChannelHandler):
+        (WebCore::RTCDataChannelHandler::~RTCDataChannelHandler):
+        * platform/mediastream/RTCDataChannelHandlerClient.h: Renamed from Source/WebCore/platform/mediastream/RTCDataChannelDescriptor.cpp.
+        (WebCore):
+        (RTCDataChannelHandlerClient):
+        (WebCore::RTCDataChannelHandlerClient::~RTCDataChannelHandlerClient):
+        * platform/mediastream/RTCPeerConnectionHandler.cpp:
+        (WebCore):
+        (WebCore::RTCPeerConnectionHandler::create):
+        * platform/mediastream/RTCPeerConnectionHandler.h:
+        (WebCore):
+        (RTCPeerConnectionHandler):
+        * platform/mediastream/RTCPeerConnectionHandlerClient.h:
+        (WebCore):
+        (RTCPeerConnectionHandlerClient):
+        * platform/mediastream/chromium/RTCDataChannelHandlerChromium.cpp: Added.
+        (WebCore):
+        (WebCore::RTCDataChannelHandlerChromium::create):
+        (WebCore::RTCDataChannelHandlerChromium::RTCDataChannelHandlerChromium):
+        (WebCore::RTCDataChannelHandlerChromium::~RTCDataChannelHandlerChromium):
+        (WebCore::RTCDataChannelHandlerChromium::setClient):
+        (WebCore::RTCDataChannelHandlerChromium::label):
+        (WebCore::RTCDataChannelHandlerChromium::isReliable):
+        (WebCore::RTCDataChannelHandlerChromium::bufferedAmount):
+        (WebCore::RTCDataChannelHandlerChromium::sendStringData):
+        (WebCore::RTCDataChannelHandlerChromium::sendRawData):
+        (WebCore::RTCDataChannelHandlerChromium::close):
+        (WebCore::RTCDataChannelHandlerChromium::didChangeReadyState):
+        (WebCore::RTCDataChannelHandlerChromium::didReceiveStringData):
+        (WebCore::RTCDataChannelHandlerChromium::didReceiveRawData):
+        (WebCore::RTCDataChannelHandlerChromium::didDetectError):
+        * platform/mediastream/chromium/RTCDataChannelHandlerChromium.h: Added.
+        (WebCore):
+        (RTCDataChannelHandlerChromium):
+        * platform/mediastream/chromium/RTCPeerConnectionHandlerChromium.cpp:
+        (WebCore::RTCPeerConnectionHandlerChromium::createDataChannel):
+        (WebCore::RTCPeerConnectionHandlerChromium::didAddRemoteDataChannel):
+        * platform/mediastream/chromium/RTCPeerConnectionHandlerChromium.h:
+        (WebCore):
+        (RTCPeerConnectionHandlerChromium):
+
+2012-12-12  Huang Dongsung  <luxtella@company100.net>
+
+        Coordinated Graphics: Refactor TiledBackingStore code in CoordinatedGraphicsLayer.
+        https://bugs.webkit.org/show_bug.cgi?id=103959
+
+        Reviewed by Kenneth Rohde Christiansen.
+
+        TiledBackingStore::setCommitTileUpdatesOnIdleEventLoop() is used when class
+        methods cannot be called asynchronously by client. Updates of tiles are
+        committed as soon as all the events in event queue have been processed.
+        After this patch Frame sets m_commitTileUpdatesOnIdleEventLoop to true.
+
+        In addition, remove TiledBackingStoreClient::tiledBackingStoreUpdatesAllowed()
+        which was introduced for Coordinated Graphics.
+
+        Refactoring covered by existing tests.
+
+        * page/Frame.cpp:
+        (WebCore::Frame::setTiledBackingStoreEnabled):
+        * platform/graphics/TiledBackingStore.cpp:
+        (WebCore::TiledBackingStore::TiledBackingStore):
+        (WebCore::TiledBackingStore::setTrajectoryVector):
+          Separate setting a trajectory vector from coverWithTilesIfNeeded().
+        (WebCore::TiledBackingStore::coverWithTilesIfNeeded):
+        (WebCore::TiledBackingStore::updateTileBuffers):
+        (WebCore::TiledBackingStore::createTiles):
+        (WebCore::TiledBackingStore::isTileBufferUpdatesSuspended):
+        (WebCore::TiledBackingStore::startTileBufferUpdateTimer):
+        (WebCore::TiledBackingStore::tileBufferUpdateTimerFired):
+        (WebCore::TiledBackingStore::startBackingStoreUpdateTimer):
+        (WebCore::TiledBackingStore::backingStoreUpdateTimerFired):
+        * platform/graphics/TiledBackingStore.h:
+        (TiledBackingStore):
+        (WebCore::TiledBackingStore::setCommitTileUpdatesOnIdleEventLoop):
+        * platform/graphics/TiledBackingStoreClient.h:
+        (WebCore::TiledBackingStoreClient::tiledBackingStoreHasPendingTileCreation):
+            If TiledBackingStore does not create all tiles, TiledBackingStore
+            notifies a client of needing to create tiles more, when
+            m_commitTileUpdatesOnIdleEventLoop is false.
+
+2012-12-11  Jocelyn Turcotte  <jocelyn.turcotte@digia.com>
+
+        [Qt] Fix the inspector not showing up on Windows
+        https://bugs.webkit.org/show_bug.cgi?id=104677
+
+        Reviewed by Simon Hausmann.
+
+        * Target.pri:
+
+2012-11-29  Yury Semikhatsky  <yurys@chromium.org>
+
+        Web Inspector: Heap snapshot crashes on any page in MacOS Canary
+        https://bugs.webkit.org/show_bug.cgi?id=103076
+
+        Reviewed by Adam Barth.
+
+        Provide global object name resolver to the heap profiler. The callback allows
+        to safely retrieve document URL to be used as a label for corresponding global
+        object in the heap snapshot.
+
+        Test: inspector-protocol/take-heap-snapshot.html
+
+        * bindings/v8/ScriptProfiler.cpp:
+        (WebCore):
+        (WebCore::ScriptProfiler::takeHeapSnapshot):
+
+2012-12-12  Sheriff Bot  <webkit.review.bot@gmail.com>
+
+        Unreviewed, rolling out r137428.
+        http://trac.webkit.org/changeset/137428
+        https://bugs.webkit.org/show_bug.cgi?id=104776
+
+        It broke the build everywhere (Requested by Ossy on #webkit).
+
+        * platform/graphics/surfaces/mac/GraphicsSurfaceMac.cpp:
+        (WebCore::GraphicsSurface::platformPaintToTextureMapper):
+        * platform/graphics/texmap/TextureMapperGL.cpp:
+        (WebCore::TextureMapperGL::drawQuad):
+        (WebCore::TextureMapperGL::drawBorder):
+        (WebCore::TextureMapperGL::drawTexture):
+        (WebCore):
+        (WebCore::TextureMapperGL::drawTextureRectangleARB):
+        (WebCore::TextureMapperGL::drawSolidColor):
+        (WebCore::TextureMapperGL::drawTextureWithAntialiasing):
+        (WebCore::TextureMapperGL::drawTexturedQuadWithProgram):
+        * platform/graphics/texmap/TextureMapperGL.h:
+        (TextureMapperGL):
+        * platform/graphics/texmap/TextureMapperShaderManager.cpp:
+        (WebCore::getShaderSpec):
+        * platform/graphics/texmap/TextureMapperShaderManager.h:
+        (TextureMapperShaderProgram):
+
+2012-12-12  Martin Robinson  <mrobinson@igalia.com>
+
+        Web inspector prints a warning about "Debug" not being localized
+        https://bugs.webkit.org/show_bug.cgi?id=104679
+
+        Reviewed by Vsevolod Vlasov.
+
+        Add a missing localization entry for the "Debug" string which is used in the web
+        inspector front-end. This prevents warnings about a missing localized version
+        of the word "Debug" and allows it to be properly localized.
+
+        * English.lproj/localizedStrings.js: Add "Debug"
+
+2012-12-12  Shinya Kawanaka  <shinyak@chromium.org>
+
+        [Shadow DOM] Implement HTMLShadowElement::olderShadowRoot
+        https://bugs.webkit.org/show_bug.cgi?id=104218
+
+        Reviewed by Hajime Morita.
+
+        Implements HTMLShadowElement::olderShadowRoot, which returns the ShadowRoot the HTMLShadowElement is assigned to.
+        When such ShadowRoot does not exist, 0 is returned.
+
+        Test: fast/dom/shadow/olderShadowRoot-in-shadowelement.html
+
+        * dom/ElementShadow.cpp:
+        (WebCore::ElementShadow::ensureDistributionFromDocument): Ensures distribution of this ElementShadow and
+        all of the parent TreeScope distribution. This function will be shared for Bug 104345.
+        (WebCore):
+        * dom/ElementShadow.h:
+        (ElementShadow):
+        * html/shadow/HTMLShadowElement.cpp:
+        (WebCore::HTMLShadowElement::olderShadowRoot):
+        (WebCore):
+        * html/shadow/HTMLShadowElement.h:
+        * html/shadow/HTMLShadowElement.idl:
+
+2012-12-12  No'am Rosenthal  <noam@webkit.org>
+
+        [Texmap] Consolidate redundant code for ARB_RECT texture
+        https://bugs.webkit.org/show_bug.cgi?id=104705
+
+        Reviewed by Kenneth Rohde Christiansen.
+
+        Instead of having a whole different function for RECT textures,
+        keep the existing functions and pass a flag that tells
+        TextureMapperGL to use the non-normalized coordinates and the
+        RECT shaders.
+
+        No new tests, refactor only. Tested to not break WebGL on
+        Qt-Mac.
+
+        * platform/graphics/surfaces/mac/GraphicsSurfaceMac.cpp:
+        (WebCore::GraphicsSurface::platformPaintToTextureMapper):
+        * platform/graphics/texmap/TextureMapperGL.cpp:
+        (WebCore::TextureMapperGL::drawQuad):
+            Compensate for rect textures in drawQuad.
+
+        (WebCore::TextureMapperGL::drawBorder):
+        (WebCore::TextureMapperGL::drawTexture):
+        (WebCore::TextureMapperGL::drawSolidColor):
+        (WebCore::TextureMapperGL::drawTextureWithAntialiasing):
+        (WebCore::TextureMapperGL::drawTexturedQuadWithProgram):
+            Pass flags to TextureMapperGL::drawQuad instead of a bool.
+
+        * platform/graphics/texmap/TextureMapperGL.h:
+        (TextureMapperGL):
+        * platform/graphics/texmap/TextureMapperShaderManager.cpp:
+        (WebCore::getShaderSpec):
+        * platform/graphics/texmap/TextureMapperShaderManager.h:
+        (TextureMapperShaderProgram):
+            Compensate for the texture-size in the vertex
+            shader instead of in the fragment shader.
+
+2012-12-11  Hayato Ito  <hayato@chromium.org>
+
+        REGRESSION(r137408): breaks chromium's browser tests which use WebKitShadowRoot (Requested by hayato on #webkit).
+        https://bugs.webkit.org/show_bug.cgi?id=104770
+
+        Unreviewed, build fix.
+
+        * dom/ShadowRoot.idl:
+        * page/DOMWindow.idl:
+
+2012-12-11  Sheriff Bot  <webkit.review.bot@gmail.com>
+
+        Unreviewed, rolling out r137333, r137344, r137364, and
+        r137377.
+        http://trac.webkit.org/changeset/137333
+        http://trac.webkit.org/changeset/137344
+        http://trac.webkit.org/changeset/137364
+        http://trac.webkit.org/changeset/137377
+        https://bugs.webkit.org/show_bug.cgi?id=104771
+
+        Caused a raft of browser_test failures in Chromium (Requested
+        by aklein on #webkit).
+
+        * loader/DocumentLoader.cpp:
+        (WebCore::DocumentLoader::setRequest):
+        (WebCore::DocumentLoader::subresource):
+        (WebCore::DocumentLoader::addSubresourceLoader):
+        (WebCore::DocumentLoader::removeSubresourceLoader):
+        (WebCore::DocumentLoader::startLoadingMainResource):
+        * loader/MainResourceLoader.cpp:
+        (WebCore::MainResourceLoader::MainResourceLoader):
+        (WebCore::MainResourceLoader::~MainResourceLoader):
+        (WebCore::MainResourceLoader::receivedError):
+        (WebCore::MainResourceLoader::willCancel):
+        (WebCore::MainResourceLoader::didCancel):
+        (WebCore::MainResourceLoader::continueAfterNavigationPolicy):
+        (WebCore::MainResourceLoader::addData):
+        (WebCore::MainResourceLoader::willSendRequest):
+        (WebCore::MainResourceLoader::continueAfterContentPolicy):
+        (WebCore::MainResourceLoader::didReceiveResponse):
+        (WebCore::MainResourceLoader::didReceiveData):
+        (WebCore::MainResourceLoader::didFinishLoading):
+        (WebCore::MainResourceLoader::didFail):
+        (WebCore::MainResourceLoader::reportMemoryUsage):
+        (WebCore::MainResourceLoader::handleSubstituteDataLoadNow):
+        (WebCore::MainResourceLoader::loadNow):
+        (WebCore):
+        (WebCore::MainResourceLoader::load):
+        (WebCore::MainResourceLoader::setDefersLoading):
+        * loader/MainResourceLoader.h:
+        (MainResourceLoader):
+        * loader/ResourceLoader.cpp:
+        (WebCore::ResourceLoader::willSendRequest):
+        * loader/ResourceLoader.h:
+        (ResourceLoader):
+        (WebCore::ResourceLoader::defersLoading):
+        * loader/SubresourceLoader.cpp:
+        (WebCore::SubresourceLoader::willSendRequest):
+        * loader/appcache/ApplicationCacheHost.cpp:
+        (WebCore::ApplicationCacheHost::maybeLoadFallbackForMainResponse):
+        (WebCore::ApplicationCacheHost::maybeLoadFallbackForMainError):
+        * loader/cache/CachedRawResource.cpp:
+        (WebCore::CachedRawResource::willSendRequest):
+        * loader/cache/CachedResourceLoader.cpp:
+        (WebCore::CachedResourceLoader::loadDone):
+        * loader/mac/DocumentLoaderMac.cpp:
+        (WebCore::DocumentLoader::schedule):
+        (WebCore::DocumentLoader::unschedule):
+
+2012-12-11  Kentaro Hara  <haraken@chromium.org>
+
+        Unreviewed, rolling out r137398.
+        http://trac.webkit.org/changeset/137398
+        https://bugs.webkit.org/show_bug.cgi?id=104188
+
+        A bunch of webaudio tests hit ASSERTs
+
+        * CMakeLists.txt:
+        * DerivedSources.make:
+        * DerivedSources.pri:
+        * GNUmakefile.list.am:
+        * Modules/webaudio/AudioContext.cpp:
+        (WebCore::AudioContext::createOfflineContext):
+        (WebCore):
+        * Modules/webaudio/AudioContext.h:
+        (AudioContext):
+        * Modules/webaudio/DOMWindowWebAudio.idl:
+        * Modules/webaudio/OfflineAudioContext.cpp: Removed.
+        * Modules/webaudio/OfflineAudioContext.h: Removed.
+        * Modules/webaudio/OfflineAudioContext.idl: Removed.
+        * WebCore.gypi:
+        * WebCore.xcodeproj/project.pbxproj:
+        * bindings/generic/RuntimeEnabledFeatures.h:
+        * bindings/js/JSAudioContextCustom.cpp:
+        (WebCore::JSAudioContextConstructor::constructJSAudioContext):
+        * bindings/v8/custom/V8AudioContextCustom.cpp:
+        (WebCore::V8AudioContext::constructorCallbackCustom):
+
+2012-12-11  Shinya Kawanaka  <shinyak@chromium.org>
+
+        [Shadow DOM] registering InsertionPoints to ShadowRoot should work out of a document.
+        https://bugs.webkit.org/show_bug.cgi?id=104346
+
+        Reviewed by Hajime Morita.
+
+        We need to register InsertionPoints even if ShadowRoot is out of Document, since distribution should work
+        out of Document, too.
+
+        Instead of checking isInDocument(), we have to make sure InsertionPoint and an element which InsertionPoint
+        inserted into have the same treescope.
+
+        Tests: fast/dom/shadow/has-content-elements.html
+               fast/dom/shadow/has-shadow-insertion-point.html
+
+        * html/shadow/InsertionPoint.cpp:
+        (WebCore::InsertionPoint::insertedInto):
+        (WebCore::InsertionPoint::removedFrom):
+
+2012-12-11  Takashi Sakamoto  <tasak@google.com>
+
+        Text nodes in shadow roots don't inherit style properly
+        https://bugs.webkit.org/show_bug.cgi?id=101116
+
+        Reviewed by Hajime Morita.
+
+        Use NodeRenderingContext to resolve styles of text nodes.
+        If text nodes are direct children of shadow roots, the text nodes
+        should be inherited styles from their shadow hosts.
+        But if reset-style-inheritance flag is true, the text nodes should
+        not be inherited. And if text nodes are distributed nodes,
+        we have to check whether their insertion point's
+        reset-style-inheritance.
+        c.f. shadow dom spec is:
+        http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#styles
+
+        Test: fast/dom/shadow/text-node-in-shadow.html
+
+        * css/StyleResolver.cpp:
+        (WebCore::StyleResolver::styleForElement):
+        Modified to use defaultStyleForElement if the given element has
+        no parent style.
+        (WebCore::StyleResolver::initForStyleResolve):
+        Removed shouldResetStyleInheritance, because now NodeRenderingContext
+        resetStyleInheritance() takes care of reset-style-inheritance of
+        both shadow roots and insertion points.
+        (WebCore::StyleResolver::defaultStyleForElement):
+        Added to create a default style for elements.
+        (WebCore):
+        (WebCore::StyleResolver::styleForText):
+        Use NodeRenderingContext to find the parent node for style from the
+        given text node. If no parent node is found or reset-style-inheritance
+        is true, returns a default style (i.e. empty render style).
+        Otherwise, just returns the found node's style.
+        * css/StyleResolver.h:
+        (StyleResolver):
+        * dom/ComposedShadowTreeWalker.cpp:
+        (WebCore::ComposedShadowTreeWalker::ParentTraversalDetails::didTraverseInsertionPoint):
+        Modify to consider insertion point's resetStyleInheritance.
+        * dom/NodeRenderingContext.cpp:
+        (WebCore::NodeRenderingContext::createRendererForTextIfNeeded):
+        Since NodeRenderingContext has already found a parent node for
+        rendering and style and a parentRenderer is just the found node's
+        renderer, we have to only check reset-style-inheritance.
+        If reset, use default style. Otherwise, the parentRenderer's style.
+        * dom/Text.cpp:
+        (WebCore::Text::recalcTextStyle):
+        Use styleForText instead of parentRenderer's styles if the given text
+        node is a direct child of a shadow root or a direct child of a shadow
+        host.
+
+2012-12-11  Takashi Sakamoto  <tasak@google.com>
+
+        Hide HOST_RULE behind SHADOW_DOM flag.
+        https://bugs.webkit.org/show_bug.cgi?id=102321
+
+        Reviewed by Dimitri Glazkov.
+
+        @host @-rules are only available when the rules are declared in styles
+        in shadow dom trees. So if SHADOW_DOM is disabled, we don't need
+        @host @-rules.
+
+        No new tests. Just hide HOST_RULE behind SHADOW_DOM flag.
+
+        * css/StyleResolver.h:
+        Hide "class ShadowRuleHost".
+        * css/StyleRule.cpp:
+        (WebCore::StyleRuleBase::reportMemoryUsage):
+        (WebCore::StyleRuleBase::destroy):
+        (WebCore::StyleRuleBase::copy):
+        (WebCore::StyleRuleBase::createCSSOMWrapper):
+        * css/StyleRule.h:
+        (StyleRuleBase):
+        Hide "Host" type and isHostRule.
+        (StyleRuleHost):
+        Hide "class StyleRuleHost".
+        * css/StyleSheetContents.cpp:
+        (WebCore::childRulesHaveFailedOrCanceledSubresources):
+
+2012-12-11  Dominic Mazzoni  <dmazzoni@google.com>
+
+        AX: accessibilityIsIgnored should avoid computing textUnderElement
+        https://bugs.webkit.org/show_bug.cgi?id=104688
+
+        Reviewed by Chris Fleizach.
+
+        Simplify the logic in accessibilityIsIgnored without affecting
+        the results of any tests. In particular, avoid expensive calls to
+        textUnderElement.
+
+        Covered by existing tests.
+
+        * accessibility/AccessibilityNodeObject.cpp:
+        (WebCore::AccessibilityNodeObject::isGenericFocusableElement):
+        * accessibility/AccessibilityRenderObject.cpp:
+        (WebCore::AccessibilityRenderObject::accessibilityIsIgnored):
+
+2012-12-11  Kentaro Hara  <haraken@chromium.org>
+
+        [V8] Reachable event listeners on image elements can be collected in a minor DOM GC
+        https://bugs.webkit.org/show_bug.cgi?id=104734
+
+        Reviewed by Kenneth Russell.
+
+        A major DOM GC treats image elements specially. In
+        V8GCController::opaqueRootForGC(), a major DOM GC puts image elements
+        that have pending activities into the same object group of their document.
+        This guarantees that image elements that have pending activities
+        are not garbage collected in the major DOM GC.
+
+        This patch adds the same special handling to a minor DOM GC to guarantee
+        the same thing in the minor DOM GC too.
+
+        In long-term, we might want to remove the special handling by making
+        image elements active DOM nodes.
+
+        Test: Manually confirmed that all characters in
+        http://alteredqualia.com/three/examples/webgl_animation_skinning_tf2.html
+        are rendered correctly.
+
+        * bindings/v8/V8GCController.cpp:
+        (WebCore::V8GCController::opaqueRootForGC):
+        (WebCore::gcTree):
+
+2012-12-11  Dominic Mazzoni  <dmazzoni@google.com>
+
+        AX: Make isActionSupported cross-platform.
+        https://bugs.webkit.org/show_bug.cgi?id=104681
+
+        Reviewed by Chris Fleizach.
+
+        Add UserGestureIndicator to increment() and decrement()
+        so that all accessibility actions are treated as
+        user actions, not scripted actions.
+
+        * accessibility/AccessibilityNodeObject.cpp:
+        (WebCore::AccessibilityNodeObject::increment):
+        (WebCore::AccessibilityNodeObject::decrement):
+
+2012-12-11  Viatcheslav Ostapenko  <v.ostapenko@samsung.com>
+
+        Remove conversion to/from float and float division from ImageFrame::setRGBA
+        https://bugs.webkit.org/show_bug.cgi?id=103693
+
+        Reviewed by Brent Fulgham.
+
+        Replace floating point operations used for alpha premultiply with fixed point arithmetic
+        which is basically integer operations. Allows to shave extra couple percent from decoding
+        images with transparency.
+
+        Covered by existing tests.
+
+        * platform/image-decoders/ImageDecoder.h:
+        (ImageFrame):
+        (WebCore::ImageFrame::fixPointUnsignedMultiply):
+        (WebCore::ImageFrame::setRGBA):
+
+2012-12-11  Kihong Kwon  <kihong.kwon@samsung.com>
+
+        Vibration API: IDL type doesn't match implementation type
+        https://bugs.webkit.org/show_bug.cgi?id=103899
+
+        Reviewed by Kentaro Hara.
+
+        According to WebIDL, "unsigned long" corresponds to "unsigned" in the platform.
+        Therefore unsigned long need to be changed to unsigned for the Vibration API.
+        - Change a parameter type of vibrate function from unsigned long to unsigned.
+
+        No new tests, it is covered by exist test.
+
+        * Modules/vibration/NavigatorVibration.cpp:
+        (WebCore::NavigatorVibration::vibrate):
+        * Modules/vibration/NavigatorVibration.h:
+        (NavigatorVibration):
+        * Modules/vibration/Vibration.cpp:
+        (WebCore::Vibration::vibrate):
+        * Modules/vibration/Vibration.h:
+        (Vibration):
+        * Modules/vibration/VibrationClient.h:
+        (VibrationClient):
+        * bindings/js/JSDOMBinding.h:
+        * bindings/scripts/CodeGeneratorJS.pm:
+        Remove workaround codes for the Vibration API which is mapped from unsigned long to unsigned long.
+        It should be mapped from unsigned long to unsigned by WebIDL spec.
+        (GetNativeVectorInnerType):
+        * bindings/scripts/test/JS/JSTestObj.cpp:
+        (WebCore::jsTestObjPrototypeFunctionOverloadedMethod10):
+        (WebCore::jsTestObjPrototypeFunctionMethodWithUnsignedLongSequence):
+
+2012-12-11  Xinazhu Wang  <wangxianzhu@chromium.org>
+
+        ScrollingCoordinator::hasVisibleSlowRepaintFixedObject() should exclude out-of-view fixed position elements
+        https://bugs.webkit.org/show_bug.cgi?id=102543
+
+        Let RenderLayerCompositor manage the reasons that fixed position elements are not composited.
+        Check the reason in ScrollingCoordinator::hasVisibleSlowRepaintFixedObjects(), don't let fixed position layer not composited with explicit reasons cause slow scrolling.
+
+        Reviewed by James Robinson.
+
+        Test: compositing/layer-creation/fixed-position-out-of-view-scroll-reason.html
+
+        * page/scrolling/ScrollingCoordinator.cpp:
+        (WebCore::ScrollingCoordinator::hasVisibleSlowRepaintFixedObjects): Exclude fixed position elements that are not composited for explicit reasons.
+        * rendering/RenderLayerCompositor.cpp:
+        (WebCore::RenderLayerCompositor::computeCompositingRequirements): Manages m_fixedPositionLayerNotCompositedReasonMap.
+        (WebCore::RenderLayerCompositor::needsToBeComposited):
+        (WebCore::RenderLayerCompositor::requiresCompositingLayer):
+        (WebCore::RenderLayerCompositor::requiresCompositingForPosition):
+        * rendering/RenderLayerCompositor.h:
+        (WebCore::RenderLayerCompositor::fixedPositionLayerNotCompositedReason): Now outputs fixedPositionLayerNotCompositedreason.
+        (RenderLayerCompositor):
+
+2012-12-11  Hayato Ito  <hayato@chromium.org>
+
+        [Shadow DOM] Kill ShadowRoot constructor
+        https://bugs.webkit.org/show_bug.cgi?id=102913
+
+        Reviewed by Dimitri Glazkov.
+
+        Remove ShadowRoot constructor in favor of Element.webkitCreateShadowRoot().
+
+        No new tests. Update existing tests.
+
+        * dom/ShadowRoot.idl:
+        * page/DOMWindow.idl:
+        * testing/Internals.cpp:
+        (WebCore::Internals::createShadowRoot):
+        (WebCore):
+        * testing/Internals.h:
+        (Internals):
+        * testing/Internals.idl:
+
+2012-12-11  Antti Koivisto  <antti@apple.com>
+
+        Add Element-specific traversal functions
+        https://bugs.webkit.org/show_bug.cgi?id=104685
+
+        Reviewed by Ryosuke Niwa.
+
+        In many cases where we use NodeTraversal we really only want Elements. By having
+        Element specific iteration functions we can tighten the code and make it faster too.
+
+        This patch adds ElementTraversal namespace, similar to NodeTraversal. It also switches
+        bunch of NodeTraversal call sites that obviously only care about elements to using
+        the new interface.
+        
+        This should be a speedup too as we avoid number of branches by not having to look
+        for children of non-ContainerNodes and by allowing use of ContainerNode specific
+        accessors.
+
+        * accessibility/AccessibilityRenderObject.cpp:
+        (WebCore::AccessibilityRenderObject::addImageMapChildren):
+        * css/SelectorChecker.cpp:
+        (WebCore::linkAttribute):
+        (WebCore::SelectorChecker::allVisitedStateChanged):
+        (WebCore::SelectorChecker::visitedStateChanged):
+        * css/StyleInvalidationAnalysis.cpp:
+        (WebCore::elementMatchesSelectorScopes):
+        (WebCore::StyleInvalidationAnalysis::invalidateStyle):
+        * dom/ContainerNodeAlgorithms.h:
+        (WebCore::ChildFrameDisconnector::collectDescendant):
+        * dom/Document.cpp:
+        (WebCore::Document::buildAccessKeyMap):
+        (WebCore::Document::updateBaseURL):
+        (WebCore::Document::processBaseElement):
+        * dom/DocumentOrderedMap.cpp:
+        (WebCore::DocumentOrderedMap::get):
+        * dom/Element.cpp:
+        (WebCore::Element::firstElementChild):
+        * dom/Element.h:
+        (WebCore):
+        * dom/ElementShadow.cpp:
+        (WebCore::ElementShadow::collectSelectFeatureSetFrom):
+        * dom/NodeTraversal.h:
+        (ElementTraversal):
+        (WebCore):
+        (WebCore::ElementTraversal::traverseNextElementTemplate):
+        (WebCore::ElementTraversal::next):
+        (WebCore::ElementTraversal::firstWithin):
+        (WebCore::ElementTraversal::traverseNextElementSkippingChildrenTemplate):
+        (WebCore::ElementTraversal::nextSkippingChildren):
+        (NodeTraversal):
+        * dom/TreeScope.cpp:
+        (WebCore::TreeScope::labelElementForId):
+        (WebCore::TreeScope::findAnchor):
+        * editing/CompositeEditCommand.cpp:
+        (WebCore::CompositeEditCommand::cloneParagraphUnderNewElement):
+        * editing/DeleteSelectionCommand.cpp:
+        (WebCore::DeleteSelectionCommand::handleGeneralDelete):
+        * editing/FrameSelection.cpp:
+        (WebCore::scanForForm):
+        * editing/markup.cpp:
+        (WebCore::completeURLs):
+        * html/HTMLFieldSetElement.cpp:
+        (WebCore::HTMLFieldSetElement::invalidateDisabledStateUnder):
+        (WebCore::HTMLFieldSetElement::childrenChanged):
+        (WebCore::HTMLFieldSetElement::legend):
+        (WebCore::HTMLFieldSetElement::refreshElementsIfNeeded):
+        * html/HTMLFormElement.cpp:
+        (WebCore::HTMLFormElement::formElementIndex):
+        * html/HTMLLabelElement.cpp:
+        (WebCore::HTMLLabelElement::control):
+        * html/HTMLLegendElement.cpp:
+        (WebCore::HTMLLegendElement::associatedControl):
+        * html/HTMLMapElement.cpp:
+        (WebCore::HTMLMapElement::mapMouseEvent):
+        * html/HTMLNameCollection.cpp:
+        (WebCore::HTMLNameCollection::virtualItemAfter):
+        * html/HTMLObjectElement.cpp:
+        (WebCore::HTMLObjectElement::containsJavaApplet):
+        * html/HTMLSelectElement.cpp:
+        (WebCore::HTMLSelectElement::recalcListItems):
+        * html/shadow/ContentDistributor.cpp:
+        (WebCore::ShadowRootContentDistributionData::ensureInsertionPointList):
+        * page/FocusController.cpp:
+        (WebCore::FocusController::findFocusCandidateInContainer):
+        * rendering/RenderCounter.cpp:
+        (WebCore::nextInPreOrder):
+        * svg/SVGSVGElement.cpp:
+        (WebCore::SVGSVGElement::collectIntersectionOrEnclosureList):
+        * svg/SVGStyledElement.cpp:
+        (WebCore::SVGStyledElement::title):
+        * svg/SVGUseElement.cpp:
+        (WebCore::removeDisallowedElementsFromSubtree):
+        * svg/animation/SMILTimeContainer.cpp:
+        (WebCore::SMILTimeContainer::updateDocumentOrderIndexes):
+
+2012-12-11  KyungTae Kim  <ktf.kim@samsung.com>
+
+        [soup] Unused parameter in ResourceHandleSoup.cpp
+        https://bugs.webkit.org/show_bug.cgi?id=104728
+
+        Reviewed by Kentaro Hara.
+
+        The soupLogPrinter has unused parameter 'logger', 
+        remove the parameter name to fix 'unused parameter' build warning.
+
+        * platform/network/soup/ResourceHandleSoup.cpp:
+        (WebCore::soupLogPrinter):
+
+2012-12-11  Xianzhu Wang  <wangxianzhu@chromium.org>
+
+        Fixed position out-of-view check is incorrect when page is scaled
+        https://bugs.webkit.org/show_bug.cgi?id=104303
+
+        Reviewed by Kenneth Rohde Christiansen.
+
+        Test: compositing/layer-creation/fixed-position-out-of-view-scaled.html
+              compositing/layer-creation/fixed-position-out-of-view-scaled-scroll.html
+
+        * rendering/RenderLayerCompositor.cpp:
+        (WebCore::RenderLayerCompositor::requiresCompositingForPosition): Scale the content rect of the fixed position layer before checking out-of-view.
+
+2012-12-11  Chris Rogers  <crogers@google.com>
+
+        Implement OfflineAudioContext constructor
+        https://bugs.webkit.org/show_bug.cgi?id=104188
+
+        Reviewed by Kentaro Hara.
+
+        The Web Audio layout tests have relied on an undocumented way (in the specification) to render
+        audio faster than realtime using an OfflineAudioContext.  We want to expose a proper OfflineAudioContext
+        object and constructor instead of piggybacking off of the normal AudioContext.
+            
+        * CMakeLists.txt:
+        * DerivedSources.make:
+        * DerivedSources.pri:
+        * GNUmakefile.list.am:
+        * Modules/webaudio/AudioContext.cpp:
+        (WebCore::AudioContext::isSampleRateRangeGood):
+        * Modules/webaudio/AudioContext.h:
+        (AudioContext):
+        * Modules/webaudio/DOMWindowWebAudio.idl:
+        * Modules/webaudio/OfflineAudioContext.cpp: Added.
+        (WebCore):
+        (WebCore::OfflineAudioContext::create):
+        (WebCore::OfflineAudioContext::OfflineAudioContext):
+        (WebCore::OfflineAudioContext::~OfflineAudioContext):
+        * Modules/webaudio/OfflineAudioContext.h: Added.
+        (WebCore):
+        (OfflineAudioContext):
+        * Modules/webaudio/OfflineAudioContext.idl: Added.
+        * WebCore.gypi:
+        * WebCore.xcodeproj/project.pbxproj:
+        * bindings/generic/RuntimeEnabledFeatures.h:
+        (WebCore::RuntimeEnabledFeatures::webkitOfflineAudioContextEnabled):
+        * bindings/js/JSAudioContextCustom.cpp:
+        (WebCore::JSAudioContextConstructor::constructJSAudioContext):
+        * bindings/v8/custom/V8AudioContextCustom.cpp:
+        (WebCore::V8AudioContext::constructorCallbackCustom):
+
+2012-12-11  Jun Jiang  <jun.a.jiang@intel.com>
+
+        WebGL: Avoid unnecessary memory copy or conversion in texImage2D and texSubImage2D for HTMLVideoElement
+        https://bugs.webkit.org/show_bug.cgi?id=102161
+
+        Reviewed by Kenneth Russell.
+
+        There are several memory copy or conversions in the texImage2D and texSubImage2D for HTMLVideoElement which may be avoided. This patch removes the redundant BackingStore copy if the corresponding Graphics port supports the DontCopyBackingStore behavior. Moreover, it optimizes the AlphaOp if the Image source is from HTMLVideoElement to avoid unnecessary Unmultiply or Premultiply operation in unpack/pack. 
+
+        Already covered by current tests. 
+
+        * html/canvas/WebGLRenderingContext.cpp:
+        (WebCore):
+        (WebCore::WebGLRenderingContext::texImage2DImpl):
+        (WebCore::WebGLRenderingContext::texImage2D):
+        (WebCore::WebGLRenderingContext::videoFrameToImage): add a parameter to choose BackingStore copy behavior.
+        (WebCore::WebGLRenderingContext::texSubImage2DImpl):
+        (WebCore::WebGLRenderingContext::texSubImage2D):
+        * html/canvas/WebGLRenderingContext.h:
+        (WebGLRenderingContext):
+        * platform/graphics/GraphicsContext3D.cpp:
+        (WebCore::GraphicsContext3D::ImageExtractor::ImageExtractor):
+        * platform/graphics/GraphicsContext3D.h:
+        (ImageExtractor):
+        (WebCore::GraphicsContext3D::ImageExtractor::imageSourceUnpackAlignment):
+        (WebCore::GraphicsContext3D::ImageExtractor::imageHtmlDomSource):
+        * platform/graphics/ImageBuffer.h:
+        (ImageBuffer):
+        * platform/graphics/cairo/GraphicsContext3DCairo.cpp:
+        (WebCore::GraphicsContext3D::ImageExtractor::extractImage): optimize the AlphaOp for HTMLVideoElement input.
+        * platform/graphics/cairo/ImageBufferCairo.cpp:
+        (WebCore::ImageBuffer::fastCopyImageMode):
+        (WebCore):
+        * platform/graphics/cg/ImageBufferCG.cpp:
+        (WebCore::ImageBuffer::fastCopyImageMode):
+        (WebCore):
+        * platform/graphics/qt/ImageBufferQt.cpp:
+        (WebCore::ImageBuffer::fastCopyImageMode):
+        (WebCore):
+        * platform/graphics/skia/GraphicsContext3DSkia.cpp:
+        (WebCore::GraphicsContext3D::ImageExtractor::extractImage): optimize the AlphaOp for HTMLVideoElement input.
+        * platform/graphics/skia/ImageBufferSkia.cpp:
+        (WebCore::ImageBuffer::fastCopyImageMode):
+        (WebCore):
+        * platform/graphics/wince/ImageBufferWinCE.cpp:
+        (WebCore::ImageBuffer::fastCopyImageMode):
+        (WebCore):
+        * platform/graphics/wx/ImageBufferWx.cpp:
+        (WebCore::ImageBuffer::fastCopyImageMode):
+        (WebCore):
+
+2012-12-11  Viatcheslav Ostapenko  <v.ostapenko@samsung.com>
+
+        [EFL] Missing implementation of GraphicsContext3DPrivate::platformLayerSize()
+        https://bugs.webkit.org/show_bug.cgi?id=104726
+
+        Reviewed by Kenneth Rohde Christiansen.
+
+        Add common implementation of GraphicsContext3DPrivate::platformLayerSize() similar
+        to Qt version. There is nothing platform specific in Qt version. 
+
+        Covered by existing tests.
+
+        * platform/graphics/efl/GraphicsContext3DPrivate.cpp:
+        (GraphicsContext3DPrivate::platformLayerSize):
+        * platform/graphics/efl/GraphicsContext3DPrivate.h:
+        (GraphicsContext3DPrivate):
+
+2012-12-11  No'am Rosenthal  <noam@webkit.org>
+
+        [Texmap] Slightly improve readability of the antialias shader
+        https://bugs.webkit.org/show_bug.cgi?id=104708
+
+        Reviewed by Martin Robinson.
+
+        Modify the antialiasing shader to include separate function that perform
+        discrete operations, rather than one big function that repeats the same
+        operations.
+
+        No new tests, readability fix.
+
+        * platform/graphics/texmap/TextureMapperShaderManager.cpp:
+        (WebCore::getShaderSpec):
+
+2012-12-11  Tim Horton  <timothy_horton@apple.com>
+
+        -webkit-svg-shadow radius changes don't cause children's boundaries to be recomputed
+        https://bugs.webkit.org/show_bug.cgi?id=104722
+        <rdar://problem/12821080>
+
+        Reviewed by Simon Fraser.
+
+        Changes to -webkit-svg-shadow currently cause a relayout of the directly affected renderer
+        and its parents, but not its children. However, children have the shadow radius
+        baked into their cached boundaries, so these need to be invalidated.
+
+        Test: svg/repaint/repaint-webkit-svg-shadow-container.html
+
+        * rendering/RenderObject.h: Expose needsBoundariesUpdate().
+        * rendering/svg/RenderSVGContainer.h: Expose needsBoundariesUpdate().
+        * rendering/svg/RenderSVGImage.h: Expose needsBoundariesUpdate().
+        * rendering/svg/RenderSVGRoot.h: Expose needsBoundariesUpdate().
+        * rendering/svg/RenderSVGShape.h: Expose needsBoundariesUpdate().
+        * rendering/svg/SVGRenderSupport.cpp:
+        (WebCore::SVGRenderSupport::layoutChildren): If the renderer has a shadow and
+        is in needs of a boundaries update, mark children as needing boundaries updates too.
+
+2012-12-11  Xianzhu Wang  <wangxianzhu@chromium.org>
+
+        Add window.internals.mainThreadScrollReasonsAsText for testing slow scrolling
+        https://bugs.webkit.org/show_bug.cgi?id=104714
+
+        Reviewed by Eric Seidel.
+
+        No new tests. Adds test api for bug 102543 and other bugs.
+
+        * WebCore.exp.in:
+        * page/Page.cpp:
+        (WebCore::ScrollingCoordinator::mainThreadScrollingReasonsAsText): Extracted from ScrollingStateScrollingNode::dumpProperties for layout tests.
+        (WebCore):
+        * page/Page.h:
+        (Page):
+        * page/scrolling/ScrollingCoordinator.cpp:
+        (WebCore::ScrollingCoordinator::mainThreadScrollingReasonsAsText):
+        (WebCore):
+        * page/scrolling/ScrollingCoordinator.h:
+        (ScrollingCoordinator):
+        * page/scrolling/ScrollingStateScrollingNode.cpp:
+        (WebCore::ScrollingStateScrollingNode::dumpProperties): Moved code for mainThreadScrollingReasons to ScrollingCoordinator.cpp.
+        * testing/Internals.cpp:
+        (WebCore::Internals::mainThreadScrollingReasons):
+        (WebCore):
+        * testing/Internals.h:
+        * testing/Internals.idl:
+
+2012-12-11  Simon Fraser  <simon.fraser@apple.com>
+
+        Enhance the TileCache to cache more tiles
+        https://bugs.webkit.org/show_bug.cgi?id=104612
+
+        Reviewed by Tim Horton.
+
+        Add smarts to the TileCache so that it keeps some tiles around
+        for longer and can prepopulate tiles in to-be-scrolled-to regions.
+
+        The new tile management is as follows:
+        * As before, we expand the visible rect to create a "tile coverage rect"
+        which is twice the width, and three times the height of the visible rect.
+        * At the edges, this coverage rect is constrained by them, rather than being
+        truncated as before (leading to larger initial tile coverage).
+        * When tiles leave the coverage rect, we keep them around but track
+        them in cohorts (where a cohort is a set of tiles that left the coverage rect
+        at the same time).
+        * If a repaint comes in for a "secondary" tile, we don't paint it, but mark
+        the tile as being stale. It will get repainted (in full) if it moves back inside
+        the coverage rect.
+        * Cohorts are kept around for 2 seconds after they were created. A repeating
+        1-second timer clears tiles in old cohorts.
+        * Secondary tiles are pruned if the visible rect changes, or if zooming happens.
+        * TiledBacking exposes a way to prepopulate a rect with tiles; this is called
+        when scrolling (e.g. via Home/End keys). Tiles created this way (if outside
+        the coverage rect) go into a cohort.
+
+        * page/FrameView.cpp:
+        (WebCore::FrameView::requestScrollPositionUpdate): Tell the TiledBacking
+        to prepopulate some tiles.
+        * platform/graphics/TiledBacking.h:
+        (TiledBacking): Add prepopulateRect().
+        * platform/graphics/ca/mac/TileCache.h:
+        (TileInfo): The TileMap contains TileInfos, which contain a pointer
+        to the layer, their cohort, and a 'stale content' flag.
+        (WebCore::TileCache::TileInfo::TileInfo):
+        (TileCache):
+        (TileCohortInfo):
+        (WebCore::TileCache::TileCohortInfo::TileCohortInfo):
+        * platform/graphics/ca/mac/TileCache.mm:
+        (WebCore::TileCache::TileCache):
+        (WebCore::TileCache::~TileCache):
+        (WebCore::TileCache::setNeedsDisplay):
+        (WebCore::TileCache::setNeedsDisplayInRect):
+        (WebCore::TileCache::setTileNeedsDisplayInRect):
+        (WebCore::TileCache::setScale):
+        (WebCore::TileCache::setAcceleratesDrawing):
+        (WebCore::TileCache::setTilesOpaque):
+        (WebCore::TileCache::prepopulateRect):
+        (WebCore::TileCache::setTileDebugBorderWidth):
+        (WebCore::TileCache::setTileDebugBorderColor):
+        (WebCore::TileCache::computeTileCoverageRect):
+        (WebCore::TileCache::tileSizeForCoverageRect):
+        (WebCore::TileCache::tileRevalidationTimerFired):
+        (WebCore::TileCache::blankPixelCount):
+        (WebCore::queueTileForRemoval):
+        (WebCore::TileCache::removeAllTiles):
+        (WebCore::TileCache::removeAllSecondaryTiles):
+        (WebCore::TileCache::removeTilesInCohort):
+        (WebCore::TileCache::revalidateTiles):
+        (WebCore::TileCache::nextTileCohort):
+        (WebCore::TileCache::startedNewCohort):
+        (WebCore::TileCache::newestTileCohort):
+        (WebCore::TileCache::oldestTileCohort):
+        (WebCore::TileCache::scheduleCohortRemoval):
+        (WebCore::TileCache::cohortRemovalTimerFired):
+        (WebCore::TileCache::ensureTilesForRect):
+        (WebCore::TileCache::tileGridExtent):
+        (WebCore::TileCache::tileCoverageRect):
+        (WebCore::TileCache::tileLayerAtIndex):
+        (WebCore::TileCache::drawTileMapContents):
+
+2012-12-11  Simon Fraser  <simon.fraser@apple.com>
+
+        Remove redundant AffineTransform in RenderSVGShape::fillAndStrokeShape()
+        https://bugs.webkit.org/show_bug.cgi?id=104736
+
+        Reviewed by Dean Jackson.
+
+        RenderSVGShape::fillAndStrokeShape() allocated a AffineTransform on
+        the stack which was shadowed by another one in narrower scope. It
+        can be removed.
+
+        * rendering/svg/RenderSVGShape.cpp:
+        (WebCore::RenderSVGShape::fillAndStrokeShape):
+
+2012-12-11  Seokju Kwon  <seokju.kwon@gmail.com>
+
+        [EFL] Remove unused headers
+        https://bugs.webkit.org/show_bug.cgi?id=104661
+
+        Reviewed by Ryosuke Niwa.
+
+        Header inclusion cleanup.
+        Remove "NotImplemented.h".
+
+        No new tests, no behavior change.
+
+        * platform/efl/CursorEfl.cpp:
+        * platform/efl/FileSystemEfl.cpp:
+        * platform/efl/ScrollViewEfl.cpp:
+        * platform/efl/ScrollbarThemeEfl.cpp:
+        * platform/efl/SoundEfl.cpp:
+
+2012-12-11  Alec Flett  <alecflett@chromium.org>
+
+        IndexedDB: Stub out data operations on IDBDatabaseBackendInterface
+        https://bugs.webkit.org/show_bug.cgi?id=104592
+
+        Reviewed by Dimitri Glazkov.
+
+        In preparation for removing objectStore/index backend
+        interfaces, stub out the basic data operations around
+        get, put, cursors, etc. on IDBDatabaseBackendInterface.
+
+        No new tests, this is just preparation for refactoring.
+
+        * Modules/indexeddb/IDBDatabaseBackendImpl.cpp:
+        (WebCore::IDBDatabaseBackendImpl::get):
+        (WebCore):
+        (WebCore::IDBDatabaseBackendImpl::put):
+        (WebCore::IDBDatabaseBackendImpl::setIndexKeys):
+        (WebCore::IDBDatabaseBackendImpl::setIndexesReady):
+        (WebCore::IDBDatabaseBackendImpl::openCursor):
+        (WebCore::IDBDatabaseBackendImpl::count):
+        (WebCore::IDBDatabaseBackendImpl::deleteRange):
+        (WebCore::IDBDatabaseBackendImpl::clear):
+        * Modules/indexeddb/IDBDatabaseBackendImpl.h:
+        (IDBDatabaseBackendImpl):
+        * Modules/indexeddb/IDBDatabaseBackendInterface.h:
+        (WebCore):
+        (IDBDatabaseBackendInterface):
+
+2012-12-11  Roger Fong  <roger_fong@apple.com>
+
+        Make Video Track compile on Windows in debug mode.
+        https://bugs.webkit.org/show_bug.cgi?id=104720.
+
+        Reviewed by Alexey Proskuryakov.
+
+        urlForLogging method was defined in both HTMLMediaElement.cpp and HTMLTrackElement.cpp. 
+        On Windows all the HTMLElements sources are included in an AllInOne source file, 
+        so the definitions conflicted. Fixed by renaming the definition in each source file.
+
+        * html/HTMLMediaElement.cpp:
+        (WebCore::urlForLoggingMedia):
+        (WebCore::HTMLMediaElement::loadResource):
+        (WebCore::HTMLMediaElement::isSafeToLoadURL):
+        (WebCore::HTMLMediaElement::didRemoveTrack):
+        (WebCore::HTMLMediaElement::selectNextSourceChild):
+        (WebCore::HTMLMediaElement::sourceWasAdded):
+        (WebCore::HTMLMediaElement::sourceWasRemoved):
+        * html/HTMLTrackElement.cpp:
+        (WebCore::urlForLoggingTrack):
+        (WebCore::HTMLTrackElement::canLoadUrl):
+
+2012-12-11  Ryosuke Niwa  <rniwa@webkit.org>
+
+        Mail hangs when resizing the font size of a large RTL text
+        https://bugs.webkit.org/show_bug.cgi?id=104643
+
+        Reviewed by Enrica Casucci.
+
+        The bug was caused by ApplyStyleCommand::applyInlineStyleToNodeRange obtaining computed styles while
+        removing and adding nodes. Fixed the slowness by breaking it into three phases:
+        1. Split the range into contiguous inline runs, and determine whether styles need to be removed or applied.
+        2. Remove any conflicting styles, and insert dummy elements at positions where inline styles ought to be
+        computed as needed.
+        3. Remove the dummy elements and apply ilnine styles as needed.
+
+        No new tests are added since there is no behavior change. This is just a performance improvement. 
+
+        * editing/ApplyStyleCommand.cpp:
+        (WebCore::InlineRunToApplyStyle::InlineRunToApplyStyle):
+        (WebCore::InlineRunToApplyStyle::startAndEndAreStillInDocument):
+        (WebCore::ApplyStyleCommand::applyInlineStyleToNodeRange):
+        (WebCore::ApplyStyleCommand::shouldApplyInlineStyleToRun):
+        (WebCore::ApplyStyleCommand::removeConflictingInlineStyleFromRun):
+        (WebCore::ApplyStyleCommand::addInlineStyleIfNeeded):
+        (WebCore::ApplyStyleCommand::positionToComputeInlineStyleChange):
+        (WebCore::ApplyStyleCommand::applyInlineStyleChange):
+        * editing/ApplyStyleCommand.h:
+        * editing/EditingStyle.h:
+        (WebCore::StyleChange::StyleChange):
+
+2012-12-11  Xianzhu Wang  <wangxianzhu@chromium.org>
+
+        Incorrect position of layers for fixed position elements when page is scaled smaller than viewport
+        https://bugs.webkit.org/show_bug.cgi?id=104294
+
+        Reviewed by James Robinson.
+
+        Fixed issue in scrollOffsetForFixedPosition when contentRect is smaller than visibleContentRect.
+        This happens when a page originally bigger than viewport is scaled down to smaller than the viewport.
+
+        Test: compositing/geometry/fixed-position-composited-page-scale-smaller-than-viewport.html
+
+        * page/scrolling/ScrollingCoordinator.cpp:
+        (WebCore::fixedPositionScrollOffset): Moved common code in scrollOffsetForFixedPosition here. Fixed issue when contentsSize < visibleContentSize.
+        (WebCore::scrollOffsetForFixedPosition):
+
+2012-12-11  Beth Dakin  <bdakin@apple.com>
+
+        https://bugs.webkit.org/show_bug.cgi?id=104725
+        Crash in EventHandler::selectCursor() on Mac bots running 
+        fast/events/mouse-cursor-image-set.html
+
+        Reviewed by Tim Horton.
+
+        https://bugs.webkit.org/show_bug.cgi?id=99493 enabled image-set for 
+        the CSS cursor property. Most of the change is guarded behind #if 
+        ENABLE(MOUSE_CURSOR_SCALE). However, image-set was still allowed to 
+        parse for the cursor property as long as image-set is enabled 
+        (which is the current state on the Mac). This would lead to an 
+        inconsistent state where style information would reflect a world 
+        where mouse cursor scaling is enabled even though nothing else on 
+        the Mac would. 
+
+        The parsing should also be guarded by the cursor scaling flag.
+        * css/CSSParser.cpp:
+        (WebCore::CSSParser::parseValue):
+
+2012-12-11  Emil A Eklund  <eae@chromium.org>
+
+        Clamp out-of-range numbers in CSS
+        https://bugs.webkit.org/show_bug.cgi?id=102735
+
+        Reviewed by Simon Fraser.
+
+        Currently when a large number (outside of the supported range)
+        is applied from a style rule or set from javascript using
+        Element.style we check if it is within the supported range and
+        set it to zero if it is not. This is incorrect and confusing.
+        
+        Change it to clamp values to the supported range. This matches
+        the behavior in Gecko.
+
+        Test: fast/css/large-numbers.html
+
+        * css/CSSPrimitiveValue.cpp:
+        (WebCore::CSSPrimitiveValue::computeLength):
+        Change to clamp out-of-range values instead of interpreting them
+        as zero.
+
+2012-12-11  Nate Chapin  <japhet@chromium.org>
+
+        Ensure ResourceRequests for main resources include fragment indentifiers when necessary,
+        regressed by r137333.
+        https://bugs.webkit.org/show_bug.cgi?id=104721
+
+        Rubber-stamped by Dimitri Glazkov.
+
+        No new tests.
+
+        * loader/SubresourceLoader.cpp:
+        (WebCore::SubresourceLoader::willSendRequest):
+
+2012-12-11  Huang Dongsung  <luxtella@company100.net>
+
+        [GTK] REGRESSION(r135620): Accelerated Compositing does not draw some pages.
+        https://bugs.webkit.org/show_bug.cgi?id=104640
+
+        Reviewed by Noam Rosenthal.
+
+        After r135620, Accelerated Compositing does not draw some pages, because
+        r135620 changes the tree-traversal behavior.  Before r135620, we
+        returned early if TextureMapperLayer can not get TextureMapper from the
+        root layer. However, after r135620, we run the tree-traversal even if
+        TextureMapperLayer can not get TextureMapper.  This patch makes
+        TextureMapperLayer return early like code before r135620.
+
+        Covered by existing tests.
+
+        * platform/graphics/texmap/GraphicsLayerTextureMapper.cpp:
+        (WebCore::GraphicsLayerTextureMapper::flushCompositingState):
+
+2012-12-11  Dan Bernstein  <mitz@apple.com>
+
+        <rdar://problem/12771885> Support ruby-position: {before, after}
+        https://bugs.webkit.org/show_bug.cgi?id=103569
+
+        Reviewed by Anders Carlsson.
+
+        Specified in <http://www.w3.org/TR/2011/WD-css3-ruby-20110630/#rubypos>, the ruby-position
+        property takes four values: before, after, inter-character, and inline. This change adds
+        support for the values before and after.
+
+        Test: fast/ruby/position-after.html
+
+        * css/CSSComputedStyleDeclaration.cpp:
+        (WebCore::CSSComputedStyleDeclaration::getPropertyCSSValue): Handle ruby-position.
+        * css/CSSParser.cpp:
+        (WebCore::isValidKeywordPropertyAndValue): Accept before and after as valid values for
+        ruby-position.
+        (WebCore::isKeywordPropertyID): Added ruby-position to the list of properties with keyword
+        values.
+        (WebCore::CSSParser::parseValue): Added ruby-position to the switch statement.
+        * css/CSSPrimitiveValueMappings.h:
+        (WebCore::CSSPrimitiveValue::CSSPrimitiveValue): Added mapping from RubyPosition.
+        (WebCore::CSSPrimitiveValue::operator RubyPosition): Added mapping from CSSPrimitiveValue.
+        * css/CSSProperty.cpp:
+        (WebCore::CSSProperty::isInheritedProperty): Added ruby-position as an inherited property.
+        * css/CSSPropertyNames.in: Added -webkit-ruby-position.
+        * css/CSSValueKeywords.in: Added after and before.
+        * css/StyleBuilder.cpp:
+        (WebCore::StyleBuilder::StyleBuilder): Added a handler for ruby-position.
+        * css/StyleResolver.cpp:
+        (WebCore::StyleResolver::applyProperty): Added ruby-position.
+        * rendering/InlineFlowBox.cpp:
+        (WebCore::InlineFlowBox::placeBoxesInBlockDirection): Changed to choose which of
+        hasAnnotationsBefore and hasAnnotationsAfter to set based on ruby position.
+        (WebCore::InlineFlowBox::computeOverAnnotationAdjustment): Changed to adjust only for
+        ruby positioned before the base.
+        (WebCore::InlineFlowBox::computeUnderAnnotationAdjustment): Added adjustment for ruby
+        positioned after the base.
+        * rendering/RenderRubyRun.cpp:
+        (WebCore::RenderRubyRun::layout): Account for ruby-position when positioning the ruby text
+        relative to the base.
+        * rendering/style/RenderStyle.cpp:
+        (WebCore::RenderStyle::diff): Made a ruby-position difference a layout difference.
+        * rendering/style/RenderStyle.h: Added rubyPosition(), setRubyPosition(), and 
+        initialRubyPosition().
+        * rendering/style/RenderStyleConstants.h: Added the RubyPosition enum.
+        * rendering/style/StyleRareInheritedData.cpp:
+        (WebCore::StyleRareInheritedData::StyleRareInheritedData): Added initialized for
+        m_rubyPosition. Added copying the value of this member to the copy constructor.
+        (WebCore::StyleRareInheritedData::operator==): Added comparison of m_rubyPosition.
+        * rendering/style/StyleRareInheritedData.h:
+        (StyleRareInheritedData): Added m_rubyPosition member variable.
+
+2012-12-11  Michael Pruett  <michael@68k.org>
+
+        [JSC] Add tests for explicit serialization values
+        https://bugs.webkit.org/show_bug.cgi?id=104423
+
+        Reviewed by Oliver Hunt.
+
+        Add tests for serialization and deserialization mechanisms of
+        the JSC implementation of SerializedScriptValue. Similar tests
+        already exist for the V8 implementation.
+
+        Test: platform/jsc/fast/storage/serialized-script-value.html
+
+        * WebCore.exp.in:
+        * testing/Internals.cpp:
+        (WebCore::Internals::serializeObject):
+        (WebCore::Internals::deserializeBuffer):
+
 2012-12-11  Alexis Menard  <alexis@webkit.org>
 
         Cleanup: Use consistent naming in CSSParser when dealing with the forward slash operator.