Remove comment about issue 368416

Since the issue was opened, the validity of removing
RenderObject::positionFromPaintInvalidationContainer
was questioned and it was determined that it's
probably not such a good idea anyway.

BUG=368416

Review URL: https://codereview.chromium.org/423943002

git-svn-id: svn://svn.chromium.org/blink/trunk@179078 bbb929c8-8fbe-4397-9dbb-9b2b20218538

third_party/WebKit/Source/core/rendering/RenderObject.cpp

@@ -1318,7 +1318,6 @@ void RenderObject::addChildFocusRingRects(Vector<IntRect>& rects, const LayoutPo
     }
 }
 
-// FIXME: In repaint-after-layout, we should be able to change the logic to remove the need for this function. See crbug.com/368416.
 LayoutPoint RenderObject::positionFromPaintInvalidationContainer(const RenderLayerModelObject* paintInvalidationContainer, const PaintInvalidationState* paintInvalidationState) const
 {
     // FIXME: This assert should be re-enabled when we move paint invalidation to after compositing update. crbug.com/360286