Squashed commit of the following:
Squashed commit of the following:

commit d3843d7780093abec893ed51a0f6fa3340b5944f
Merge: 0a40204 90a3584
Author: Vic Mitnick <vmitnick@adobe.com>
Date:   Wed Oct 21 15:28:23 2015 -0700

    Merge branch 'master' into vmitnick/layer-effect-optimiz

commit 0a402045a78feddaf70d428f9ede72be13290233
Author: Vic Mitnick <vmitnick@adobe.com>
Date:   Wed Oct 21 10:32:24 2015 -0700

    Fix a half-typo that was left over after merging with master.

commit 3578c4879e756b219f3ac66565b348b80271a3ea
Merge: a39e635 ced18ed
Author: Vic Mitnick <vmitnick@adobe.com>
Date:   Tue Oct 20 16:49:26 2015 -0700

    Merge branch 'master' into vmitnick/layer-effect-optimiz

commit a39e6357f88adbe433ae3b1a25a2ac931bb84431
Author: Vic Mitnick <vmitnick@adobe.com>
Date:   Tue Oct 20 15:36:58 2015 -0700

    Remove a couple debugging log statements.

commit 6e6818aea2ea518091c056f7528a1d0913d24193
Author: Vic Mitnick <vmitnick@adobe.com>
Date:   Tue Oct 20 12:58:42 2015 -0700

    In DocumentManager, add new function clearDeferred(), which can be used
    when the caller (e.g. devicePreview) needs to be sure that there are no
    lingering deferred promises for getDocument.
    In PixmapRenderer.prototype._getData(), clean up hasComplexTransform a bit, to include the check
    for existence of layer.

commit 80945a3296a59e41d5ea9193e6c78e61623d78cc
Author: Vic Mitnick <vmitnick@adobe.com>
Date:   Mon Oct 19 14:53:27 2015 -0700

    In _componentHasLayerEffects(), ignore layerEffects for layers that
    are directly or indirectly invisible, that can't make the layer bigger, or
    that don't cause the layer to cross the bounds of its container (document
    or artboard).
    In _getData(), only be concerned with hasComplexTransform for layers/layer groups,
    not for whole documents.

    Note; There are a couple logging statements present here that will be removed before this is merged.

Remove trailing whitespace

In _componentHasLayerEffects, when we consider whether a layer that has been enlarged due to a layer effect
also changes the size of its container, now at bounds being "beyond or equal" to the bounds of the container,
instead of just "beyond". This is because for a layerGroup that contains a layer with a (growing) effect,
the layerGroup's bounds already take the efect into account, so it was looking like the effect didn't make
the layer go outside the layerGroup.

adobe-photoshop/generator-assets,PaladinStudiosBVs/generator-assets,adobe-photoshop/generator-assets,PaladinStudiosBVs/generator-assets