What we do and don't expose to client toolkits

[Alan Griffiths]

On 01/09/16 12:02, Alan Griffiths wrote:
>
>
> Thoughts and suggestions for the right way forward please.
>

A data point from Wayland
(https://cgit.freedesktop.org/wayland/wayland-protocols/tree/unstable/xdg-shell/xdg-shell-unstable-v6.xml#n1018):

    <event name="configure">
      <description summary="configure the popup surface">
    This event asks the popup surface to configure itself given the
    configuration. The configured state should not be applied immediately.
    See xdg_surface.configure for details.

    The x and y arguments represent the position the popup was placed at
    given the xdg_positioner rule, relative to the upper left corner of the
    window geometry of the parent surface.
      </description>
      <arg name="x" type="int"
       summary="x position relative to parent surface window geometry"/>
      <arg name="y" type="int"
       summary="y position relative to parent surface window geometry"/>
      <arg name="width" type="int" summary="window geometry width"/>
      <arg name="height" type="int" summary="window geometry height"/>
    </event>

So (in their current "unstable" anyway) they are returning the relative
placement. And running the risk of sneaky clients probing the display
boundaries.

I claim this as "prior art" and propose that we do the same by sending a
MirRectangle notification.

Any objections before the weekend please.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20160902/bb25bbca/attachment.html>