Unexpected changes in continuation behavior between 0.8.0 and 1.0.0 release?

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

mdast-util-from-markdown@1.0.0 (via remark-parse@10.0.0)

Link to runnable example

https://codesandbox.io/s/rough-silence-cu56j?file=/src/grid/syntax.js

Steps to reproduce

In the linked codesandbox above, compare the rendered output (and console log) between remark-parse is locked at v9.0.0 vs v10.0.0

• in v9.0.0 (mdast-util-from-markdown@^0.8.0): continuation correctly trigger exit when nok was returned, as seen in the console.log output of:

  #### START 
  onGridStart 
  shouldContinue?  ok 
  shouldContinue?  ok 
  shouldContinue?  nok 
  onGridExit 
  onGridStart 
  shouldContinue?  ok 
  shouldContinue?  ok 
  shouldContinue?  nok 
  onGridExit 
  

• in v10.0.0 (mdast-util-from-markdown@^1.0.0): a 2nd “onGridStart” somehow gets triggered before the first continuation exits, leading to imbalance enter-exit effects pair:

  onGridStart 
  shouldContinue?  ok 
  shouldContinue?  nok 
  onGridStart 
  onGridExit 
  onGridStart 
  shouldContinue?  ok 
  shouldContinue?  nok 
  onGridExit
  

Expected behavior

a 2nd enter should not be triggered before the 1st exited

Actual behavior

a 2nd enter is triggered triggered before the 1st exited

Runtime

No response

Package manager

No response

OS

No response

Build and bundle tools

No response

[ignatiusreza]

i see, i didn’t know that lazy line is a thing in markdown… i tested that the same change in behavior is observable in other construct as well, e.g. list…

given that the updated behavior is considered a bugfix, i’ll close this ticket…

[github-actions[bot]]

Hi team! Could you describe why this has been marked as wontfix?

Thanks, — bb