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

Allow Positioning Options for Header and Footer #86286

Open
rickmgithub opened this issue Jan 11, 2024 · 10 comments
Open

Allow Positioning Options for Header and Footer #86286

rickmgithub opened this issue Jan 11, 2024 · 10 comments
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Feature Request Feature requests

Comments

@rickmgithub
Copy link

Quick summary

It's not possible to set a sticky header
Setting sticky on a group block within a header also doesn't work.
The content scrolls.
Moving the group block outside the header fixes the problem.

Steps to reproduce

  1. Create a header with a group in the home page template
    Markup on 2024-01-11 at 22:05:28
  2. Try to set the group of header to sticky
  3. Once the group block has been set to sticky move it outside the header. Now it works

What you expected to happen

That the header and the group block within it should be possible to set as sticky

What actually happened

The sticky option had no effect.
Replicate the problem on a test site with a similar set up.

Impact

Some (< 50%)

Available workarounds?

Yes, easy to implement

Platform (Simple and/or Atomic)

No response

Logs or notes

7569183

@rickmgithub rickmgithub added [Type] Bug When a feature is broken and / or not performing as intended Needs triage Ticket needs to be triaged [Feature] Full Site Editor The site editor. [Product] WordPress.com All features accessible on and related to WordPress.com. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. labels Jan 11, 2024
@github-actions github-actions bot added the [Pri] Low Address when resources are available. label Jan 11, 2024
@cat-og cat-og added [Type] Feature Request Feature requests and removed [Type] Bug When a feature is broken and / or not performing as intended labels Jan 12, 2024
@cat-og
Copy link

cat-og commented Jan 12, 2024

📌 REPRODUCTION RESULTS

  • Tested on Simple – Replicated
  • Tested on Atomic – Replicated

📌 FINDINGS
This is technically not a bug, as the Sticky feature is only intended to work on top level blocks, and will not work when the Group is nested, as it is in the Header.

📌 ACTIONS

  • Update as Feature request; Allow Positioning Options for Header and Footer.

@cat-og cat-og moved this from Needs Triage to In Triage in Automattic Prioritization: The One Board ™ Jan 12, 2024
@cat-og cat-og changed the title Header can't be made sticky Allow Positioning Options for Header and Footer Jan 13, 2024
@cat-og cat-og moved this from In Triage to Triaged in Automattic Prioritization: The One Board ™ Jan 13, 2024
@happychait
Copy link

A user shared feedback about the issue in this ticket, in 8209807-zen

Copy link

github-actions bot commented May 18, 2024

Support References

This comment is automatically generated. Please do not edit it.

  • 8209807-zen
  • 8254974-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label May 18, 2024
@happychait
Copy link

Another report in 8254974-zen

@inaikem inaikem closed this as completed Oct 13, 2024
@inaikem inaikem reopened this Oct 13, 2024
@inaikem inaikem moved this from Done 🎉 to Needs Triage in Automattic Prioritization: The One Board ™ Oct 15, 2024
@inaikem
Copy link
Contributor

inaikem commented Oct 15, 2024

@Automattic/dotcom-product-ambassadors, please retriage this issue and if needed, create a companion Core issue, thanks!

@Robertght Robertght added Triaged To be used when issues have been triaged. and removed Needs triage Ticket needs to be triaged labels Oct 23, 2024
@Robertght Robertght moved this from Needs Triage to Triaged in Automattic Prioritization: The One Board ™ Oct 23, 2024
@Robertght
Copy link

Robertght commented Oct 23, 2024

📌 REPRODUCTION RESULTS

  • Tested on Simple – Replicated
  • Tested on Atomic – Replicated
  • Replicable outside of Dotcom – YES

📌 ACTIONS

@matticbot matticbot moved this from Needs Core/3rd Party Fix to Triaged in Automattic Prioritization: The One Board ™ Oct 23, 2024
@Robertght Robertght moved this from Triaged to Needs Core/3rd Party Fix in Automattic Prioritization: The One Board ™ Oct 23, 2024
@inaikem
Copy link
Contributor

inaikem commented Oct 24, 2024

Hey @Robertght, quick question: You noted it can't be replicated on self-hosted sites but raised a Core issue. I just wanted to learn more about that decsion.

@Robertght
Copy link

Apologies! I removed the wrong answer 🤦 . Corrected now.

@mmtr
Copy link
Member

mmtr commented Jan 21, 2025

Hey @annezazu, do you think someone from the .Org/CtD folks could look into this? Thanks!

@annezazu
Copy link

Hey, hey. This matches this issue in Gutenberg: WordPress/gutenberg#50617 It also was discussed here: WordPress/gutenberg#47043

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". [Feature] Full Site Editor The site editor. [Feature Group] Editor Experience Features related to Gutenberg integration on WordPress.com. [Pri] Low Address when resources are available. [Product] WordPress.com All features accessible on and related to WordPress.com. Triaged To be used when issues have been triaged. [Type] Feature Request Feature requests
Projects
Development

No branches or pull requests

7 participants