Closed
Bug 577059
Opened 14 years ago
Closed 14 years ago
[Camino 2.1a1pre] Delete/backspace does not work at: http://code.google.com/p/adblockforchrome/issues/list
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 576821
People
(Reporter: mehmet.sahin, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.8pre) Gecko/20100705 Camino/2.1a1pre (like Firefox/3.6.8pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en; rv:1.9.2.8pre) Gecko/20100705 Camino/2.1a1pre (like Firefox/3.6.8pre) Hello. Delete/backspace works fine again now (thanks!). But it doesn't work at the above mentioned page with a german keyboard. Note: With Firefox 3.6.6 (and Safari 5) it works fine there! Keyboard: German OS: 10.6.4 Camino Version 2.1a1pre (1.9.2.8pre 20100705001228) Thanks and regards Mehmet Reproducible: Always Steps to Reproduce: 1.) go to http://code.google.com/p/adblockforchrome/issues/list 2.) click on a bug from the list 3.) Press delete/backspace to go back to the list Actual Results: delete/backspace does not work Expected Results: delete/backspace should work
Comment 1•14 years ago
|
||
I can actually reproduce this :-(. And it is not limited to that particular project on googlecode. This one shows the same issue: http://code.google.com/p/textpattern/issues/list. It seems more of a focus issue somewhere as I can't page up/down a page either. If I switch between two open tabs from the keyboard, then the focus is restored, backspace works, paging & tabbing works, etc.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•14 years ago
|
Version: unspecified → 1.9.2 Branch
Comment 2•14 years ago
|
||
This is actually pretty much the same issue as bug 576821. On those bug pages as well, backspace doesn't work in the case of lost focus.
I can't reproduce this, either :( That said, it's ultimately a focus issue, so bug 576821.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•