XdndProxy not handled correctly |
|||||||
Issue descriptionThe XDND specification [1] states that XdndProxy indicates the window that must be checked for XdndAware, and must receive XDND messages. We implement this behavior correctly. However, the specification also says that the window field in the messages must indicate the window that the cursor points to (the original window whose XdndProxy we followed). We always set the window field to the receiver of the XDND messages. Writing the correct code isn't too hard, but finding a test is non-trivial. According to [2], XdndProxy only seems to be used to accept drops on the root window in an X system. A couple of quick searches haven't been able to identify a real-life application where this bug could be observed. [1] https://freedesktop.org/wiki/Specifications/XDND/ [2] https://www.acc.umu.se/~vatten/drop_on_root.html
,
Oct 2 2016
,
Oct 2 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 3 2017
,
Oct 3
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 3
+huangdarwin
,
Oct 3
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by pwnall@chromium.org
, Sep 30 2016