Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W wayland-protocols
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container 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
  • Simon Ser
  • wayland-protocols
  • Repository
Switch branch/tag
  • wayland-protocols
  • stable
  • xdg-shell
  • xdg-shell.xml
Find file BlameHistoryPermalink
  • Simon Ser's avatar
    xdg-shell: introduce toplevel wm_capabilities · 1157e80d
    Simon Ser authored Oct 08, 2021
    
    
    Some compositors don't implement all of the features of xdg-shell.
    This results in UI elements (e.g. buttons) in clients which do
    nothing when activated.
    
    Add a wm_capabilities event to allow clients to hide these UI elements
    when they don't make sense.
    Signed-off-by: Simon Ser's avatarSimon Ser <contact@emersion.fr>
    Closes: wayland/wayland-protocols#64
    1157e80d