Bug 134092 – Introduce RenderLayer::offsetFromAncestorLayer() to make convertToLayerCoords() calls with LayoutPoint(0, 0) as parameter more explicit.

• Component: Layout and Rendering
• Status: RESOLVED FIXED

[zalan]

Most of the RenderLayer::convertToLayerCoords() callers are just interested in getting the offset from the ancestor layer. Introducing offsetFromAncestorLayer() makes those calls more explicit/self-explanatory -> callsite's code can be simplified.

[zalan]

Created attachment 233407 [details]
Patch

[Simon Fraser (smfr)]

Comment on attachment 233407 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=233407&action=review

> Source/WebCore/rendering/RenderGeometryMap.cpp:-190
> -//    fprintf(stderr, "RenderGeometryMap::pushMappingsToAncestor from layer %p to layer %p, canConvertInLayerTree=%d\n", layer, ancestorLayer, canConvertInLayerTree);

Lots of commented printfs in this patch.

> Source/WebCore/rendering/RenderLayer.cpp:2026
> +LayoutPoint RenderLayer::offsetFromAncestorLayer(const RenderLayer* ancestorLayer) const

I think you could call this offsetFromAncestor. Would it make sense to return a LayoutSize?

[zalan]

(In reply to comment #2)
> (From update of attachment 233407 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=233407&action=review
> 
> > Source/WebCore/rendering/RenderGeometryMap.cpp:-190
> > -//    fprintf(stderr, "RenderGeometryMap::pushMappingsToAncestor from layer %p to layer %p, canConvertInLayerTree=%d\n", layer, ancestorLayer, canConvertInLayerTree);
> 
> Lots of commented printfs in this patch.
You want me to keep them in? :)

> 
> > Source/WebCore/rendering/RenderLayer.cpp:2026
> > +LayoutPoint RenderLayer::offsetFromAncestorLayer(const RenderLayer* ancestorLayer) const
> 
> I think you could call this offsetFromAncestor. Would it make sense to return a LayoutSize?
Indeed!

[zalan]

Committed r170220: <http://trac.webkit.org/changeset/170220>