X
Tap here to go to the mobile version of the site.

Support Forum

switch to previous view in way

Posted

upgraded to firefox 19 on android and I came a cross an issue, the button to go into multitask mode (makes the app take up half the screen) is in the bottom riht corner, it blocks part of everypage and it covers the keyboard, my question is, can I remove ormove this button to the address bar area, say beside the me u button.

would make more sense in that position!

upgraded to firefox 19 on android and I came a cross an issue, the button to go into multitask mode (makes the app take up half the screen) is in the bottom riht corner, it blocks part of everypage and it covers the keyboard, my question is, can I remove ormove this button to the address bar area, say beside the me u button. would make more sense in that position!

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Android; Tablet; rv:19.0) Gecko/19.0 Firefox/19.0

More Information

Andrew
  • Moderator
281 solutions 3601 answers

Could you provide a screenshot if possible and possibly point out where what the issue is as this would help us out in an easier way.

Could you provide a screenshot if possible and possibly point out where what the issue is as this would help us out in an easier way.

Question owner

bottom right corner, , second image shows it imposed over the keyboard

bottom right corner, , second image shows it imposed over the keyboard
Andrew
  • Moderator
281 solutions 3601 answers

Firefox does not provide keyboards. Please find out what keyboard program you are using as well as if required download another type of keyboard because as far as I can see, this issue is not a Firefox issue but a keyboard issue.

Firefox does not provide keyboards. Please find out what keyboard program you are using as well as if required download another type of keyboard because as far as I can see, this issue is not a Firefox issue but a keyboard issue.

Helpful Reply

it's not they keyboard, its their before keyboard is opened, the button showed up as soo. as I updated fieefox to 19.

its on all pages including home, I have included a picture of what does when pushed, as you can see when pushed button moves to top of the app screen to maximize it again.


for reference I am using the keyboard built into the tablet, which is a samsung galaxy note 10.1

it's not they keyboard, its their before keyboard is opened, the button showed up as soo. as I updated fieefox to 19. its on all pages including home, I have included a picture of what does when pushed, as you can see when pushed button moves to top of the app screen to maximize it again. for reference I am using the keyboard built into the tablet, which is a samsung galaxy note 10.1
Andrew
  • Moderator
281 solutions 3601 answers

In this case it is a new feature and I unfortunately am not aware of it. I will have to check this out and get back to you.

In this case it is a new feature and I unfortunately am not aware of it. I will have to check this out and get back to you.

Question owner

alright, it's in a horrible location as you can see, prefer to turn it off or have ut moved.

thank you for the help, in case it helps my tablet is using Android os jellybean.

alright, it's in a horrible location as you can see, prefer to turn it off or have ut moved. thank you for the help, in case it helps my tablet is using Android os jellybean.
kbrosnan
  • Top 25 Contributor
  • Moderator
407 solutions 2827 answers

I assume this is some sort of Samsung tablet. Which model? Filed the following bug https://bugzilla.mozilla.org/show_bug.cgi?id=842911

I assume this is some sort of Samsung tablet. Which model? Filed the following bug https://bugzilla.mozilla.org/show_bug.cgi?id=842911

Question owner

its a galaxy note 10.1 tablet.


so does that mean its a tablet issue and not a firefox issue?

its a galaxy note 10.1 tablet. so does that mean its a tablet issue and not a firefox issue?

Modified by ankanamoon

Andrew
  • Moderator
281 solutions 3601 answers

I can confirm that this issue has been resolved but once again reported to be added back from another thread (https://support.mozilla.org/en-US/questions/954217)

I can confirm that this issue has been resolved but once again reported to be added back from another thread (https://support.mozilla.org/en-US/questions/954217)