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

Layouts - Moving a layout above a block that is not within a layout makes layout inaccessible #2738

Closed
Ruudt opened this issue Jul 16, 2015 · 3 comments

Comments

@Ruudt
Copy link
Contributor

Ruudt commented Jul 16, 2015

When I want to move a layout above a block element that is directly placed into the area (so not contained itself within a layout) the layout and everything in it are inaccessible. The system thinks the block covers the entire area of itself + the layout. So the blocks controls and green lines also encompass the layout above.

Steps to reproduce (Concrete 5.7.4.2):

  1. Add a content block to an area (I've added a Horizontal rule)
  2. Add a layout to that area (I use Twitter bootstrap, and set 2 columns at 50/50%)
  3. Add a content block in each column (just to add some height)
  4. Click one of the labels below theadded columns and select "Edit Container Layout"
  5. Using the move icon; pick up the layout and drag it to the top of the area (notice it might be hard to get the top line to thicken).
  6. Now try to click the content. You'll notice the part outline includes the hr and nothing in that area does as you would expect.

I included no packages/css/js files.

@KorvinSzanto
Copy link
Member

I followed your directions exactly and wasn't able to replicate this on the current develop. So I asked @MeyerJL to test as well and neither of us could replicate it. Try checking for javascript errors that might be breaking something.

Feel free to reopen if you're able to replicate on the develop branch.

@joe-meyer
Copy link
Contributor

Can confirm the struggle was real in 5.7.4.2. This behaves way better in the develop branch. Should be fixed in the next release :)

@Ruudt
Copy link
Contributor Author

Ruudt commented Jul 17, 2015

Good to hear. Thanks!
On Jul 16, 2015 23:22, "Joe Meyer" notifications@github.com wrote:

Can confirm the struggle was real in 5.7.4.2. This behaves way better in
the develop branch. Should be fixed in the next release :)


Reply to this email directly or view it on GitHub
#2738 (comment)
.

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

3 participants