You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the test helper to reset your FTC progress, options and whatever is needed to get the notification with the Start SEO data optimization button, as show in the screenshot below
Enable the feature flag
Visit the General page
Have the screen width between 1024 and 1124 pixels
Notice the Start SEO data optimization notification is pushing its button out of bounds
Hide the notification in question
Have a screen width between 1024 and 1248 pixels
Notice it is even worse now
What needs to be done to achieve the goal?
WP styling includes a white-space: nowrap; style on the .button class, which that Start SEO data optimization has.
However, there is still not enough room then between 1024 and ~1090 pixels.
I haven't figured out why that is. But could be better to just change when the cards go below each other instead?
Does the issue still need UX or research?
If available: what are the tips for fixing the problem or possible solutions?
What is the expected result/behavior?
Should documentation be added or updated for this change? and if so, where?
The text was updated successfully, but these errors were encountered:
What is the goal of this issue?
Start SEO data optimization
button, as show in the screenshot belowStart SEO data optimization
notification is pushing its button out of boundsWhat needs to be done to achieve the goal?
WP styling includes a
white-space: nowrap;
style on the.button
class, which thatStart SEO data optimization
has.However, there is still not enough room then between 1024 and ~1090 pixels.
I haven't figured out why that is. But could be better to just change when the cards go below each other instead?
Does the issue still need UX or research?
If available: what are the tips for fixing the problem or possible solutions?
What is the expected result/behavior?
Should documentation be added or updated for this change? and if so, where?
The text was updated successfully, but these errors were encountered: