-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Stub / spy counter badge is cut off #4822
Comments
Hello @bahmutov - I think I know how to address this. It would seem that the counter is not so much being 'cut off' as the border-radius css hasn't been defined to create a symmetrical pill shape around the counter. Specifically, I would propose changing the css to .num-duplicates.has-alias {
border-radius: 10px 10px 10px 10px;
line-height: 2;
padding: 3px 5px 3px 5px;
} I believe this change would give the desired 'not cut-off look' you are seeking. Would you like me to contribute this change? |
@hhudson Sure! The CSS is here. I def broke this about a month ago. 😝 https://github.com/cypress-io/cypress/blob/issue-4874/packages/reporter/src/commands/commands.scss#L164 |
Proposal to eliminate the 'cut-off' appearance of the counter in favor of more of a 'pillbox' look
The code for this is done in cypress-io/cypress#4910, but has yet to be released. |
* #4822 Proposal to eliminate the 'cut-off' appearance of the counter in favor of more of a 'pillbox' look * Simplify 10px CSS
* cypress-io#4822 Proposal to eliminate the 'cut-off' appearance of the counter in favor of more of a 'pillbox' look * Simplify 10px CSS
Released in |
Cypress 3.4.0 with Electron or Chrome
Recipe in https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/stubbing-spying__window
Run the spec file and after it is finished click on the button "Open new window" inside the application frame (like a user). The
cy.stub
counter keeps incrementing - and the badge appears, but the badge gets cut off on the left.Relevant markup
Relevant files:
The text was updated successfully, but these errors were encountered: