Rendering the property, text-align-last.

Specification link : http://www.w3.org/TR/css3-text/#text-align-last-property

BUG=248839

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161122 bbb929c8-8fbe-4397-9dbb-9b2b20218538
RenderTableCol should inherit from RenderObject instead of RenderBox

This patch makes RenderTableCol inherit from RenderObject instead of RenderBox,
since RenderTableCol is purely metadata. A bunch of layout test needs to be
rebaselined because RenderTableCol no longer dumps its border attributes.

Also widthAttr is no longer processed in HTMLTableColElement::parseAttribute,
since it will be plugged to style sheet as a presentation attribute. This
eliminates dependency to layout results.

No new tests. Shouldn't change behavior.

R=jchaffraix@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161123 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename 'callbackInfo' to 'info' in V8 custom bindings

This is for naming consistency with other places.
We use 'info' for PropertyCallbackInfo and FunctionCallbackInfo.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161124 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove rendering dependency in GraphicsContextAnnotation

BUG=297477

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161125 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Re-land deferred compositing updates with fixed assumptions

Deferred compositing updates originally landed in r159961.
It was reverted in r160106 because of debug assertions in
touch-event scrollingcoordinator code.

The problem was that ScrollingCoordinator touch event handling
was still assuming that compositing state is correctly updated
immediately after layout and style recalculations. This is not
true when compositing updates are deferred.  This patch re-lands
deferred compositing with the correct ScrollingCoordinator
changes.

Additionally in the time that this patch was reverted, the
inspector has changed to support asynchronous compositing
updates. This patch also fixes some logic in that new code
(removing the timeout mechanism) so that it works seamlessly
with deferred compositing updates.

BUG=229679, 302726, 309733

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161126 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Don't leave stale pointer into m_grid

This change fixes several stale pointers issue in our code:
- We would wrongly add boxes wrapped in anonymous wrappers to
m_grid, which would never be removed.
- RenderBlock::removeLeftoverAnonymousBlock would remove some
anonymous wrappers under RenderGrid without notifying it of
the hierarchy change (yay!).

To fix the second issue, I took the more conservative approach
of notifying RenderGrid of any child's death and not clearing
parent in removeLeftoverAnonymousBlock.

BUG=313293

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161127 bbb929c8-8fbe-4397-9dbb-9b2b20218538
IDL compiler: Rename 'args' to 'info', remove |callback_info| and |isolate| as possible

Python side to 'args' => 'info' CL.
This also allows significant simplification, since now |callback_info|
is always 'info', and |isolate| is almost always 'info.GetIsolate()'.

2 questions:
1. Should assume |isolate| == 'info.GetIsolate()' in V8_VALUE_TO_CPP_VALUE?
In CPP_VALUE_TO_V8_VALUE, we need to have an {isolate} parameter b/c
callback interfaces have |isolate| == 'isolate' instead,
but for attributes and methods (which are all that use V8 -> C++ for)
this assumption is true.

2. Style-wise, we could:
a. use {isolate} in string templates and pass isolate='info.GetIsolate()'
(which might be clearer),
b. inline 'info.GetIsolate()' (to be explicit), which is what I've done now.

Ref:
Rename |args| to |info| in V8 bindings
https://codereview.chromium.org/54283002/

BUG=239771
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@161128 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove friendship from RenderLayerScrollableArea

It's time to strenghen the API between RenderLayer
and RenderLayerScrollableArea. This is the easy
friendship to break.

BUG=260899

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

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