opened
Yakow13
username_0
When using padding for FAB component, to trim its position in layout, after expanding the content cover, it's not filling the whole area.  I'm not sure if this is bug, or expected behavior.

For more info, check the screenshot. The area on left is covered, the area on right is not. FAB is in the layout which is covering whole screen

![screenshot_20180821-110102 1](https://user-images.githubusercontent.com/10089252/44392125-c280c680-a531-11e8-82e8-b91b7c488764.png)
Content cover and padding/margin
issue
created
Yakow13
username_0
I'm working with newest version, v2.3.1. 

Here is screenshot how does it looks like with following parameters:
android:layout_width="match_parent"
android:layout_height="match_parent"
android:paddingEnd="630dp"

Am I doing something wrong, or content cover is not designed to work with padding?

![screenshot_20180823-102547](https://user-images.githubusercontent.com/10089252/44513938-0b19ba80-a6bf-11e8-9e8f-549af10c7964.png)
comment
created
Yakow13
username_0
Unfortunately, usage of margin instead of padding, doesn't make any different. 

Thanks for your time :)
comment
created
markormesher
username_1
What we need here is to have the FAB container still take up the full width/height of the layout (to allow the content cover to use the whole screen) and specify an internal offset to push the FAB, speed-dial and content-cover around _within_ the bounds of the container.

If it's urgent you could do this yourself by accessing the individual views (https://github.com/username_1/android-fab#access-to-underlying-views) and programatically moving them, but the better option is to actually implement that internal offset in the library itself. I'll take a stab at that this weekend!
comment
closed
markormesher
username_1
issue
created
markormesher
username_1
Hey @username_0. This should be possible now in v2.4.1 - you can set an internal offset from any of the four edges, so in your case you'd set `internalOffsetEnd` to be the width of the area that isn't getting covered in the screen shots above (you can do this from code or XML). The internal offset is _added_ to the default offset, so it will appear slightly inset into the left-side area (as it does right now), rather than being right on the line between them. It's implemented this way for exactly this use case, because I think that'll be the most common usage of the feature. LMK how you get on with the update version; I'll close this for now but feel free to re-open if necessary.
comment