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

Grid does not arrange correctly with columns Auto,*,Auto. #3

Closed
grokys opened this issue Nov 29, 2014 · 0 comments
Closed

Grid does not arrange correctly with columns Auto,*,Auto. #3

grokys opened this issue Nov 29, 2014 · 0 comments

Comments

@grokys
Copy link
Member

grokys commented Nov 29, 2014

...and a fixed Width. Demonstrated in the issue-3-grid-problem branch.

Our Grid implementation comes from Moonlight but was converted from C++ to C#. Maybe the problem arises because that conversion missed something, but I can't see where. Perhaps the problem was also present in Moonlight.

@grokys grokys closed this as completed in 338e82c Dec 4, 2014
grokys pushed a commit that referenced this issue Sep 13, 2017
jkoritzinsky pushed a commit that referenced this issue May 23, 2018
grokys pushed a commit that referenced this issue Sep 8, 2018
kekekeks pushed a commit that referenced this issue Oct 18, 2018
kekekeks pushed a commit that referenced this issue Nov 15, 2018
Added Visual Indicators for Column Reorder
jmacato pushed a commit that referenced this issue Feb 26, 2021
grokys added a commit that referenced this issue Dec 4, 2023
github-merge-queue bot pushed a commit that referenced this issue Dec 5, 2023
* Add failing unit test for scenario 1 in #11878.

* Set TabOnceActiveElement on realized container.

Fixes scenario 1 in #11878.

* Use TabOnceActiveElement to decide focused element.

Fixes scenario #3 in #11878.
maxkatz6 pushed a commit that referenced this issue Dec 5, 2023
* Add failing unit test for scenario 1 in #11878.

* Set TabOnceActiveElement on realized container.

Fixes scenario 1 in #11878.

* Use TabOnceActiveElement to decide focused element.

Fixes scenario #3 in #11878.
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

No branches or pull requests

1 participant