Fix render tree construction when inlines are inserted in reverse after a block in a continuation

Fix render tree construction when inlines are inserted in reverse after a block in a continuation

When inserting inlines after a block inside of an inline continuation, if we insert inline
content in reverse DOM order, we can (depending on when we attach) end up appending the renderers
in the wrong location, leading to visual aberrations. Since Blink r158839, we always attach in
reverse DOM order, which makes this bug easier to run into.

The fix is in RenderInline, where we should always attach behind our beforeChild if we're
inserting an inline and beforeChild is an inline, regardless of other continuation state.

Big thanks to Elliott for the test case!

BUG=318805
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=162160

[eae, 2013-11-16 01:45:37]

LGTM

https://codereview.chromium.org/68013006/diff/1/LayoutTests/fast/inline/conti...
File
LayoutTests/fast/inline/continuation-inlines-inserted-in-reverse-after-block.html
(right):

https://codereview.chromium.org/68013006/diff/1/LayoutTests/fast/inline/conti...
LayoutTests/fast/inline/continuation-inlines-inserted-in-reverse-after-block.html:10:
var last = null;
var last; will do, variables are undefined by default in js.

[esprehn, 2013-11-16 03:19:58]

lgtm, awesome

[commit-bot: I haz the power, 2013-11-16 22:00:16]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/leviw@chromium.org/68013006/60001

[commit-bot: I haz the power, 2013-11-16 23:20:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/leviw@chromium.org/68013006/170001

[commit-bot: I haz the power, 2013-11-17 01:15:38]

Change committed as 162160