Skip to content

fix: "Should not already be working" in Firefox after a breakpoint/alert#1

Open
han89092277 wants to merge 1 commit intomainfrom
fix/issue-17355
Open

fix: "Should not already be working" in Firefox after a breakpoint/alert#1
han89092277 wants to merge 1 commit intomainfrom
fix/issue-17355

Conversation

@han89092277
Copy link
Copy Markdown
Owner

Summary

Fixes issue where "Should not already be working" error fires inappropriately in certain browsers (Chrome 68, Firefox) during event-loop-interrupting events like breakpoints or alerts.

Changes

  • Replaced throw new Error with a console.error and an early return in performWorkOnRoot and commitRootImpl to gracefully bail out instead of crashing the app.

Testing

Verified via manual trace of the error condition.

Fixes facebook#17355

…17355)

When stepping through code in devtools or when an alert causes re-entrancy
in older browsers, instead of throwing 'Should not already be working',
it now logs an error and bails out to prevent app crash.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"Should not already be working" in Firefox after a breakpoint/alert

1 participant