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

Enable shadow support for cover block #61883

Merged
merged 1 commit into from
May 25, 2024
Merged

Conversation

vcanales
Copy link
Member

What?

On previous attempts to do this, the cover block was displaying inconsistencies between how it was rendered in the editor vs the frontend; that doesn't seem to be the case anymore, so we should be enable shadow support without any modifications to the block itself.

I'd still appreciate some eyes on this, because I don't know what exactly has changed since the first time I attempted this.

Testing Instructions

  1. Add a cover block
  2. Add a shadow to it
  3. Modify the block's border radius and size; modifications should be consistent between frontend and editor.

Screenshots or screencast

image

@vcanales vcanales added the [Block] Cover Affects the Cover Block - used to display content laid over a background image label May 22, 2024
@vcanales vcanales added this to the Gutenberg 18.4 milestone May 22, 2024
@vcanales vcanales added [Type] Enhancement A suggestion for improvement. [Type] Feature New feature to highlight in changelogs. and removed [Type] Enhancement A suggestion for improvement. labels May 22, 2024
Copy link

github-actions bot commented May 22, 2024

Flaky tests detected in bc517f0.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9215617685
📝 Reported issues:

@vcanales vcanales force-pushed the add/cover-block-shadow-support branch from 46425ba to 7de05db Compare May 23, 2024 22:13
Copy link

github-actions bot commented May 23, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: vcanales <vcanales@git.wordpress.org>
Co-authored-by: madhusudhand <madhudollu@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@vcanales vcanales force-pushed the add/cover-block-shadow-support branch 2 times, most recently from 25554a6 to bc517f0 Compare May 23, 2024 22:20
Copy link
Contributor

@madhusudhand madhusudhand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shadow applies to cover block both in global styles and block settings.

LGTM! 🚢

On previous attempts to do this, the cover block was displaying
inconsistencies between how it was rendered in the editor vs the
frontend; that doesn't seem to be the case anymore, so we should be
able to enable shadow support without any modifications to the block itself.

I'd still appreciate some eyes on this, because I don't know what
exactly has changed since the first time I attempted this.

Tracking issue: #57103

Co-authored-by: vcanales <vcanales@git.wordpress.org>
Co-authored-by: madhusudhand <madhudollu@git.wordpress.org>
@vcanales vcanales force-pushed the add/cover-block-shadow-support branch from bc517f0 to 770fa91 Compare May 25, 2024 15:49
@vcanales vcanales enabled auto-merge (squash) May 25, 2024 15:52
@vcanales vcanales merged commit 97422ea into trunk May 25, 2024
61 checks passed
@vcanales vcanales deleted the add/cover-block-shadow-support branch May 25, 2024 16:27
@bph bph added [Type] Enhancement A suggestion for improvement. and removed [Type] Feature New feature to highlight in changelogs. labels Jun 3, 2024
carstingaxion pushed a commit to carstingaxion/gutenberg that referenced this pull request Jun 4, 2024
On previous attempts to do this, the cover block was displaying
inconsistencies between how it was rendered in the editor vs the
frontend; that doesn't seem to be the case anymore, so we should be
able to enable shadow support without any modifications to the block itself.

I'd still appreciate some eyes on this, because I don't know what
exactly has changed since the first time I attempted this.

Tracking issue: WordPress#57103

Co-authored-by: madhusudhand <madhudollu@git.wordpress.org>
vcanales added a commit that referenced this pull request Jun 11, 2024
On previous attempts to do this, the cover block was displaying
inconsistencies between how it was rendered in the editor vs the
frontend; that doesn't seem to be the case anymore, so we should be
able to enable shadow support without any modifications to the block itself.

I'd still appreciate some eyes on this, because I don't know what
exactly has changed since the first time I attempted this.

Tracking issue: #57103

Co-authored-by: madhusudhand <madhudollu@git.wordpress.org>
patil-vipul pushed a commit to patil-vipul/gutenberg that referenced this pull request Jun 17, 2024
On previous attempts to do this, the cover block was displaying
inconsistencies between how it was rendered in the editor vs the
frontend; that doesn't seem to be the case anymore, so we should be
able to enable shadow support without any modifications to the block itself.

I'd still appreciate some eyes on this, because I don't know what
exactly has changed since the first time I attempted this.

Tracking issue: WordPress#57103

Co-authored-by: madhusudhand <madhudollu@git.wordpress.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Block] Cover Affects the Cover Block - used to display content laid over a background image [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants