Poly authored 1 year ago and Poly committed 1 year ago

Fix double "should" in ext-foreign-toplevel-list-v1

Signed-off-by: Bartłomiej Maryńczak <marynczakbartlomiej@gmail.com>

David Redondo authored 1 year ago and Vlad Zahorodnii committed 1 year ago

This protocol allows applications to request that a window is moved
at the same time as a drag operation - effectively dragging windows.
With this features such as detaching a tab from a window and reattaching
it, dragging tabs between windows or (un)dockable tool windows can
be implemented.
Based on the previously proposed extended drag protocol but trimmed
down.

Signed-off-by: David Redondo <kde@david-redondo.de>

Signed-off-by: Daniel Stone <daniels@collabora.com>

Upgrade Debian to bookworm and ci-templates to the latest commit.

Signed-off-by: Simon Ser <contact@emersion.fr>

Jonas Ådahl authored 1 year ago and Simon Ser committed 1 year ago

xdg-shell assumes that the client provides all parts of a toplevel
window, i.e. things like titlebar, drop shadow. There are already things
here and there implies it, but it could be helpful to spell it out.

This doesn't change any semantics - it's still valid, from the
perspective of the protocol, to create a toplevel without any
decorations, and it always has been, it just means that the semantical
intention is for them to be exactly so.

Signed-off-by: Jonas Ådahl <jadahl@gmail.com>

Signed-off-by: Max Verevkin <maxxverrr@gmail.com>

Simon Ser authored 1 year ago and Daniel Stone committed 1 year ago

wayland-protocols is more than just a repository of XML files.
Make this clear and link to the governance document and member
list.

Signed-off-by: Simon Ser <contact@emersion.fr>

Simon Ser authored 1 year ago and Daniel Stone committed 1 year ago

The kernel enforces this. Accepting a separate modifier per-plane is
an historical artifact.

Signed-off-by: Simon Ser <contact@emersion.fr>
Closes: #29

Simon Ser authored 1 year ago and Daniel Stone committed 1 year ago

With the new rules, we always keep the major version, even for
stable protocols.

Signed-off-by: Simon Ser <contact@emersion.fr>

Signed-off-by: Lleyton Gray <lleyton@fyralabs.com>

clock_gettime() has nothing Linux/glibc-specific.

Signed-off-by: Simon Ser <contact@emersion.fr>

Sebastian Wick authored 1 year ago and Simon Ser committed 1 year ago

Specifically this also changes the well-known name for flatpak from
"flatpak" to "org.flatpak". This would be a breaking change but there is
no released version of flatpak yet with security-context support.

Signed-off-by: Sebastian Wick <sebastian.wick@redhat.com>

"ask the client" isn't very clear. Let's use the word "configure"
which is more explicit: the client doesn't have a say in this.
(Note, wording in the following paragraphs is clearer and uses the
word "must".)

Signed-off-by: Simon Ser <contact@emersion.fr>

This was probably carried over from an early draft of the protocol.
This event is not a suggestion as the full description explains:
the client must ack it.

Signed-off-by: Simon Ser <contact@emersion.fr>

Signed-off-by: Vaxry <vaxry@vaxry.net>

Signed-off-by: Vaxry <vaxry@vaxry.net>

This protocol extension is ubiquitous. It's time to mark it as
stable.

The interface names are left unchanged, so that compositors and
clients don't need to be updated. In particular, the legacy "z"
prefix is still part of the interface name.

Signed-off-by: Simon Ser <contact@emersion.fr>

Stable protocols used to not have a version. But with the new
rules, they have one. Accomodate the build script for the new
rules.

Signed-off-by: Simon Ser <contact@emersion.fr>

Instead of iterating on the keys and then using get(), iterate on
both keys and values.

Signed-off-by: Simon Ser <contact@emersion.fr>

Signed-off-by: Andri Yngvason <andri@yngvason.is>

Simon Ser authored 1 year ago and Daniel Stone committed 1 year ago

EFL/Enlightenment hasn't been active in a while, doesn't seem to
have interest in the near future, and Mike is fine with ceasing
their membership. They can always be added back when interest
sparks again.

Signed-off-by: Simon Ser <contact@emersion.fr>
Closes: wayland/wayland-protocols#146

Make it clear that implicit sync is the expectation without another
protocol extension.

Signed-off-by: Simon Ser <contact@emersion.fr>

Sebastian Wick authored 1 year ago and Sebastian Wick committed 1 year ago

Specifically that after calling create_listener the only valid operation
on the sockets is to close them. They also must stay open and valid
until a round-trip after the call.

Signed-off-by: Sebastian Wick <sebastian.wick@redhat.com>

and specify when the invalid_metadata error will be sent.

Signed-off-by: Sebastian Wick <sebastian.wick@redhat.com>

Signed-off-by: Jonas Ådahl <jadahl@gmail.com>

Kirill Chibisov authored 1 year ago and Simon Ser committed 1 year ago

Clarify how and when initial wl_surface state provided by the core
protocol or by extensions to the wl_surface, like as
wp_fractional_scale_v1, is being delivered.

The motivation for such change is to make it clear that the first frame
for xdg-shell will be perfect, which implies that scaling and similar
properties affecting presentation would be delivered in time.

Signed-off-by: Kirill Chibisov <contact@kchibisov.com>

David Redondo authored 1 year ago and Simon Ser committed 1 year ago

Signed-off-by: David Redondo <kde@david-redondo.de>

This is a variation of the unveil protocol I suggested in the Weston
issue about security contexts. This lets sandbox engines such as Flatpak
attach a security context to sandboxed clients. The compositor can then
restrict which features are made available to that client.

The protocol is designed around the assumption that the sandbox engine
uses this protocol when setting up the sandboxed application. After this
inital setup, the sandbox engine isn't necessarily running anymore.
For this reason, a special "close FD" is used to indicate when to stop
the security context listener: the sandbox engine can leak the FD into
the sandboxed app's process, and the OS will automatically close the FD
when the sandboxed app exits.

Signed-off-by: Simon Ser <contact@emersion.fr>
References: weston#206

Add a toplevel state to indicate that surface repaints have been
suspended. This may arise due to occlusion, output power state, etc.

In this state, clients can choose to take meaningful action such as
suspending any processing which would drive a repaint loop, or
communicating to the active browser tab that the tab is not
system-visible, or any other action that would be taken by a client not
expecting to repaint until further notice.

cf. discussion in !99

Signed-off-by: Daniel Stone <daniels@collabora.com>

Signed-off-by: Xaver Hugl <xaver.hugl@gmail.com>

This allows developers to work on a new wayland-scanner feature and
test it with wayland-protocols without too much hassle.

Depends on wayland!313



Signed-off-by: Simon Ser <contact@emersion.fr>

This is based on the Chromium protocol [1].

[1]: https://chromium.googlesource.com/chromium/src/+/main/third_party/wayland-protocols/unstable/cursor-shapes/cursor-shapes-unstable-v1.xml



Signed-off-by: Simon Ser <contact@emersion.fr>
Closes: #58
References: !21

This should fix the following problem when I targeted a MR to
branch 'color' in Sebastian's fork of wayland-protocols:

$ ci-fairy check-commits --signed-off-by --junit-xml=results.xml
Traceback (most recent call last):
  File "/usr/bin/ci-fairy", line 33, in <module>
    sys.exit(load_entry_point('ci-fairy==0.1', 'console_scripts', 'ci-fairy')())
  File "/usr/lib/python3.9/site-packages/click/core.py", line 1137, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/click/core.py", line 1062, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3.9/site-packages/click/core.py", line 1668, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3.9/site-packages/click/core.py", line 763, in invoke
    return __callback(*args, **kwargs)
  File "/usr/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3.9/site-packages/ci_fairy.py", line 1335, in check_commits
    for commit in repo.iter_commits(commit_range):
  File "/usr/lib/python3.9/site-packages/git/objects/commit.py", line 318, in _iter_from_process_or_stream
    finalize_process(proc_or_stream)
  File "/usr/lib/python3.9/site-packages/git/util.py", line 370, in finalize_process
    proc.wait(**kwargs)
  File "/usr/lib/python3.9/site-packages/git/cmd.py", line 447, in wait
    raise GitCommandError(remove_password_if_present(self.args), status, errstr)
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git rev-list cifairy/color..HEAD --
  stderr: 'fatal: bad revision 'cifairy/color..HEAD'
'

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>

This interface has no "enter" event. This was likely copy-pasted
from wl_pointer.set_cursor.

The event which indicates focus is proximity_in.

Signed-off-by: Simon Ser <contact@emersion.fr>

We merged a commit by mistake which doesn't have S-o-b. ci-fairy is
unhappy about it and will fail the check. Skip it if we aren't
running in a merge request context.

Signed-off-by: Simon Ser <contact@emersion.fr>

Simon Ser authored 1 year ago and Daniel Stone committed 1 year ago

See [1], required to allow contributors to trigger CI pipelines
for MRs. Example failure can be found at [2].

[1]: freedesktop/freedesktop#540
[2]: https://gitlab.freedesktop.org/i509VCB/wayland-protocols/-/jobs/40117393



Signed-off-by: Simon Ser <contact@emersion.fr>

There are no interfaces such as zlinux_dmabuf_params and zlinux_buffer_params.

Signed-off-by: Vlad Zahorodnii <vlad.zahorodnii@kde.org>

Jonas Ådahl authored 1 year ago and Simon Ser committed 1 year ago

The xdg_surface window geometry can extend outside the base wl_surface
to e.g. accompany subsurfaces that extend outside it but is part of the
window itself. Spell out this bit explicitly.

Signed-off-by: Jonas Ådahl <jadahl@gmail.com>

Jonas Ådahl authored 4 years ago and Simon Ser committed 1 year ago

The spec says that

	When applied, the effective window geometry will be the set
	window geometry clamped to the bounding rectangle of the combined
	geometry of the surface of the xdg_surface and the associated
	subsurfaces.

Thus, a client cannot assume the geometry will adapt to any subsequent
changes to any conditions that constrained the geometry.

Signed-off-by: Jonas Ådahl <jadahl@gmail.com>