-
Notifications
You must be signed in to change notification settings - Fork 17.4k
PaneItem onDidTerminatePendingState is ignored unless onDidDestroy is defined #17535
Comments
Ah! This is probably why I've always been unable to double-click PDF files ( |
@smashwilson: It sounds to me like we want to treat both
Does that sound right to you? |
Yah, that's exactly what I would expect. I didn't see any reason why the two should be bound together as they are. If I missed something, we should at least amend the Workspace docs to note this. Also: the Workspace "Required Methods" section where these should be documented appears to be broken 😅 |
@smashwilson: Thanks for pointing this out. I've opened #17746 to track this issue. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
Prerequisites
Description
When implementing a PaneItem that's intended to be opened as pending, defining
onDidTerminatePendingState()
is insufficient - you need to implementonDidDestroy()
as well.atom/src/pane.js
Lines 617 to 626 in e2c89b2
Steps to Reproduce
onDidTerminatePendingState
but notonDidDestroy
.workspace.open(..., {pending: true})
.Expected behavior: The item should terminate its pending state and become a non-pending item.
Actual behavior: The item remains as a pending item.
Reproduces how often: 100%
Versions
Additional Information
Interestingly, choosing "Keep pending tab" from the context menu on the tab works correctly.
The text was updated successfully, but these errors were encountered: