Closed Bug 198473 Opened 23 years ago Closed 23 years ago

Shift+return error in Dreamweaver MX when running Camino

Categories

(Camino Graveyard :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: rob, Assigned: saari)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030306 Camino/0.7 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.0.1) Gecko/20030306 Camino/0.7 I use Camino as my web development browser (despite not being able to use the Preview function!) and I have discovered that when Camino is running, the Shift+Return keystroke in Dreamweaver MX seems to be disabled, which of course is an important keystroke for inserting a <BR>. Reproducible: Always Steps to Reproduce: 1. Quit all other programs. 2. Run Dreamweaver MX 3. Open a new document and confirm that Shift+Return WILL insert a <BR> 4. Now run Camino 0.7 5. Return to Dreamweaver and confirm that Shift+Return is affected/disabled. Actual Results: Dreamweaver appears to ignore the Shift keystroke and adds a <P> as if only Return had been pressed. Expected Results: In Dreamweaver, the Shift+Return keystroke should enter a Line Break. I have been using Chimera/Camino for some time and just noticed this bug in the lastest 0.7 download.
Robert, since the application demonstrating the problem is Dreamweaver rather than Camino, it would probably be best if you contact Macromedia about the problem first, and follow up here afterwards.
Summary: shift+return error in dreamweaver MX when running camino → Shift+return error in Dreamweaver MX when running Camino
hi greg,well, i suppose that's sound advice... although i suspect that macromedia will respond with exactly the same comment! :)in my three or four years of using dreamweaver with the dozens of versions of new browsers (small and large) to enter the market, i have never experienced such keystroke behavior. i would further comment that if something about a new development (such as the camino app) appears to be affecting a program that i have used extensively for so long in so many environments, that this behavior at least warrants some testing and examination.perhaps some other users will post some comments. i certainly don't write apps myself and would never assume that i understand how such a bug would manifest itself!
i don't see how camino could impact the keyhandling of another app. reopen if anyone has any better ideas. eg, does this happen with any other apps?
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.