Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(146)

Unified Diff: LayoutTests/fast/events/touch/touch-action-double-remove.html

Issue 899163003: Move rendering/RenderObject to layout/LayoutObject. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 5 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: LayoutTests/fast/events/touch/touch-action-double-remove.html
diff --git a/LayoutTests/fast/events/touch/touch-action-double-remove.html b/LayoutTests/fast/events/touch/touch-action-double-remove.html
index 3a7db617a4a11b8035af31ec9413261992c9bbaf..b13fc3051810fecc3637d0bf16ca3149d7c41374 100644
--- a/LayoutTests/fast/events/touch/touch-action-double-remove.html
+++ b/LayoutTests/fast/events/touch/touch-action-double-remove.html
@@ -7,11 +7,11 @@ br {
<!--
This is a regression test against a double unregistration of a touch action
event handler on a <br> element. When the document finishes loading and is
-attached to the view, all of its RenderObjects are destroyed and recreated. If
-a RenderObject had a touch action associated with it, it will need to remove
+attached to the view, all of its LayoutObjects are destroyed and recreated. If
+a LayoutObject had a touch action associated with it, it will need to remove
the fake event handler it registered for it in the EventHandlerRegistry.
However, when the document gets detached, all of the event handlers within it
-are automatically unregistered. When the RenderObject tries to unregister its
+are automatically unregistered. When the LayoutObject tries to unregister its
own handler after the fact, it is no longer there and we hit an assertion
failure.

Powered by Google App Engine
This is Rietveld 408576698