[hafqa] [hafqa] [Bug 2787] Screen lock not entirely locked, allows some input
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Mon Nov 3 17:41:09 EET 2008
- Previous message: [hafqa] [Bug 2787] Screen lock not entirely locked, allows some input
- Next message: [hafqa] [Bug 1943] No easy way to add dsp tasks to the dsp_dld config file
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://bugs.maemo.org/show_bug.cgi?id=2787 ------- Comment #10 from eero.tamminen at nokia.com 2008-11-03 17:41 GMT+3 ------- (In reply to comment #9) > (In reply to comment #8) > > So, a different bug? Or if you're using 4.1 instead of 4.0, the bug (menu > > being accessible when screen is "locked") is fixed? > > One can see it either as a different bug or as the same bug partially fixed. Input passing through system modal dialog and changing banner position (code bugs) are completely different issues from "All button and touchscreen presses ignored until screen lock pattern is repeated" enhancement request (UI spec issue and IMHO also very annoying). > > Btw. If you set the dim & blank period to the same value, > > But this would change the behavior when locking isn't used. Timeouts, not behavior. (personally I think dimming is just annoying, you then need to tap to the screen to see what's on it which results often in tapping accidentally some link in browser. Then you need to stop the page load, tap back and wait until the page you were reading reloads...) -- Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email Replies to this email are NOT read, instead please add comments at https://bugs.maemo.org/show_bug.cgi?id=2787 ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
- Previous message: [hafqa] [Bug 2787] Screen lock not entirely locked, allows some input
- Next message: [hafqa] [Bug 1943] No easy way to add dsp tasks to the dsp_dld config file
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]