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
  • #6448
Closed
Open
Issue created Jan 04, 2013 by Administrator@rootContributor

Recommendation: Modal backdrop click should not close modal before it is fully shown

Created by: tenedor

Given a modal with backdrop: true and a fade class, double-clicking a button that launches the modal will hide the modal before it has been shown. The first click lands on the button while the second lands on the backdrop. This seems undesirable during a fade transition and might be undesirable even when there is no delay caused by a transition.

Possibilities:

  • ignore all backdrop clicks during the time window presumed to be a doubleclick (Microsoft loosely suggests 500ms)
  • ignore backdrop clicks until the shown event, thereby handling

Both of these changes reduce Bootstrap's flexibility since a developer can add these behaviors onto Bootstrap but cannot remove them. (A noDoubleClick option could be added to modals, but this is probably not worth the additional API complexity.) However, it seems more likely that a user would accidentally doubleclick a button than that a user would almost-immediately reclick after misclicking a button; furthermore, it seems more likely that a user would be annoyed by undesired behavior in the first case than in the second case.

Assignee
Assign to
Time tracking