FAB potential bug?

Describe your issue & Steps to reproduce & Actual Behaviour

I have just created a simple app with no blocks in it to test the components of the platform.
Added only a textbox and a FAB. When clicking on the textbox and keyboard pops up FAB stays hidden behind the keyboard!!
(edit 1: I have tested this only in companion not in production)

Expected Behaviour

FAB should float upwards above the keyboard

Show your Blocks

none everything was done on the designer

Android version

8.0.0 on Samsung Galaxy Edge 7

(edit 2)
The same is happening with other FABs provided in extensions like @Andres_Cotes paid FAB…

Since I thought it was related to the specific extension I had created the simple project that I mentioned above to see if this behaviour was repeated in the built in component…

Sadly it was, that is why I created this topic …

1 Like

When the keyboard opens the FAB disappears so as not to disturb the typing, when the keyboard is closed, the FAB appears again, it is not a bug, it is a behavior to avoid problems with typing.

But I understand what you mean, you expected different behavior right? that the FAB would take off to the top of the keyboard, so it would not have to disappear, I also think it would be better.

1 Like

You guys can move the FAB to any position to any time you want.
Just change the margin option.

1 Like

@Soft_Darsh yes exactly I expected a different behaviour instead of disappearing…

@Mika I was ready to ask how but you edited your reply…

However how can we know the proper margin to show FAB above the keyboard?
There are devices that have adjustable keyboard height (though keyboard settings) and differences might exist when building apps that play both in phones and tablets…

1 Like

And here you have now the answer why I did not have added this to our component.
Because we can never know the size of the keyboard as you wrote.

OK I understand …
I have been using other distributors that have this behaviour that I expected and I thought that it would not be that hard to implement it to this platform as well.

However there are different POVs to each distributor and that is entirely respected…

Might be helpful


This is an interesting approach to get the margin… :+1:
The fact that there is also a block available to check if keyboard is visible is also helping the process…

However in case there are several textboxes an extensive use of when Textbox got/lost focus blocks would be necessary to complete the task.

Also in case someone is using multiple arrangements instead of different screens and several FABs then things might get a little bit complicated… however it is still possible to fix the “issue”…

Anyway, thanks for the suggestion, I will keep in mind in case I opt to move the FAB around instead of using the currently implemented functionality…

1 Like

We have this on screen 1 properties

1 Like

Yes I know, that is what I am saying that having this block will certainly help :wink:

1 Like