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
I am trying to use the SettingsEditor returned from workbench.openSettings(), but subsequent function calls on the settings editor instance don't appear to be run against the open setting page.
The call to switchToPerspective is failing with Can't call click on element with selector ".//a[@title='Workspace']" because element wasn't found.
I am also using the function await editor.findSetting(myTitle, myCategory); Observing the workspace, with settings open as well as Enabled Extensions, I can see the text for then find written into the search input area for EnabledExtensions.
Am I using the interfaces correctly?
The text was updated successfully, but these errors were encountered:
petehale
changed the title
SettingEditor function don't appear to be working properly
SettingsEditor functions don't appear to be working properly
Jul 10, 2024
I think the selector being used in switchToPerspective is incorrect. With settings open, searching for .//a[@title='Workspace'] yields 0 while .//a[text()='Workspace'] yields 1.
I am trying to use the SettingsEditor returned from workbench.openSettings(), but subsequent function calls on the settings editor instance don't appear to be run against the open setting page.
This is the code I am using
The call to switchToPerspective is failing with
Can't call click on element with selector ".//a[@title='Workspace']" because element wasn't found
.I am also using the function
await editor.findSetting(myTitle, myCategory);
Observing the workspace, with settings open as well as Enabled Extensions, I can see the text for then find written into the search input area for EnabledExtensions.Am I using the interfaces correctly?
The text was updated successfully, but these errors were encountered: