Bug 279492

Summary: [DataBinding] Tooltip value properties needs to escape ampersands
Product: [Eclipse Project] Platform Reporter: Remy Suen <remy.suen>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: bokowski, pwebster, qualidafial
Version: 3.5   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Remy Suen CLA 2009-06-08 12:37:13 EDT 
It seems the modelled workbench suffers from the same problem as bug 279461. You can see the problem if you just change the contacts' demo's xmi file's tooltip attribute's value from "Contacts List" to "Contacts &amp; List".

Class in question:
CTabItemTooltipTextProperty

Other casualties:
ControlTooltipTextProperty
TabItemTooltipTextProperty
TableColumnTooltipTextProperty
ToolItemTooltipTextProperty
TrayItemTooltipTextProperty
TreeColumnTooltipTextProperty
Comment 1 Matthew Hall CLA 2009-06-08 13:06:32 EDT 
Bug 279461 does not seem to be related
Comment 2 Remy Suen CLA 2009-06-08 13:07:35 EDT 
(In reply to comment #1)
> Bug 279461 does not seem to be related

Whoops, that oughta be bugs 279152.
Comment 3 Remy Suen CLA 2009-06-08 13:13:59 EDT 
There was some confusion since I said "modelled workbench" but the code in question is from the databinding bundles.

I'm curious as to whether we need to modify the getters too. If I pass in "A & B", will I get "A && B" back? o.O
Comment 4 Matthew Hall CLA 2009-06-08 13:16:54 EDT 
> I'm curious as to whether we need to modify the getters too. If I pass in "A &
> B", will I get "A && B" back? o.O

It should be escaped on set and unescaped on get.
Comment 5 Matthew Hall CLA 2009-06-29 11:17:53 EDT 
Should we fix this in 3.5.1 or in 3.6?  Technically this is a changing behavior, which might become a problem for people who introduce workarounds.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:03:51 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.