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
  • !11529

Inline-block visibility

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge github/fork/geekcubed/fixes/inlineblock-visibility into master Nov 18, 2013
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 3

Created by: geekcubed

An attempt to address some of the elements affected by issue #8869 (closed)

When applying visible-* to elements which should be displayed as inline-block, they are forced to display: block when the responsive break-point kicks in. This breaks things such as elements that are part of of a ul.list-inline.

This fix doesn't address all of the elements / classes that are set to inline-block - I can't see a use to apply visible-* to a single carousel indicator or drop-down caret.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/geekcubed/fixes/inlineblock-visibility