Skip to content
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

Panel doesn't resize when hiding currentTypeRadioButtonGroup #1028

Closed
arouinfar opened this issue Mar 11, 2025 · 5 comments
Closed

Panel doesn't resize when hiding currentTypeRadioButtonGroup #1028

arouinfar opened this issue Mar 11, 2025 · 5 comments

Comments

@arouinfar
Copy link
Contributor

For phetsims/qa#1224

I found a dynamic layout bug in CCK: DC dev.2, as well as the latest published version 1.3. This bug is also present in the CCK: AC flavors on main.

Setting view.displayOptionsPanel.currentTypeRadioButtonGroup.visibleProperty to false leaves a gap in the panel.

Image

@samreid
Copy link
Member

samreid commented Mar 11, 2025

Related to #945

@samreid
Copy link
Member

samreid commented Mar 11, 2025

@zepumph and I pushed a proposed fix in the commit. @arouinfar can you please test on phettest? We saw that hiding both buttons individually is not well supported, but we considered this out of scope. Close if all is well.

@arouinfar
Copy link
Contributor Author

Thanks @samreid @zepumph. Looks good on main.

We saw that hiding both buttons individually is not well supported, but we considered this out of scope.

Agreed!

Close if all is well.

Shouldn't this be verified in the RC test instead of closed?

@arouinfar arouinfar assigned samreid and zepumph and unassigned arouinfar Mar 11, 2025
@zepumph
Copy link
Member

zepumph commented Mar 11, 2025

Shouldn't this be verified in the RC test instead of closed?

We are still in dev-test land. I'll make an RC from main within the next day or two.

@zepumph zepumph closed this as completed Mar 11, 2025
@arouinfar
Copy link
Contributor Author

We are still in dev-test land. I'll make an RC from main within the next day or two.

Right. I meant that this issue should be in the list of things to verify in the upcoming RC test, so it's premature to close it. Typically, we don't close issues discovered in dev tests until QA verifies the fix in the RC test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants