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 description web view uses the non-preview mode of the editor tab and the file changes use the preview mode.
Say I have the description page open, then I click on one of the files to see the diff open in a new editor. When returning to the description page (that is already open), it is blank and there is a considerable lag in populating the page when the machine is seeing a high CPU usage
An already open tab gives the perception that all data for that editor is already loaded and we are just switching back and forth (even though thats not the case based on our implementation).
I would suggest that the PR description page also use the preview mode. This would solve the perception problem
The text was updated successfully, but these errors were encountered:
Testing microsoft/vscode#55396 on Ubuntu
The description web view uses the non-preview mode of the editor tab and the file changes use the preview mode.
Say I have the description page open, then I click on one of the files to see the diff open in a new editor. When returning to the description page (that is already open), it is blank and there is a considerable lag in populating the page when the machine is seeing a high CPU usage
An already open tab gives the perception that all data for that editor is already loaded and we are just switching back and forth (even though thats not the case based on our implementation).
I would suggest that the PR description page also use the preview mode. This would solve the perception problem
The text was updated successfully, but these errors were encountered: