Implement a PageTransitionEvent constructor for JSC
[WebKit-https.git] / Source / WebCore / ChangeLog
index 07702c7..e6fd871 100644 (file)
@@ -1,3 +1,74 @@
+2011-09-14  Kentaro Hara  <haraken@google.com>
+
+        Implement a PageTransitionEvent constructor for JSC
+        https://bugs.webkit.org/show_bug.cgi?id=68048
+
+        Reviewed by Sam Weinig.
+
+        The spec for the PageTransitionEvent constructor is here:
+        http://www.whatwg.org/specs/web-apps/current-work/#pagetransitionevent
+
+        Test: fast/events/constructors/page-transition-event-constructor.html
+
+        * bindings/generic/EventConstructors.h: Added a definition for the PageTransitionEvent constructor.
+        * bindings/js/JSEventConstructors.cpp: Added #includes for PageTransitionEvent.
+        * dom/PageTransitionEvent.cpp:
+        (WebCore::PageTransitionEventInit::PageTransitionEventInit):
+        (WebCore::PageTransitionEvent::PageTransitionEvent):
+        (WebCore::PageTransitionEvent::initPageTransitionEvent):
+        * dom/PageTransitionEvent.h: Added a definition for PageTransitionEventInit.
+        (WebCore::PageTransitionEvent::create):
+        (WebCore::PageTransitionEvent::isPageTransitionEvent):
+        (WebCore::PageTransitionEvent::persisted):
+        * dom/PageTransitionEvent.idl: Makes PageTransitionEvent constructible.
+
+2011-09-13  Sheriff Bot  <webkit.review.bot@gmail.com>
+
+        Unreviewed, rolling out r95058.
+        http://trac.webkit.org/changeset/95058
+        https://bugs.webkit.org/show_bug.cgi?id=68058
+
+        It made css3/calc/regression-62276.html crash (Requested by
+        Ossy on #webkit).
+
+        * css/CSSParser.cpp:
+        (WebCore::BorderImageParseContext::BorderImageParseContext):
+        (WebCore::BorderImageParseContext::allowBreak):
+        (WebCore::BorderImageParseContext::allowWidth):
+        (WebCore::BorderImageParseContext::allowOutset):
+        (WebCore::BorderImageParseContext::allowRepeat):
+        (WebCore::BorderImageParseContext::commitImage):
+        (WebCore::BorderImageParseContext::commitImageSlice):
+        (WebCore::BorderImageParseContext::commitSlash):
+        (WebCore::BorderImageParseContext::commitBorderWidth):
+        (WebCore::BorderImageParseContext::commitBorderOutset):
+        (WebCore::BorderImageParseContext::commitRepeat):
+        (WebCore::CSSParser::parseBorderImage):
+        (WebCore::CSSParser::parseBorderImageRepeat):
+        (WebCore::CSSParser::parseBorderImageSlice):
+        (WebCore::CSSParser::parseBorderImageQuad):
+        * css/CSSParserValues.h:
+
+2011-09-13  Abhishek Arya  <inferno@chromium.org>
+
+        Crash in RenderScrollbarPart::imageChanged.
+        https://bugs.webkit.org/show_bug.cgi?id=68009
+
+        Reviewed by Simon Fraser.
+
+        When a custom scrollbar is removed from its FrameView, its destruction
+        can be delayed because of RefPtr maintained in EventHandler class
+        (m_lastScrollbarUnderMouse). Upon removal, we delete all the scrollbar
+        parts so that they don't link back to scrollbar. However, because of the
+        delay, we can have a call to updateScrollbarPart which recreates it.
+        When scrollbar is getting destroyed, we just check to see if there are
+        remaining scrollbar parts and if yes, we destroy them.
+
+        Test: scrollbars/scrollbar-part-created-with-no-parent-crash.html
+
+        * rendering/RenderScrollbar.cpp:
+        (WebCore::RenderScrollbar::~RenderScrollbar):
+
 2011-09-13  Adam Klein  <adamk@chromium.org>
 
         Fix cssText property of counter-valued CSSPrimitiveValue and avoid uninitialized read