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

Less greedy span selector using a starts-with pattern rather than a contains.

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge github/fork/r-murphy/master into master Nov 28, 2011
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: r-murphy

The current wildcard span selector selects any class which contains the word 'span'. Based on the classes bootstrap uses, it should be enough to just select where the class starts with span. That way there will be less conflicts with other css classes.

In my particular case, the conflicts are caused by a WYSIWYG editor which adds a class 'Apple-style-span'.

*Yes, I know WYSIWYG editors are flaky, but it's what my client wants ;)

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/r-murphy/master