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.

Sign up for GitHub

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

Jump to bottom

Consider Default value of 'invisible' default-value when creating 'rs_columns_stop' #12

Closed
jacob418 opened this issue Feb 15, 2017 · 1 comment
Closed

Consider Default value of 'invisible' default-value when creating 'rs_columns_stop' #12

jacob418 opened this issue Feb 15, 2017 · 1 comment
Assignees
@ausi
Labels
bug

Comments

@jacob418
Copy link

When one has set the Content field 'invisible' to default checked, every element is invisible after creation.

When creating a closing wrapper this value is not replicated there, it is set to visible always, indifferent what the default value for 'invisible' field is.

This can lead to bad column set configurations and destructed layouts.
@ausi ausi self-assigned this Feb 15, 2017
@ausi ausi added the bug label Feb 15, 2017
@ausi ausi closed this as completed in 4767901 Jun 18, 2018
ausi added a commit that referenced this issue Jun 18, 2018
@ausi
Copy visibility settings from start element, fixes #12
35ca1f9
@ausi
Copy link
Member

ausi commented Jun 18, 2018

Fixed in 4767901 and 35ca1f9

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

@ausi ausi

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ausi @jacob418