Bug #11654
Fix key press handling in Content Dialog
Status: | Rejected | Start date: | 2010-12-22 | |
---|---|---|---|---|
Priority: | -- undefined -- | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - |
Description
Currently the ContentDialog uses a Ext.keyMap on document to work with key events. That should be refactored.
Related issues
History
#1 Updated by Robert Lemke about 4 years ago
- Project changed from Core Team to Base Distribution
#2 Updated by Sebastian Kurfuerst about 4 years ago
- Project changed from Base Distribution to TYPO3.Neos
#3 Updated by Sebastian Kurfuerst about 4 years ago
- Tracker changed from Task to Bug
- Status changed from New to Needs Feedback
- Priority changed from Should have to Could have
Could you check if this is still relevant? I remember a changeset recently which has changed some behavior there...
#4 Updated by Christian Müller about 4 years ago
- Status changed from Needs Feedback to Rejected
- Priority changed from Could have to -- undefined --