Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Pajamas Design System
Pajamas Design System
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 276
    • Issues 276
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 15
    • Merge Requests 15
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-services
  • Pajamas Design SystemPajamas Design System
  • Issues
  • #783

Closed
Open
Opened Jan 06, 2021 by Taurie Davis@tauriedavis🔴Maintainer0 of 1 task completed0/1 task

Alerts > Consider removing danger alert variant

The following discussion from !2206 (merged) should be addressed:

  • @tauriedavis started a discussion: (+3 comments)

    I know we've talked about this previously so apologies if this is rehashing old topics, but it is possible for an error alert to be contextual as well, right? I could imagine it being global or contextual. For example, perhaps a graph fails to load and so an error alert is shown.

    An error alert may happen in a global context that impacts the entire experience. When this occurs, it is placed directly below the navigation bar. For example, an alert that states “Your subscription has expired” after a user has authenticated. Only the global error alert uses `position: sticky`, while other alert variants are contextual within a page and scroll with content.

    Reading further, the example given under page-level does appear to be what I would consider an error alert so I think we are aligned.

Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-services/design.gitlab.com#783