Jetpack Checklist: Center Guided Tour bubble arrow below toggle

[ockham]

From #25864 (comment):

Guided Tours positioning is based on element selectors (.sso__card .form-toggle__switch), and some more 'qualitative' args (arrow="top-left", placement="below"). You'd think that'd do a better job:

Maybe I can use the additional style arg to tweak this...

#25864 (comment):

Unfortunately it doesn't seem like an easy problem to fix because as @ockham mentions, its position is calculated from the picked selector, so the left values you're seeing @joanrho are generated dynamically and change depending on the screen resolution you use.

transform: translateX(-16px) would be ideal here but doesn't work because it has a fixed position.

margin-left: -16px seems to do the trick, but it's not pretty at all.

[jeherve]

This also happens for plugin autoupdates:

This is on Mac OS Catalina with Chrome Version 78.0.3904.108.

Reported in p8oabR-qW-p2#comment-3592

[davipontesblog]

Moved to Jetpack Improved Onboarding for triaging.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[github-actions]

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

[cuemarie]

👋 Hey folks! Since this issue has been inactive for quite some time, KitKat has made the decision to close it.

• Internal reference, for more on this decision: pdqkMK-14B-p2

If you think this issue warrants another look, here are some next steps!

1. Report anew: A new report with more current details and steps to replicate may be the best way to renew attention on this issue. Feel free to refer back to this closed issue in your report!
2. Reopen: If you feel the issue still matches the context/history here, you can also reopen the issue and add fresh logs, screenshots and steps to reproduce.

Thanks for your involvement!