Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gtk4. Pick up PR#2836 #2927

Merged
merged 6 commits into from
Feb 19, 2024
Merged

Gtk4. Pick up PR#2836 #2927

merged 6 commits into from
Feb 19, 2024

Conversation

LukashonakV
Copy link
Contributor

Hi @Alexays , @alebastr . Just picked up Require gtk-layer-shell #2836 into gtk4 branch

BREAKING CHANGE: gtk-layer-shell is now required and unconditionally
used. The corresponding config option is removed.

As a part of preparation for future versions of GTK, remove an ability
to use wlr-layer-shell directly. The APIs it required were dropped in
GTK4, and with the menus/tooltips positioning issue being practically
unsolvable it doesn't make sense to keep maintaining the code.
Ensure that the position and the corresponding CSS class on window are
always set.
Previously, the only way to select all the module labels was with the
following kind of selector:
```css
.modules-left > widget > label,
.modules-center > widget > label,
.modules-right > widget > label {
    /* ... */
}
```
(and a matching block for the `box` containers).

Now, this can be expressed as
```css
label.module, box.module {
    /* ... */
}
```
`string_view` leads to UAF when reading custom mode definitions from the
configuration.
With only one implementation left, the abstraction is no longer
necessary.
@Alexays Alexays merged commit b54e2c1 into Alexays:gtk4 Feb 19, 2024
0 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants