diff options
| author | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2018-02-19 23:47:19 +0100 |
|---|---|---|
| committer | Daniel Calviño Sánchez <danxuliu@gmail.com> | 2018-02-28 15:03:26 +0100 |
| commit | e37c4fd7f308be6f4dbece2c6cd2e8ff2d211c09 (patch) | |
| tree | af54ed3cf4f82f1e6ef95ed5ad0578f2c3ffbe64 /apps/files/js/breadcrumb.js | |
| parent | 3850221ae118f05df4fff9016606ad2572c0057f (diff) | |
| download | nextcloud-server-e37c4fd7f308be6f4dbece2c6cd2e8ff2d211c09.tar.gz nextcloud-server-e37c4fd7f308be6f4dbece2c6cd2e8ff2d211c09.zip | |
Take padding and margin of the creatable actions div into account
There are some differences in width handling between the browsers used
to run the tests, most likely due to their support (or lack of) of
certain CSS features: PhantomJS requires "width" to be set (probably
because it does not handle flex displays and treats it like a block, so
"min-width" does not matter in this case), while Firefox requires
"min-width" to be set (otherwise the children of "#controls" could be
compressed due to its use of flex display and the elements would end
with a different width than the one needed for the tests). Due to all
that the width of the breadcrumb siblings must be specified in the tests
using both "width" and "min-width".
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Diffstat (limited to 'apps/files/js/breadcrumb.js')
| -rw-r--r-- | apps/files/js/breadcrumb.js | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/apps/files/js/breadcrumb.js b/apps/files/js/breadcrumb.js index c02ed488da0..16762f386be 100644 --- a/apps/files/js/breadcrumb.js +++ b/apps/files/js/breadcrumb.js @@ -316,7 +316,7 @@ return; } - var availableWidth = this.$el.parent().width() - this.$el.parent().find('.actions.creatable').width(); + var availableWidth = this.$el.parent().width() - this.$el.parent().find('.actions.creatable').outerWidth(true); // If container is smaller than content // AND if there are crumbs left to hide |