maemo.org Bugzilla – Full Text Bug Listing
|Summary:||Hardware keys do not change volume when status menu in foreground & browser in background|
|Product:||[Maemo Official Platform] Multimedia||Reporter:||Jan Knutar <jknutar>|
|Component:||Multimedia framework||Assignee:||unassigned <nobody>|
|Status:||RESOLVED FIXED||QA Contact:||multimedia-framework-bugs|
|Priority:||Low||CC:||andrea, andre_klapper, bugzilla770, harish.k, jknutar, maemo, quim.gil, tri|
|Bug Depends on:|
SOFTWARE VERSION: 1.2009.42-11 EXACT STEPS LEADING TO PROBLEM: 1. Open browser 2. Tap lower right to bring browser out of fullscreen 3. Tap status area to get the status menu 4. press volume keys to adjust volume 5. tap outside status menu to return to browser EXPECTED OUTCOME: - Browser is opened. - Browser switches out of fullscreen. - Status menu appears. Browser is blurred out. - Volume is adjusted. - Status menu goes away. Browser is unblurred. ACTUAL OUTCOME: Browser is opened. Browser switches out of fullscreen. Status menu appears. Browser is blurred out. * Nothing happens when pressing volume keys. Status menu goes away. Browser is unblurred. * Zoom has been changed in browser. REPRODUCIBILITY: Always OTHER COMMENTS: The browser grabs the volume keys for zooming normally, but when the user taps the status area and the status menu is visible, the browser isn't really the main focus of the user, one of the most prominent UI elements visible (not counting blurred browser) is the volume slider, it would make sense that the volume keys would now be directed to the status menu and the volume slider in the status menu, instead of going to the browser that is blurred out and sitting in the background.
> EXACT STEPS LEADING TO PROBLEM: > > 1. Open browser > 2. Tap lower right to bring browser out of fullscreen > 3. Tap status area to get the status menu What do you mean by 'status area' ? I can't reproduce it as I don't quite understand the exact steps.
Status area, in upper left corner of the screen, to the right of the icon consisting of two (or more) rectangles for swapping applications. The status area has the clock, signal strength meter, and battery meter, and other small things depending on device state. If an application has focus, then to the right of the status area we have the window titlebar, from where you can activate a program's own menu. Further to the right of this, in the right upper corner, is the close "X" button. When I tap the status area, I get a menu that covers a little less than the top half of the screen. It has the battery icon "Battery", a speaker icon with a volume slider, "Clock & Alarms" button, "Profile" button, "Internet connection" button, "Bluetooth" button, and sometimes more buttons. Whatever application was open before is blurred out when activating this menu. When you start the browser, you initially see the bookmarks. The status area is still visible at this point, and adjusting volume works. Tap a bookmark to launch the real browser. The browser is fullscreen, and the status area is no longer visible. Tap lower right to bring browser out of fullscreen, the status area is now visible again. Tap the status area to bring out the status menu, press one of the volume/zoom hardware keys on top of the device. Press the rightmost one, for example, 10 times. Tap outside the status menu, to go back to browser. Zoom has been changed in browser. Volume has not been changed. Another related thing: If I tap the window titlebar (right of the status area), and bring out the browser's menu (New Window, reload, paste, find on page, save page as, downloads, details, options), then the hardware keys control volume.
If you think the current behaviour is not consistent then this must be addressed as a back. Note that I'm just triaging enhancement requests and I haven't attempted to reproduce this case.
Thanks for reporting this. I can reproduce this in internal version 49-3. For future reference please only list the expected and actual outcome *AFTER* performing ALL steps listed above. Thanks! OTHER COMMENTS: Works e.g. in Conversations view.
The status menu seems to inherit the foreground app's handling of the hardware keys (in general it works if the foreground app is one that doesn't override the zoom/volume keys and vice versa).
Volume level doesn't change at all now (or browser zoom) in 2.2009.51-1 so the change hasn't implemented expected bahviour only introduced new and seemingly wrong behaviour. I suggest reopening this bug or open a new for the new unwanted behaviour.
Reopening as this bug is not fixed as per "expected outcome": 1. Browser is opened. 2. Browser switches out of fullscreen. 3. Status menu appears. Browser is blurred out. 4. Volume is adjusted. 5. Status menu goes away. Browser is unblurred. Now instead of the volume adjusting as it should in step 4, the volume keys do nothing at all when the status menu is visible on top of the browser. In fact this behaviour can be repeated in x-term, however several other apps (eg. photo viewer, email) still incorrectly intercept the status menu volume key event and treat it as a zoom event. Oddly, the Bookmarks application works as expected (ie. status menu volume key event changes the volume level). So we still have 3 different responses to the status menu volume key event depending on the currently focused application. This needs to be fixed across the board, irrespective of application: When the status menu is visible, the volume keys should change the volume level regardless of the currently focused application.
This has been fixed in package maemo-statusmenu-volume 0.51+0m5 which is part of the internal build version 2009.52-5 (Note: 2009 is the year, and the number after is the week.) A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.) Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time. To answer popular followup questions: * Nokia does not announce release dates of public updates in advance. * There is currently no access to these internal, non-public build versions. A Brainstorm proposal to change this exists at http://maemo.org/community/brainstorm/view/undelayed_bugfix_releases_for_nokia_open_source_packages-002/
*** Bug 7634 has been marked as a duplicate of this bug. ***
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).