-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix or revert PR #12363 #12367
Comments
I'd suggest reverting the PR immediately, since it currently causes (viewer) errors and testing/makeref won't work correctly, and re-landing it later once it's been carefully tested/validated. While it's probably simple to just hack-around the error, however the final patch ought to explain why (for this case) things broke such that we don't just introduce an error elsewhere; especially considering that the SMask handling isn't that simple/straightforward. |
I have a fix, but I'm happy re-landing after revert if that's preferred. |
…stateStack is empty. This fixes mozilla#12367. When we end the SMask group and stateStack.length is zero, nothing updates this.current to reflect it.
#12369 is the fix. |
(And I think the fix is pretty safe, but again, more than happy to revert my original PR, then land the fix, then re-land my original PR). |
…stateStack is empty. This fixes mozilla#12367. When we end the SMask group and stateStack.length is zero, nothing updates this.current to reflect it.
I've done the former, thanks, and sorry for the trouble! |
…stateStack is empty. This fixes the issue that caused mozilla#12363 to get reverted, see mozilla#12367. When we end the SMask group and stateStack.length is zero, nothing updates this.current to reflect it.
No worries! |
See #12363 (comment) for context. If we can easily fix this I'd prefer that, but otherwise we can revert it for now.
/cc @emilio
The text was updated successfully, but these errors were encountered: