You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version boundary and source links are useful, but the actual exception text and extension environment are needed to identify the regression. Could you provide a minimal component, Chrome/extension version, and whether the draggable node lives in the extension page, popup, or content-script DOM? Testing bounds="body" when ownerDocument.body differs from the global document would be a focused compatibility case.
The regression is between 4.4.6 and 4.5.0, with bounds="body".
In current source, bounds resolves against node.ownerDocument and ownerDocument.defaultView, so a content script whose DOM differs from the global document is the likely suspect.
Activity
hiSandog commentedon Jul 18, 2026
The version boundary and source links are useful, but the actual exception text and extension environment are needed to identify the regression. Could you provide a minimal component, Chrome/extension version, and whether the draggable node lives in the extension page, popup, or content-script DOM? Testing
bounds="body"whenownerDocument.bodydiffers from the global document would be a focused compatibility case.STRML commentedon Sep 27, 2026
Triage Notes
What we've established so far:
bounds="body".boundsresolves againstnode.ownerDocumentandownerDocument.defaultView, so a content script whose DOM differs from the globaldocumentis the likely suspect.What we still need from you (@LengYXin):