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

_ #395

Closed
ghost opened this Issue Sep 26, 2016 · 3 comments

Comments

Projects
None yet
1 participant
@ghost
Copy link

ghost commented Sep 26, 2016

_

@ghost ghost closed this Sep 26, 2016

@ghost ghost reopened this Sep 26, 2016

@dioslaska

This comment has been minimized.

Copy link
Contributor

dioslaska commented Sep 27, 2016

Thanks for the detailed steps to reproduce. Based on the description I think this will occur everywhere, regardless of enviroment.

The problem most probably is, that the Cards needs some dimensions for proper operations. On orientationchange these dimensions are automatically recalculated, but if the Cards are not visible (container div is invisible) , this won't work correctly.

The solution would be to call the refresh method of the Cards menustrip every time its tab becomes visible to force recalculation.

Let me know if this solves.

@dioslaska

This comment has been minimized.

Copy link
Contributor

dioslaska commented Oct 3, 2016

Using your code the issue is reproducible everywhere, even in the browser, in specific conditions:

  • menustrip is not visible at the time of the initialization
  • snap is set to true
  • itemWidth is not specified

The workaround in this case is to add itemWidth: 1 to the init settings

@dioslaska dioslaska changed the title MenuStrip Cards not working properly on Amazon Fire MenuStrip snap not working properly Oct 3, 2016

dioslaska added a commit that referenced this issue Oct 7, 2016

@dioslaska

This comment has been minimized.

Copy link
Contributor

dioslaska commented Oct 12, 2016

Fixed in 3.0.0-beta6

@dioslaska dioslaska closed this Oct 12, 2016

@ghost ghost changed the title MenuStrip snap not working properly _ Jan 3, 2019

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