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
Multiple track registration constructor vs add api (split-grid) #781
Comments
I think either one of the following should happen.
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please refer to reproduction below:
Reproduction
It has two versions (Constructor and Api)
both are doing the same thing:
For Constructor, it works fine (but i guess i am doing something I should not be doing)
For Api, only the last div for track works (3rd div for column. and 3rd div for row 1 and row 3)
Constructor works because it does not "cleanup" duplicates.
if
gutterOptins.track
has duplicates, it does not destroy the previous one, though i guess, based on code, that i should not do this (?)For Api, it is a different story
Is it intentional that there can only be one element per track?
My intention is to add an orthogonal control (so that intersection can control both directions at the same time when resizing)
The text was updated successfully, but these errors were encountered: