ozone/wayland: Clarify flag usage in window drag controller

BUG=1148021
R=msisov@igalia.com

Change-Id: Id3d0a8c9ea41c421cd4ae633709372e12a77c2b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546980
Auto-Submit: Nick Yamane <nickdiego@igalia.com>
Commit-Queue: Maksim Sisov (GMT+2) <msisov@igalia.com>
Reviewed-by: Maksim Sisov (GMT+2) <msisov@igalia.com>
Cr-Commit-Position: refs/heads/master@{#829216}

ui/ozone/platform/wayland/host/wayland_window_drag_controller.h

@@ -153,8 +153,10 @@ class WaylandWindowDragController : public WaylandDataDevice::DragDelegate,
   std::unique_ptr<ScopedEventDispatcher> nested_dispatcher_;
   base::OnceClosure quit_loop_closure_;
 
-  // Tells if the current drag event should be processedc. E.g: received through
-  // wl_data_device::motion wayland event.
+  // Tells if the current drag event should be processed. Buggy compositors may
+  // send wl_pointer::motion events, for example, while a DND session is still
+  // in progress, which leads to issues in window dragging sessions, this flag
+  // is used to make window drag controller resistant to such scenarios.
   bool should_process_drag_event_ = false;
 
   base::WeakPtrFactory<WaylandWindowDragController> weak_factory_{this};