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

Can't disable automatic assignment to background layer for full bleed content #12987

Open
RyanNeilson opened this issue Jan 31, 2023 · 2 comments
Labels
Group: Canvas Type: Bug Something isn't working Type: UX Quality For issues impacting user experience UX Needed

Comments

@RyanNeilson
Copy link

RyanNeilson commented Jan 31, 2023

Bug Description

When adding an element (an image, usually) to the web story canvas, if that element spans wider than the entire canvas it is automatically applied as the background layer.

I can detach the element from the background manually, but if I reposition the element at all it will once again be set as the background. The editors I work with are reporting this as a significant impediment to their workflow.

Expected Behaviour

There should be some kind of settings field where the behavior of automatically setting a full bleed element as the background can be toggled on or off.

Steps to Reproduce

  • In the web stories editor, drag an image from the library onto an empty canvas.
  • Resize the added image so that it bleeds outside the workspace in all directions.
  • The image will be automatically applied as the background layer for the current page.
  • Click on the image / background layer and in the popup list click Detach Image From Background.
  • Move the image on the canvas, making sure it still overflows the canvas in all directions.
  • When you stop moving the image it will once again be set as the background layer.

Additional Context

  • Plugin Version: 1.27.0
  • WordPress Version: 5.8.4
  • Operating System: Mac OS Monterey
  • Browser: Google Chrome version 109
@RyanNeilson RyanNeilson added the Type: Bug Something isn't working label Jan 31, 2023
@swissspidy
Copy link
Collaborator

Thanks for raising this.

Is there a specific type of story or page layout where this current behavior is deemed not useful? i.e. what result are you aiming for when this happens? A screenshot or story link might be helpful.

@RyanNeilson
Copy link
Author

We have some web stories where editors build charts out of stacked layers, which are sometimes partly transparent and overflow the web story in all directions. A pretty typical example of one of these charts is on page 7 of this web story: https://www.barrons.com/visual-stories/lithium-electric-cars-tesla-stocks-01663596657

There isn't a specific story type where this is an issue, but the most common case where this behavior becomes a headache is with charts like these.

@swissspidy swissspidy added UX Needed Group: Canvas Type: UX Quality For issues impacting user experience labels Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Group: Canvas Type: Bug Something isn't working Type: UX Quality For issues impacting user experience UX Needed
Projects
None yet
Development

No branches or pull requests

2 participants