Upgrade parser-created Custom Elements in creation order.

Originally, parser-created Custom Elements were upgraded in reverse
order (which quickly and dirtily ensured that an element's children
were upgraded before the element itself.) Then we rethought this and
upgraded them post-order (which meant an element's children were still
upgraded before the element itself, but siblings were upgraded in
order.)

Now parser-created Custom Elements are upgraded in creation order (ie
pre-order.) This is consistent with how Custom Elements are upgraded
when cloning a subtree of nodes.

This is described here:
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=23778>

BUG=234509

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

git-svn-id: svn://svn.chromium.org/blink/trunk@162229 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make generation IDs of animated GIF and webp frames unique.

Re-landing https://codereview.chromium.org/65713004/

In some cases GIFImageDecoder::initFrameBuffer/WEBImageDecoder::initFrameBuffer
copy the content of the previous frame as the starting state for the current
frame. The generation ID of the two bitmaps is identical after that copy. We
need to call SkBitmap::notifyPixelsChanged to make sure that the new frame
gets a unique generation ID.

R=hclam@chromium.org,reveman@chromium.org,reed@chromium.org,enne@chromium.org,zmo@chromium.org
BUG=307689

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

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

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

BUG=319541
TBR=senorblanco@chromium.org

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

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