Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 551404

Summary: "Add new expression" in Debug perspective does not display the input field when clicked
Product: [Eclipse Project] Platform Reporter: Javier Cruz <mjcves>
Component: SWTAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: ericwill, h2obrain, jonah, loskutov, mjcves, sarika.sinha, taro_k
Version: 4.12   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Screenshot from version 2019-06
none
Eclipse 2019-09 Installation details
none
Video Showing the issue none

Description Javier Cruz CLA 2019-09-24 06:39:28 EDT
Created attachment 279999 [details]
Screenshot from version 2019-06

In the previous version, when you click in "Add new expression" in the Debug perspective, an input field appeared where you could write the expression, with the new version, this is not displayed, and after you click in "Add new expression" and type something, when click again, is displayed as an expression. The only way to correctly write something is using the right click over "Add new expression" and type in the popup
Comment 1 Javier Cruz CLA 2019-09-24 06:49:30 EDT
Created attachment 280000 [details]
Eclipse 2019-09 Installation details
Comment 2 Javier Cruz CLA 2019-09-24 06:50:54 EDT
It has been tested with a version update from 2019-06 and a clean version of 2019-09 downloaded from the eclipse site, in both cases the same behaviour
Comment 3 Andrey Loskutov CLA 2019-09-24 07:08:26 EDT
(In reply to Javier Cruz from comment #0)
> Created attachment 279999 [details]
> Screenshot from version 2019-06
> 
> In the previous version, when you click in "Add new expression" in the Debug
> perspective, an input field appeared where you could write the expression,
> with the new version, this is not displayed, and after you click in "Add new
> expression" and type something, when click again, is displayed as an
> expression. The only way to correctly write something is using the right
> click over "Add new expression" and type in the popup

Sorry, I can't follow. What exact is missing, and what do you see instead?
Comment 4 Javier Cruz CLA 2019-10-06 10:18:37 EDT
Sorry if I didn't explained it clearly, let's go step by step:
- You go to the Debug perspective
- Open the Debug -> Expressions view
- When empty you see "+ Add new expression"

Expected behaviour (as in previous version):

- When you click in "+ Add new expression" appears an input field where you can write the expression you want to evaluate while debugging.

Actual behaviour:
- When you click in "+ Add new expression" does not appears input field, if you type anything, you don't see it, but if you click in any empty area, what you typed appears, and you cannot edit it clicking over it.

I hope this clarifies the issue
Comment 5 Javier Cruz CLA 2019-10-06 10:19:48 EDT
(In reply to Andrey Loskutov from comment #3)
> (In reply to Javier Cruz from comment #0)
> > Created attachment 279999 [details]
> > Screenshot from version 2019-06
> > 
> > In the previous version, when you click in "Add new expression" in the Debug
> > perspective, an input field appeared where you could write the expression,
> > with the new version, this is not displayed, and after you click in "Add new
> > expression" and type something, when click again, is displayed as an
> > expression. The only way to correctly write something is using the right
> > click over "Add new expression" and type in the popup
> 
> Sorry, I can't follow. What exact is missing, and what do you see instead?

Sorry if I didn't explained it clearly, let's go step by step:
- You go to the Debug perspective
- Open the Debug -> Expressions view
- When empty you see "+ Add new expression"

Expected behaviour (as in previous version):

- When you click in "+ Add new expression" appears an input field where you can write the expression you want to evaluate while debugging.

Actual behaviour:
- When you click in "+ Add new expression" does not appears input field, if you type anything, you don't see it, but if you click in any empty area, what you typed appears, and you cannot edit it clicking over it.

I hope this clarifies the issue
Comment 6 Andrey Loskutov CLA 2019-10-06 10:26:46 EDT
From attachment :

org.eclipse.swt.internal.deviceZoom=100
org.eclipse.swt.internal.gdk.backend=x11
org.eclipse.swt.internal.gtk.theme=Adwaita
org.eclipse.swt.internal.gtk.version=3.24.1
org.eclipse.swt.internal.webkitgtk.version=2.24.4

If this would be older GTK I would say it is the (old) inline table editing bug.

Sounds like SWT issue.
Comment 7 Javier Cruz CLA 2019-10-06 10:56:41 EDT
Created attachment 280176 [details]
Video Showing the issue
Comment 8 Javier Cruz CLA 2019-10-06 10:59:30 EDT
(In reply to Andrey Loskutov from comment #6)
> From attachment :
> 
> org.eclipse.swt.internal.deviceZoom=100
> org.eclipse.swt.internal.gdk.backend=x11
> org.eclipse.swt.internal.gtk.theme=Adwaita
> org.eclipse.swt.internal.gtk.version=3.24.1
> org.eclipse.swt.internal.webkitgtk.version=2.24.4
> 
> If this would be older GTK I would say it is the (old) inline table editing
> bug.
> 
> Sounds like SWT issue.

The weird thing is that in the previous version it worked fine, shouldn't have been fixed, or has been reintroduced?
Comment 9 Andrey Loskutov CLA 2019-10-06 11:05:35 EDT
(In reply to Javier Cruz from comment #8)
> 
> The weird thing is that in the previous version it worked fine, shouldn't
> have been fixed, or has been reintroduced?

In which version it worked fine?
Comment 10 Javier Cruz CLA 2019-10-06 11:21:44 EDT
In version 2019-06 was working fine, it was after the upgrade to 2019-09 that it started happening(In reply to Andrey Loskutov from comment #9)
> (In reply to Javier Cruz from comment #8)
> > 
> > The weird thing is that in the previous version it worked fine, shouldn't
> > have been fixed, or has been reintroduced?
> 
> In which version it worked fine?

In version 2019-06 was working fine, it was after the upgrade to 2019-09 that it started happening
Comment 11 Javier Cruz CLA 2019-10-06 11:23:13 EDT
(In reply to Javier Cruz from comment #10)
> In version 2019-06 was working fine, it was after the upgrade to 2019-09
> that it started happening(In reply to Andrey Loskutov from comment #9)
> > (In reply to Javier Cruz from comment #8)
> > > 
> > > The weird thing is that in the previous version it worked fine, shouldn't
> > > have been fixed, or has been reintroduced?
> > 
> > In which version it worked fine?
> 
> In version 2019-06 was working fine, it was after the upgrade to 2019-09
> that it started happening

Just to clarify (I put it in another comment before), I tried with a clean downloaded version and with an upgraded version, in both cases with the same error.
Comment 12 Andrey Loskutov CLA 2019-10-07 05:32:59 EDT
Can't reproduce on GTK 3.22.30 / RHEL 7.4.

Eric: can you check on 3.24.1?
Comment 13 Eric Williams CLA 2019-10-07 11:13:21 EDT
Sounds like a duplicate of bug 550606.
Comment 14 Javier Cruz CLA 2019-10-07 12:22:25 EDT
(In reply to Andrey Loskutov from comment #12)
> Can't reproduce on GTK 3.22.30 / RHEL 7.4.
> 
> Eric: can you check on 3.24.1?

Hi Andrey, I had the issue with Fedora 29 and Fedora 30, if that can help
Comment 15 Taro Kyo CLA 2019-10-14 17:28:30 EDT
Eclipse 2019-09, version 4.13 stable, using Ubuntu 18.04 LTS. Same issue with the Expressions view pane
Comment 16 Sarika Sinha CLA 2019-10-15 00:48:06 EDT
@Eric,
Can you see if this needs a separate fix?
Comment 17 Oliver Meier CLA 2019-10-16 04:13:38 EDT
*** Bug 551940 has been marked as a duplicate of this bug. ***
Comment 18 Eric Williams CLA 2019-10-16 14:37:11 EDT
(In reply to Sarika Sinha from comment #16)
> @Eric,
> Can you see if this needs a separate fix?

I believe this is a duplicate of bug 550606, which was fixed in 4.14 M1. If the issue does not reproduce on 4.14 M1 then I suggest this ticket be closed as a duplicate of bug 550606.
Comment 19 Javier Cruz CLA 2019-10-21 04:23:27 EDT
(In reply to Eric Williams from comment #18)
> (In reply to Sarika Sinha from comment #16)
> > @Eric,
> > Can you see if this needs a separate fix?
> 
> I believe this is a duplicate of bug 550606, which was fixed in 4.14 M1. If
> the issue does not reproduce on 4.14 M1 then I suggest this ticket be closed
> as a duplicate of bug 550606.

Hi Eric, I downloaded the 4.14 M1 and tested it, it seems to be fixed in that version
Comment 20 Sarika Sinha CLA 2019-10-21 04:40:09 EDT
Thanks for confirming!

*** This bug has been marked as a duplicate of bug 550606 ***