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
  • Issues
  • #18178
Closed
Open
Issue created Nov 05, 2015 by Administrator@rootContributor

Why are responsive images opt-in?

Created by: peiche

It seems strange to me that Bootstrap, being responsive and mobile-first, requires an additional class for any image to behave responsively. The docs state that you must manually disable responsiveness, but conversely, you must add a class to images to enable, not disable, responsive behavior.

Obviously your choices are your choices, and I'm not looking to reverse that. I would just like to know the reasoning behind this decision, and I'm unable to find a past issue that might address this.

Assignee
Assign to
Time tracking