Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bootstrap
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 114
    • Merge requests 114
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Bootstrap
  • bootstrap
  • Merge requests
  • !38128

(Fixed) Brand icon area too large in third header example #38122

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge github/fork/xarcode/docs-example-change into main Feb 28, 2023
  • Overview 4
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: xarcode

Closes #38122 (closed)

Description

The brand icon area was too large in the third header example from 769px breakpoint. After going through the html page, it was found that changing the Bootstrap spacing classes from col-md-3 mb-2 mb-md-0 to my-2 my-lg-0 me-lg-auto solves the issue.

Reference of the issue

Motivation & Context

Earlier, a user reading through the docs could accidentally click the Bootstrap icon since the icon area was too large. After this change, such a behavior will no longer happen.

Type of changes

  • 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

  • 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
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/xarcode/docs-example-change