Closed Bug 671920 Opened 14 years ago Closed 4 months ago

Mail composition windows initially unresponsive while running Dreamweaver CS5.5 for Mac

Categories

(Thunderbird :: Message Compose Window, defect)

All
macOS
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: efridge, Unassigned)

References

()

Details

(Whiteboard: [gs])

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0.1) Gecko/20100101 Firefox/5.0.1 Build ID: 20110707182747 Steps to reproduce: I launched Thunderbird 5.0 for Mac. I was able to open a compose window and type. I then launched Dreamweaver CS5.5 (11.5) for Mac. I then clicked the "Write" button again. Actual results: The compose window opens but it's not editable. I clicked in the window but nothing happens. I dragged the window around and it became editable. When I quit Dreamweaver the windows became editable again. Expected results: The window should have been editable from the start.
Anything in Tools -> Error console ? Anything in console.app when this happens ?
Nothing in Error console other than a basic OpenGL message: OpenGL LayerManager Initialized Succesfully. Version: 2.1 ATI-1.6.36 Vendor: ATI Technologies Inc. Renderer: ATI Radeon HD 2400 XT OpenGL Engine FBO Texture Target: TEXTURE_2D Nothing in console.app.
E.L., Is only the the compose window affected? Does it also happen to firefox? Does it happen if you start TB in safe mode? http://support.mozillamessaging.com/en-US/kb/safe-mode
OS: Other → Mac OS X
Hi Wayne, Yes, the compose window is the only one affected. I haven't noticed this in Firefox (5.0). I restarted TB in safe mode and the window worked fine every time. So, I disabled the add-ons one by one and restarted TB each time. In each case, the first compose window appeared normally but the subsequent ones were still frozen. I wonder what else safe mode does besides disabling add-ons. I know my buttons on the toolbar were rearranged. Any other ideas? The bug seems like some sort of a redraw error. Moving the window around at all causes it to redraw and work properly. Also, I have been noticing some strange crashing in TB and Dreamweaver while firing them up one after another over and over. Each crashed about 3 times. Nothing consistent enough to identify a pattern, though. Thanks for the tips, E.L.
I think it also clears localstore.rdf - you might have a corrupt one. Try renaming it to old to see if it fixes your issue (and you'll loose your buttons and al).
Hello, I renamed this file and the problem still occurs. Here's an interesting thing I noticed, though. I tried to create a screen recording of the problem using QuickTime and the problem showed up - even though I wasn't using Dreamweaver. Even stranger, when I went back to watch the recording, it's as if the problem never happened. It's only what I'm seeing on the screen that is the trouble. Apparently what I am typing is making it into the editor, but I can't see it until I move the window. Here is a video recording of the problem I made so you can see what's going on. http://uwf.edu/efridge/tb_bug/bug_video.mov Thanks, E.L.
Try this link on youtube instead... http://www.youtube.com/watch?v=FDTmBJQ0CO4
Can you look on apple's support and see if there are drivers for your machine that you could update to ? (they don't always push these as automatic updates)
Blocks: 680655
(did a small sweep of gfsn and still only reported in one topic)
This appears related to Bug 682500
the same problem in firefox but only with the download window, if you click to clear list, all downloads are show until you move the download window, normal browser have no problems.
Same on Firefox 6.0.2 on Lion if you have Dreamweaver started, starting fullscreen in Firefox (cmd+shift+f), closing fullscreen (cmd+shift+f), if you now click any link you will not see the new site or changes until you move the window.
Severity: normal → S3

No reports in a decade and not seen any support requests, so I doubt this exists.

Status: UNCONFIRMED → RESOLVED
Closed: 4 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.