Bug 9407 – Browser: Do not show fullscreen button when scrolling with the keyboard

Bug 9407 - (int-159631) Browser: Do not show fullscreen button when scrolling with the keyboard

(int-159631)
Summary:	Browser: Do not show fullscreen button when scrolling with the keyboard

Status:	REOPENED

Product:	UI Specification
Component:	General
Version:	5.0/(3.2010.02-8)
Platform:	All Maemo

Importance:	Unspecified minor with 3 votes (vote)
Target Milestone:	---
Assigned To:	Urho Konttori
QA Contact:	ui-specification-bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2010-03-05 04:38 UTC by Ryan Abel
Modified:	2010-06-16 18:37 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Ryan Abel (reporter) maemo.org

2010-03-05 04:38:20 UTC

SOFTWARE VERSION:
3.2010.02-8

EXACT STEPS LEADING TO PROBLEM: 

 1. Open a browser window
 2. Tap the fullscreen button in the toolbar to enter fullscreen mode.
 3. Open the keyboard.
 4. Press an arrow key or the spacebar.

EXPECTED OUTCOME:
Scrolling with the keyboard does not show the fullscreen button.

ACTUAL OUTCOME:
Scrolling with the keyboard shows the fullscreen button.

REPRODUCIBILITY:
Always

OTHER COMMENTS:
There seems to be little point in having the fullscreen button appear when
scrolling using keyboard, and it's quite distracting to having it flashing in
and out in the bottom corner while reading. Of course it needs to appear if a
user is touching the touchscreen (since, presumably, they may want to toggle
fullscreen mode then), but it seems like it'd be a safe assumption that users
scrolling with the keyboard are not interested in having the fullscreen button
appearing and disappearing constantly.


User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-US)
AppleWebKit/531.9+(KHTML, like Gecko, Safari/528.16) OmniWeb/v622.10.0

Comment 1 Andre Klapper maemo.org

2010-03-05 16:21:40 UTC

Spec says that "In full screen mode the button will fade away when the user
hasn’t interacted with the screen within 5 sec. Button will reappear the moment
the user interacts with the content."

Comment 2 timeless 2010-03-05 17:06:50 UTC

roughly this bug got killed because the ui designer is a ghost. i personally
agree with the bug but we need to appeal to someone else if we want it fixed.

Comment 3 Bartosz Taudul 2010-03-11 01:29:19 UTC

(In reply to comment #1)
> Spec says that "In full screen mode the button will fade away when the user
> hasn’t interacted with the screen within 5 sec.
I think this clearly says that only touchscreen interaction should delay the
fade away.

> Button will reappear the moment the user interacts with the content."
This can be interpreted in two ways.
1. "The content" is used to avoid repetition of "the screen". In this case fix
is not against the spec.
2. "The content" means everything, so even scrolling the page using keyboard
fits. This interpretation would however mean that either keyboard or
touchscreen actions cause the button to appear, but only touchscreen
interaction delays its disappearance (this is not how the browser behaves).

Comment 4 timeless 2010-03-11 08:36:35 UTC

you're welcome to think whatever you like, you're even welcome to get all the
devs to agree with you. however.

according to the author of the specification:
> any interaction will show the full screen button. this way we make sure the
> user will not get lost in full screen mode.

the spec author then tried to say:
> the actual outcome matches the expected outcome

as such, it's very clear that if we want to change this behavior, we'd have to
get the spec changed. this bug is assigned to the only person who could do
that.

please don't add too many comments complaining or expressing your opinion, the
summary of the bug is clear enough for the assignee to consider dealing with
it. the assignee, sadly, is quite busy worrying about your next upgrade.

Comment 5 Urho Konttori 2010-04-04 21:42:08 UTC

Discuss with simone, change the behavior and forget about the spec. (my 2
cents)

Comment 6 Andre Klapper maemo.org

2010-04-23 21:15:33 UTC

Internal comment:
"any interaction will show the full screen button. this way we make sure the
user will not get lost in full screen mode.
Actual out come is the valid one and Spec will not be changed."

Comment 7 Ryan Abel (reporter) maemo.org

2010-04-23 21:42:29 UTC

(In reply to comment #6)
> Internal comment:
> "any interaction will show the full screen button. this way we make sure the
> user will not get lost in full screen mode.
> Actual out come is the valid one and Spec will not be changed."
> 

Going back to Comment #5. Has this discussion taken place?

The spec is clearly not sane. This is the sort of behavior that irritates users
and makes people dislike your product. It needs to be changed.

Comment 8 Andre Klapper maemo.org

2010-06-16 18:37:39 UTC

Reopening.