Community
Participate
Working Groups
Created attachment 219896 [details] Details of Juno installation and screenshot Hello, i was asked to report an issue here when i posted to the forum: http://www.eclipse.org/forums/index.php/mv/msg/369485/901847/#msg_901847 After upgrade to Juno i have serious problems with the key bindings when i edit JSF / xhtml files. As u can see on the sceenshot the bindings Ctrl-C, Ctrl-V, Ctrl-X very often are disabled and i can only enable them again when i switch between "Design" and "Preview". But soon after the bindings vanish again and the only way to e.g. remove content is via the Backspace key. Copy&Paste is not possible then.
Created attachment 219897 [details] .log with some msgs regarding keybindings
Info: issue appears to only be present when using the Web Page Editor under the 4.x platform (can't seem to reproduce under platform 3.8).
And what does this mean? Can i solve the issue somehow? As this behavior is really annoying...
(In reply to comment #3) > And what does this mean? Can i solve the issue somehow? As this behavior is > really annoying... This means simply what it says; I wanted to capture and relay relevant information discovered during investigation of the issue.
3.4.1 is in a shutdown mode. We will continue to investigate and provide a fix as early as possible. Targeting to Kepler.
Juno SR1 builds are now producing related errors (for cut/copy/paste/delete actions): !ENTRY org.eclipse.ui 4 4 2012-10-03 16:06:34.104 !MESSAGE Conflicting handlers for org.eclipse.ui.edit.cut: {ActionHandler(org.eclipse.ui.texteditor.TextOperationAction@3dd2ac21)} vs {ActionHandler(org.eclipse.jst.pagedesigner.commands.CutAction@1b322cc8)}
Created attachment 222140 [details] Retargets global actions for Web Page Editor instead of registering conflicting actions.
Committed to master. http://git.eclipse.org/c/jsf/webtools.jsf.git/commit/?id=e172355cd7f3acc5f0afdb6429e9b288a839d243
Released to R3_4_maintenance and master.
*** Bug 389218 has been marked as a duplicate of this bug. ***
*** Bug 395924 has been marked as a duplicate of this bug. ***