See this [document](https://docs.google.com/document/d/1mr9CZQKyZ_2pWUbOcO-0qOMCYrTenapipFL1cpMxSPo/edit?tab=t.lia8kngzl7c3#heading=h.4orukig2d4zl) for discussion. In an effort to cleanup tabs.js, we should move drag and drop code to a new module. This will hopefully cut down on some of some of the added complexity that was introduced when drag to pin logic was added recently and give us a space for adding more drag and drop logic required for upcoming split view work. We can address things like performance and potential reusability in follow-ups, so this task should only involve moving things out of tabs.js.
Bug 1980240 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
See this [document](https://docs.google.com/document/d/1mr9CZQKyZ_2pWUbOcO-0qOMCYrTenapipFL1cpMxSPo/edit?tab=t.lia8kngzl7c3#heading=h.4orukig2d4zl) for discussion. In an effort to cleanup `browser/components/tabbrowser/content/tabs.js`, we should move drag and drop code to a new module. This will hopefully cut down on some of some of the added complexity that was introduced when drag to pin logic was added recently and give us a space for adding more drag and drop logic required for upcoming split view work. We can address things like performance and potential reusability in follow-ups, so this task should only involve moving things out of tabs.js.
See this [document](https://docs.google.com/document/d/1mr9CZQKyZ_2pWUbOcO-0qOMCYrTenapipFL1cpMxSPo/edit?tab=t.lia8kngzl7c3#heading=h.4orukig2d4zl) for discussion. In an effort to cleanup `browser/components/tabbrowser/content/tabs.js`, we should move drag and drop code to a new module. This will hopefully cut down on some of some of the added complexity that was introduced when drag to pin logic was added recently and give us a space for adding more drag and drop logic required for upcoming split view work. We can address things like performance and potential reusability in follow-ups if needed, so this task should only involve moving things out of tabs.js.
See this [document](https://docs.google.com/document/d/1mr9CZQKyZ_2pWUbOcO-0qOMCYrTenapipFL1cpMxSPo/edit?tab=t.lia8kngzl7c3#heading=h.4orukig2d4zl) for discussion. In an effort to cleanup `browser/components/tabbrowser/content/tabs.js`, we should move drag and drop code to a new module. This will hopefully cut down on some of some of the added complexity that was introduced when drag to pin logic was added recently and give us a space for adding more drag and drop logic required for upcoming split view work. We can address things like performance and potential reusability in follow-ups if needed, so this task should only involve moving things out of `tabs.js`.