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

Blocks: Movers on left floated content overlapping next elements controls #3868

Closed
gziolo opened this issue Dec 8, 2017 · 7 comments
Closed
Labels
[Feature] Blocks Overall functionality of blocks [Type] Bug An existing feature does not function as intended
Milestone

Comments

@gziolo
Copy link
Member

gziolo commented Dec 8, 2017

Issue Overview

Movers on left floated content overlapping next elements controls.

Steps to Reproduce (for bugs)

  1. Add an image.
  2. Set align left property on the image.
  3. Add any other block with text.
  4. Try to move the 2nd block up.
  5. It's not possible because movers from the image take precedence.

Browser: Chrome.
System: macOS.

Expected Behavior

It's possible to move the block added after the floated image.

Current Behavior

It's not possible to move the block added after the floated image because movers from the image take precedence.

Screenshots / Video

screen shot 2017-11-30 at 10 43 20

/cc @jasmussen

@gziolo gziolo added [Feature] Blocks Overall functionality of blocks [Type] Bug An existing feature does not function as intended labels Dec 8, 2017
@mikeyarce
Copy link
Contributor

Came to report the same thing:
Screenshot

I would add that I did not expect blocks to be able to be overlapping. Its nice because I would actually like to have an image and text beside it, but the controls aren't easily usable.

If you align the image to the right, the menu is then hidden from one of the blocks:
Screenshot

@jasmussen
Copy link
Contributor

Really really good bug report.

The big issue here is that side controls appear on hover. When those controls stack, you can't decide which layer of controls you want to deal with.

One hacky fix could be making sure that whenever a block is floated, the hover controls can only appear if the block has first been selected. But I'm not sure this would fix it — the non-floated quote block would then stack below. Hmmm. Any ideas here, @youknowriad? Can we make it so the floated image block prevents any other block than itself to be "hovered"? I.e. you can't hover the text block "through" the image block?

Another option is to rethink how the controls work generally on floated (or future nested blocks, for that matter). I just posted some mockups in #428 (comment). The idea, applied to this issue, would be that any floated block would get the inline, "mobile UI". That way you could still use the controls on the image because they wouldn't stack.

A plan B would be to simply only allow those side controls to appear if you've first selected a block.

@youknowriad
Copy link
Contributor

Any ideas here, @youknowriad? Can we make it so the floated image block prevents any other block than itself to be "hovered"? I.e. you can't hover the text block "through" the image block?

I tried playing with pointer-events and such but couldn't make it work properly :(. The plan B/C should be tried I think. But I think no matter what we do we'll always have a similar issue. The mobile controls of a floated/non-floated block can still overlap

@jasmussen
Copy link
Contributor

The mobile controls of a floated/non-floated block can still overlap

Not if we go with the mobile controls that appear onselect and below the block surely?

@youknowriad
Copy link
Contributor

below the block surely

This is not sufficient on its own but yes if they appear only on select then yes the can't overlap

@karmatosed karmatosed added this to the Merge Proposal milestone Jan 25, 2018
@jasmussen
Copy link
Contributor

This issue appears to have been fixed with the recent floats refactor:

floatmovers

The issue with the right-aligned toolbar will be fixed when #5212 is merged.

Noting that the side-UI for floated items still isn't ideal, the movers for floated blocks should perhaps be optimized, the buttons nonetheless work now as expected.

@gziolo
Copy link
Member Author

gziolo commented Feb 23, 2018

Thanks for fixing 🌟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Blocks Overall functionality of blocks [Type] Bug An existing feature does not function as intended
Projects
None yet
Development

No branches or pull requests

5 participants