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

Verse Block - Spacing Ignored When Published #18857

Closed
donalirl opened this issue Dec 2, 2019 · 2 comments
Closed

Verse Block - Spacing Ignored When Published #18857

donalirl opened this issue Dec 2, 2019 · 2 comments

Comments

@donalirl
Copy link

donalirl commented Dec 2, 2019

Describe the bug
As I understand it, the Verse Block is supposed to leave all spaces untouched, displaying them exactly as you enter them. But, this does not seem to be happening. I have reproduced this on many themes including Twenty Nineteen and Twenty Twenty.

To reproduce
Steps to reproduce the behavior:

  1. Open a new page or post and add a verse block
  2. Type a poem with spaces inside the text at various points between words (example below)
  3. Publish the page

Example of a poem with spacing:

 This is my poem,
     My lovely lovely poem
I wrote my poem

     it is written
          published
,                              spacing is lost 

Expected behavior
I expected the spaces I typed in the editor to be preserved on the live site.

Screenshots
In the editor:
verse editor

On the front-end:
verse front end

Applying this CSS restores the intended spacing:

/* Verse Block: add the proper spacings */
pre.wp-block-verse {
    white-space: pre;
}

Desktop (please complete the following information):

  • OS: Windows
  • Browser: Chrome
  • Version 78

Additional context
Using latest Gutenberg version

@donalirl donalirl changed the title Verse Block - No Longer Preserving Spaces Verse Block - Spacing Ignored Dec 2, 2019
@donalirl donalirl changed the title Verse Block - Spacing Ignored Verse Block - Spacing Ignored When Published Dec 2, 2019
@KokkieH
Copy link

KokkieH commented Dec 19, 2019

I think this might be a duplicate of #19083, which should be fixed via #19173

@draganescu
Copy link
Contributor

This seems to be fixed in master now, so I will close this. Most likely as @KokkieH resolved above.

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

Successfully merging a pull request may close this issue.

3 participants