If the first load in a Page is a history load, ensure we use the main frame

Currently, it is possible that we will get confused between "The desired frame
doesn't exist in the current history entry" and "There is no current history
entry because we are in a new Page". In the later case, if the history load
includes an about:blank child item, we might accidentally load that into the
main frame instead.

BUG=332377
TEST=WebFrameTest.firstNavigationIsHistoryWithBlankChild

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165201 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Auto-rebaseline for r165189

http://src.chromium.org/viewvc/blink?view=revision&revision=165189

BUG=248894
TBR=dw.im@samsung.com

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

git-svn-id: svn://svn.chromium.org/blink/trunk@165202 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Avoiding multiple text/string parsing while creating TextRun. When TextRun is created we parse Text String but we are not storing CodePath. In InlineTextBox check was missing for Simple Code Path due to which multiple calls were made to "CodePath" to get code path for current text. Plus when
Run is made with complete string we can store CodePath and use the same.

Bug=330502

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

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