Bugzilla – Full Text Bug Listing
| Summary: | visual artifacts after renaming project containing target of unfocused xml editor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Reuben Garrett <ReubenGarrett> | ||||
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | remy.suen, ReubenGarrett, satyam.kandula | ||||
| Version: | 4.2 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Reuben Garrett
Created attachment 208857 [details]
visual artifacts
apologies, I should have attached the stacktrace instead of inlining. (In reply to comment #0) > after renaming the project root folder containing a file open in an unfocused > xml editor, the view ungracefully fails to refresh. Did you restart Eclipse at all or is this the same Eclipse session? same Eclipse session - cleared after restart. not a major bug for that reason, but it would be nice for the view to be gracefully re-connected to the file after refactoring. (In reply to comment #4) > same Eclipse session - cleared after restart. not a major bug for that reason, Based on your stack trace the editor was never created. Did you click on that tab when you opened Eclipse or was it in the background the entire time? (In reply to comment #5) > Did you click on that tab when you opened Eclipse or was it in the background the entire time? it's distant for me to recall - but for that file, it's likely that I left it open in the background between sessions. (In reply to comment #6) > (In reply to comment #5) > > Did you click on that tab when you opened Eclipse or was it in the background the entire time? > > it's distant for me to recall - but for that file, it's likely that I left it > open in the background between sessions. If you never opened the editor then it's probably similar to bug 41431. (In reply to comment #7) > If you never opened the editor then it's probably similar to bug 41431. I'm okay to correlate/close as a duplicate if you believe they're related to the same root cause. If the error should recur for me, I'll capture better information on the context to facilitate troubleshooting. 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. If the bug is still relevant, please remove the "stalebug" whiteboard tag. |