Fix error recovery after invalid var() in unparsed declarations.
If hitting an invalid var() while in a block, we would go into error
recovery mode and eat tokens until we are back at the top level.
However, since we did “break”, we did not reach the “continue” statement
that would jump over the otherwise-used logic of incrementing the
block level counter. Fundamentally, this comes from the issue that
in C++, break and continue in the same context can refer to entirely
different loop constructs (in this case, a switch and a for loop).
Fixed: 364443009
Change-Id: I54356afa37afffe590e04810cda0c14ac386487c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5839697
Commit-Queue: Steinar H Gunderson sesse@chromium.org
Reviewed-by: Anders Hartvoll Ruud andruud@chromium.org
Cr-Commit-Position: refs/heads/main@{#1351326}