Right, this is a regression in rc-proposed (most likely introduced with
multiple window support), now being tracked by bug #1659884. thanks
Adnane!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am on OTA-14 and this is what i am seeing
** Attachment added: "20170116_200106.mp4"
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1655402/+attachment/4805140/+files/20170116_200106.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I’m not seeing that, at least not on rc-proposed: if I browse to
http://blogs.sitepointstatic.com/examples/tech/full-screen/index2.html
and tap on the squirrel to make it go fullscreen, then pulling down the
indicators bar (partially or completely) doesn't exit fullscreen.
--
You received this
Yeah i mean even right now if you pull down it makes the browser exist
the fullscreen mode only compared to the pull up gesture.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655402
Title:
Exit
The current behaviour was implemented according to design. I can see how the
fact that exiting fullscreen also brings up the tabs view may be confusing to
the user.
However only the bottom edge can be used by apps. The browser wouldn’t have a
way of knowing that the top edge has been pulled
** Description changed:
Actually to exit the fullscreen mode you need to pull up, but this
gesture also brings the tabs listing view, so i think the right gesture
- is pull down which make the browser-app exists fullscreen mode and the
+ is pull down which make the browser-app exist
