| Summary: | Only persist DisplayView contents on view closure | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jared Burns <jared_burns> | ||||
| Component: | Debug | Assignee: | Darin Wright <darin.eclipse> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | darin.eclipse | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | 3.1 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 65606 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Jared Burns
Bug 60039 was fixed, but there's a problem with the implementation (bug 65606) that prevents us from using the feature. Created attachment 11562 [details]
DisplayView.62200.patch
This patch implements the change from our end. Will release once the UI bug is
fixed.
Now that bug 65606 has been fixed, the attached patch functions correctly and can be released for RC3. Jared, although this is a "nice to fix" bug, I see no reason that this has to be fixed for 3.0. There is no change in behavior to the user, and no user information is lost without the fix. Is this correct? Removing RC3 target, as I don't believe this bug is critical. The code in HEAD was released last month with the knowledge that it was wrong. We've just been waiting for bug 65606 to get fixed. I don't like the idea of knowingly shipping the wrong code when we have the right code available, but the performance problem here isn't critical. Deferred. open for 3.1 Fixed in DisplayView. Please verify, DW. Verified |