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

Bug 361151

Summary:	Error: invalid to assign null to the non-nullable operand in 4 widgets
Product:	z_Archived	Reporter:	broy2
Component:	EDT	Assignee:	Huang Ji Yong <hjiyong>
Status:	CLOSED FIXED	QA Contact:
Severity:	major
Priority:	P1	CC:	hjiyong, svihovec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description broy2

2011-10-17 10:49:44 EDT

I'm on the 201110170901 install build.

Create a new RUI project which imports org.eclipse.edt.rui.widgets_0.7.0.
There are errors on TextArea, Tooltip, Password Text Field, and TextField.

IWN.VAL.6757.e 130/4 TextArea - It is invalid to assign null to the non-nullable operand backgroundColor. At line 130 in file \org.eclipse.edt.rui.widgets_0.7.0\EGLSource\org\eclipse\edt\rui\widgets\TextArea.egl	

IWN.VAL.6757.e 22/2 Tooltip - It is invalid to assign null to the non-nullable operand text. At line 22 in file \org.eclipse.edt.rui.widgets_0.7.0\EGLSource\org\eclipse\edt\rui\widgets\Tooltip.egl	

IWN.VAL.6757.e 77/4 PasswordTextField - It is invalid to assign null to the non-nullable operand backgroundColor. At line 77 in file \org.eclipse.edt.rui.widgets_0.7.0\EGLSource\org\eclipse\edt\rui\widgets\PasswordTextField.egl	

IWN.VAL.6757.e 99/4 TextField - It is invalid to assign null to the non-nullable operand backgroundColor. At line 99 in file \org.eclipse.edt.rui.widgets_0.7.0\EGLSource\org\eclipse\edt\rui\widgets\TextField.egl

Comment 1 Huang Ji Yong

2011-10-17 22:22:22 EDT

This bug is happened because the language change between EDT and RBD. The compiler  may just add support for the changes, so that compile error is shown.

Comment 2 broy2

2011-10-18 10:29:49 EDT

Verified in 20111018 build.

Comment 3 Brian Svihovec

2011-10-18 22:16:32 EDT

Ji Yong,

I made similar changes in my own workspace (e.g. convert 'null' to ""), but I did not have a chance to test the runtime behavior in all browsers.  When 'setReadOnly' is invoked for these 4 widgets, does setting the background to "" instead of 'null' have the same behavior at runtime?

Comment 4 Huang Ji Yong

2011-10-19 01:26:41 EDT

(In reply to comment #3)
> Ji Yong,
> 
> I made similar changes in my own workspace (e.g. convert 'null' to ""), but I
> did not have a chance to test the runtime behavior in all browsers.  When
> 'setReadOnly' is invoked for these 4 widgets, does setting the background to ""
> instead of 'null' have the same behavior at runtime?

I test in IE 6/7/8,9, FF 3.6/7.0 and chrome, the behavior is the same.