bootstrap icon indicating copy to clipboard operation
bootstrap copied to clipboard

Remove `outline: 0` from modals

Open coliff opened this issue 9 months ago • 4 comments

Description

This was added about 12 years ago and is no longer needed from what I can tell.

I've tested with Chrome 133 and Edge 122 on Windows 11. The modal itself is never focused anyway, when the modal opens the focus is only within the modal.

Motivation & Context

No longer needed. Removing it saves a few bytes. :-)

Type of changes

  • [x] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Refactoring (non-breaking change)
  • [ ] Breaking change (fix or feature that would change existing functionality)

Checklist

  • [x] I have read the contributing guidelines
  • [ ] My code follows the code style of the project (using npm run lint)
  • [ ] My change introduces changes to the documentation
  • [ ] I have updated the documentation accordingly
  • [ ] I have added tests to cover my changes
  • [ ] All new and existing tests passed

Live previews

Related issues

coliff avatar Mar 05 '25 12:03 coliff

Thanks for this patch. Unfortunately, I don't have access anymore to BrowserStack (or any equivalent tool) to try to render the thing with Chrome 60 on Windows (based on the rules of our current .browserslistrc. The safest option would maybe be to merge this PR in v6 where we'll use less restrictive rules in the .browserslistrc file.

julien-deramond avatar Mar 05 '25 19:03 julien-deramond

thanks! I have a BrowserStack subscription and just tested this with Chrome 60 on Windows 10 and it does indeed still have an unwanted blue outline without the outline: 0

image

Production version (with the outline: 0) doesn't have this issue: image

So you're quite right, it should be parked until v6. 👍

coliff avatar Mar 06 '25 09:03 coliff

Thanks a lot for providing the rendering with Chrome 60 on Windows 10 🙌 @mdo That's something you could introduce in your current work in the v6-dev branch.

julien-deramond avatar Mar 06 '25 20:03 julien-deramond

Man, Chrome 60 is archaic these days lol. I can't wait to move on from our browser support list here. Let's just save for v6 to be good about leaving v5 in a good spot for what it is. We can always roll back on this. But at the same time, I don't care at all haha.

mdo avatar Apr 06 '25 19:04 mdo