Fix a bogus assertion in CLM

In the CompositedLayerMapping's doPaintTask function we ASSERT that
we never get here if we paint into our composited ancestor (i.e., we
don't paint ourself). This doesn't make sense for the squashing layer.
Even if the layer that owns the backing happens to paint into its
ancestor, the squashed layers may well paint into the squashing layer.

BUG=394413

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

git-svn-id: svn://svn.chromium.org/blink/trunk@180328 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert of Add lextab.pyc as an output of the cached_lex_yacc_tables action (patchset #1 of https://codereview.chromium.org/463063003/)

Reason for revert:
This CL added the assumption that Python will write the lextab.pyc file. If that's a wrong assumption, which seems to be the case in some situations, the result is that the cached_lex_yacc_tables target never becomes clean, which in turn means that all IDL files are recompiled on each build.

The problem fixed by this CL was cosmetic only, so is not worth the risk.

Original issue's description:
> Add lextab.pyc as an output of the cached_lex_yacc_tables action
> 
> The primary output is lextab.py, but since it is imported, Python also
> writes lextab.pyc. Listing it too as an output means it won't be left
> around by "ninja -t clean" (and not much else, I think.)
> 
> Prior to the patch
>   https://codereview.chromium.org/425953002/
> the result of not having lextab.pyc listed as an output and running
> "ninja -t clean" was a tree that would build correctly, but that would
> always rerun all the IDL code generation scripts, and thus never become
> "clean".
> 
> BUG=397909
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=180142

TBR=haraken@chromium.org,nbarth@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=397909

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

git-svn-id: svn://svn.chromium.org/blink/trunk@180329 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Merge m_didCallDispose and m_isMarkedForDeletion flags into one flag

Currently we have the following two flags:

- m_didCallDispose is used to know whether AudioContext::dispose() is called or not.
- m_isMarkedForDeletion is used to guarantee the following facts:

--- AudioNode should not be re-registered to AudioNode::m_outputs after AudioNode::dispose is called.
--- AudioNode should not get marked as dirty after AudoNode::dispose is called.

We don't need the two flags; just one flag that is set in AudioContext::dispose() is enough.

This CL removes m_didCallDispose and m_isMarkedForDeletion and introduces m_isDisposeCalled. This CL doesn't change any behavior.

BUG=340522

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

git-svn-id: svn://svn.chromium.org/blink/trunk@180330 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename minRepetitions to maxRepetitions and clamp with min()

The value minRepetitions is actually used as an upper bound. Looks like
this was a misunderstanding of a review comment in
https://codereview.chromium.org/251643002.

BUG=404023

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

git-svn-id: svn://svn.chromium.org/blink/trunk@180331 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add an assertion to make sure NodeRenderingTraversal::parent is not called with a dirty distribution result.

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

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