Correctly update size when a plugin has a transform.

Correctly update size when a plugin has a transform.

When RenderWidget::updateWidgetGeometry is called, we were using the
absolute content box to set the geometry. This means if a
non-translation transform were sent, this would be expanded,
and the widget would scale up.

BUG=254805
R=vollick@chromium.org

[ojan, 2014-05-21 18:48:30]

This needs a test.

Also, I'm not familiar with the history of this function, why do we ever use the
absolute box?

[awoloszyn, 2014-05-21 19:01:18]

Sorry I had not meant to put this up for review until I had a test done. As for
the reason for the absolute box, it was done in 75915 (2011), to deal with
transforms, and then we specifically undid it for FrameViews, because we had an
identical problem to what we are still having with plugincontainers.

On 2014/05/21 18:48:30, ojan wrote:
> This needs a test.
> 
> Also, I'm not familiar with the history of this function, why do we ever use
the
> absolute box?

[MarkDodsworth, 2014-12-28 21:25:47]

On 2014/05/21 19:01:18, awoloszyn wrote:
> Sorry I had not meant to put this up for review until I had a test done. As
for
> the reason for the absolute box, it was done in 75915 (2011), to deal with
> transforms, and then we specifically undid it for FrameViews, because we had
an
> identical problem to what we are still having with plugincontainers.
> 
> On 2014/05/21 18:48:30, ojan wrote:
> > This needs a test.
> > 
> > Also, I'm not familiar with the history of this function, why do we ever use
> the
> > absolute box?

Any resolution for this yet? Waiting on a fix:
http://sourceforge.net/p/vbam/patches/48/