Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W weston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 342
    • Issues 342
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 134
    • Merge requests 134
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waylandwayland
  • weston
  • Issues
  • #92
Closed
Open
Issue created May 14, 2017 by Bugzilla Migration User@bugzilla-migration

Chrome/Chromium's maximize button doesn't work

Submitted by Ilia Bozhinov

Assigned to Wayland bug list

Link to original bug (#101036)

Description

I've tested this on weston and on my own toy WM, so I guess this is a bug in libweston. When I open chrome or chromium, they are not decorated by the WM(which is fine). However, their "custom" buttons for maximization don't work. In other Xwayland views, the maximize button on the frames drawn by weston are working fine. So my guess is that the maximize request from Xwayland isn't implemented in XWM.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking