Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358579 - XML editor design tab gets out of sync with the source tab
Summary: XML editor design tab gets out of sync with the source tab
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: wst.xml (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: 3.3.2   Edit
Assignee: Nick Sandonato CLA
QA Contact: Nitin Dahyabhai CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-22 09:03 EDT by Walter Brunauer CLA
Modified: 2012-03-01 04:52 EST (History)
3 users (show)

See Also:

Attachments
patch (3.20 KB, patch)
2011-10-28 16:36 EDT, Nick Sandonato CLA 		no flags Details | Diff
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 Walter Brunauer CLA 2011-09-22 09:03:13 EDT 
Build Identifier: org.eclipse.wst.sse.ui_1.3.1.v201108191312

Doing changes to attributes, the design tab does not show the real values entered, whereas the source tab does. This happens as soon as the mouse is used to focus into another attribute, after the current attribute was changed but not committed with the return key. Starting with the second attribute, the value does not get updated any longer in the design tab. The value in the source tab is correct, though.

Reproducible: Always

Steps to Reproduce:
Open any XML file, change the first attribute value, then click into any other attribute field, change this again, and click into a third attribute field. Do not hit enter during this sequence.
Comment 1 Helmut J. Haigermoser CLA 2011-09-22 10:13:38 EDT 
CQ:WIND00303346
Comment 2 Nick Sandonato CLA 2011-10-28 16:36:31 EDT 
Created attachment 206155 [details]
patch

This seems to be a result of the changes from Bug 324409. We had to make the changes within an aboutToChangeModel, but if a refresh job runs again while editing a field, it will cancel the editor before firing changedModel. This leaves the internal state count of the model > 1, so no notifications are sent to cause another refresh.
Comment 3 Nick Sandonato CLA 2011-10-28 16:36:49 EDT 
Code checked in for 3_3_Maintenance and HEAD.
Comment 4 Helmut J. Haigermoser CLA 2011-10-31 06:34:09 EDT 
(In reply to comment #3)
> Code checked in for 3_3_Maintenance and HEAD.

Thanks Nick! :)
It will be some time till we pick this fix up in our product, will report back once we can verify the fix! :)
Helmut
Comment 5 Martin Oberhuber CLA 2012-03-01 04:52:53 EST 
(In reply to comment #1)
> CQ:WIND00303346

Correction - CQ:WIND00306346