Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 553177 - Display issue in "Expressions" view when entering an expression
Summary: Display issue in "Expressions" view when entering an expression
Status: RESOLVED DUPLICATE of bug 550606
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-18 07:41 EST by Oliver Buchien CLA
Modified: 2019-11-18 08:13 EST (History)
2 users (show)

See Also:

Attachments
Config Listing (17.69 MB, text/plain)
2019-11-18 07:41 EST, Oliver Buchien CLA 		no flags Details
Screen Capture (112.11 KB, image/gif)
2019-11-18 07:41 EST, Oliver Buchien CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Buchien CLA 2019-11-18 07:41:00 EST 
Created attachment 280676 [details]
Config Listing

A display issue was introduced in the "Expression" view.
User is not able to see the entered text when entereing an expression manulally.

Step to reproduce:
 - Use "Add new expression"
 - In 4.12 an textinput field occures in name cell where the user can enter the expression
 - In 4.13 the "Add new expression" stays there and no text inputfield is visible 
 - The user can enter text but this text will not be display immediatily which is very inconvenient.

Please refer to attached .gif file where I tried to visualize the problem.

This issue occurs only on linux. Windows seems to finde. Mac I wasn't able to test.

I used GTK version 3.22.30. (s. attached config listing)
Comment 1 Oliver Buchien CLA 2019-11-18 07:41:57 EST 
Created attachment 280677 [details]
Screen Capture
Comment 2 Andrey Loskutov CLA 2019-11-18 07:59:33 EST 
Please try with 4.14 nightly, this should be fixed already (I believe, can't find the right bug).
Comment 3 Paul Pazderski CLA 2019-11-18 08:13:46 EST 

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