-
Notifications
You must be signed in to change notification settings - Fork 25
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
primary-component-initialratio #17
Comments
I am also having this issue. I have tried it with .9 and 1 and it always goes basically in half. |
the same to me, two divs always in half |
Do you have dynamic values for primary-component-toggled-off or secondary-component-toggled-off? |
I've tried with or without a lot of settings. Always is .5. Even in the demo provided it is at half. How I have mine set up currently : |
Same issue, however, in my case the layout is not visible when its initialized, its encapsulating div has [hidden] on it. Does this matter? |
I have the same issue - can't get primary-component-initialratio to work, and it doesn't work in your own Plunkr I'd love to have a fix for this! |
When primary component is toggled off from the start, the ratio is set to 0.5 although I have set it to 0.3. Is there any workaround to fix it? |
I seem to have a tough time getting 'primary-component-initialratio' to work.
In your Plunker, per your documentation, I expect a { 'primary-component-initialratio': 0.8 } on the 'vertical-split-pane' div to would result in 'Left' to be basically '80%' while 'Right' would be the remaining '20%'.
Am I missing some details or totally misunderstanding this property?
Thanks in advance.
The text was updated successfully, but these errors were encountered: