-
Notifications
You must be signed in to change notification settings - Fork 27.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug Dropdown: New items added can have hover select disabled #46011
Comments
@isidorn |
@cleidigh thanks for looking into this. I can review the PR once it is ready. |
@elucidsoft |
One thing I left out that I should have mentioned is I also have
configurations spanning mutiple workspaces. This issue was in a single
workspace, however I have multiple configs which it merges together.
…On Tue, Mar 20, 2018, 12:00 AM Christopher Leidigh ***@***.***> wrote:
@elucidsoft <https://github.com/elucidsoft>
I was able to partially reproduce your issue. While I did not have a
problem with two debug configurations with the same name, I did see the
hover issue. It it appears that you can still select the item with the
keyboard so it's actually probably a misplaced disable class within the
CSS. It is also still possibly related to another index problem with a
twist on the results. StayTuned.
[image: image]
<https://user-images.githubusercontent.com/25272315/37635351-7e105f58-2bd1-11e8-9b7c-87146c541900.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46011 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANRUBosX7t9XRnbrEufcH3_Xc687qvUks5tgH69gaJpZM4Suotj>
.
|
@elucidsoft |
I do not currently, but I can, I'll check it after the merge and let you
know.
…On Sat, Mar 24, 2018, 12:49 AM Christopher Leidigh ***@***.***> wrote:
@elucidsoft <https://github.com/elucidsoft>
cc: @isidorn <https://github.com/isidorn>
I can reproduce this in several ways. It appears to be an odd "sticky"
class label within the list. I have a fix , I would consider the work
around. I will commit tomorrow with comments to at least avoid the problem
for now. @elucidsoft <https://github.com/elucidsoft> do you use insiders
to check after I merge?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#46011 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANRUF6giWsjez5rPdGmksnFWlNRX1vBks5thdA_gaJpZM4Suotj>
.
|
@elucidsoft |
Steps to Reproduce:
{ "type": "node", "request": "launch", "name": "Stuff", "program": "${workspaceFolder}\\Stuff\\run.js" },
{ "type": "node", "request": "launch", "name": "Stuff", "program": "${workspaceFolder}\\Stuff2\\run.js" },
{ "type": "node", "request": "launch", "name": "Stuff2", "program": "${workspaceFolder}\\Stuff2\\run.js" },
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: