Some fields are created in the onMeasure method such as mReorderedIndices. It will be more efficient to avoid object creations as much as possible.
Create those objects when needed instead (e.g. It will be enough to recreate the mReorderedIndices when the children views are updated in the FlexboxLayout)

I added compile 'com.google.android:flexbox:0.2.1' to my build.gradle (app) file and I got the above error. The automatic install takes a while, so how can I manually download and install the dependencies on OsX

Hi, i'm receiving this crash when i add a flexbox to my layout without any children, i'm using version 0.2.0. Temporary fixed it by adding a 0dp size Space children.

 java.lang.NullPointerException: Attempt to invoke virtual method 'int android.util.SparseIntArray.size()' on a null object reference
                                                                                       at com.google.android.flexbox.FlexboxLayout.isOrderChangedFromLastMeasurement(FlexboxLayout.java:403)
                                                                                       at com.google.android.flexbox.FlexboxLayout.onMeasure(FlexboxLayout.java:259)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1465)
                                                                                       at android.widget.LinearLayout.measureVertical(LinearLayout.java:748)
                                                                                       at android.widget.LinearLayout.onMeasure(LinearLayout.java:630)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.widget.RelativeLayout.measureChildHorizontal(RelativeLayout.java:715)
                                                                                       at android.widget.RelativeLayout.onMeasure(RelativeLayout.java:461)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                                       at android.support.v7.widget.ContentFrameLayout.onMeasure(ContentFrameLayout.java:135)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1465)
                                                                                       at android.widget.LinearLayout.measureVertical(LinearLayout.java:748)
                                                                                       at android.widget.LinearLayout.onMeasure(LinearLayout.java:630)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1465)
                                                                                       at android.widget.LinearLayout.measureVertical(LinearLayout.java:748)
                                                                                       at android.widget.LinearLayout.onMeasure(LinearLayout.java:630)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5951)
                                                                                       at android.widget.FrameLayout.onMeasure(FrameLayout.java:194)
                                                                                       at com.android.internal.policy.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2643)
                                                                                       at android.view.View.measure(View.java:18794)
                                                                                       at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:2100)
                                                                                       at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1216)
                                                                                       at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1452)
                                                                                       at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1107)
                                                                                       at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6013)
                                                                                       at android.view.Choreographer$CallbackRecord.run(Choreographer.java:858)
                                                                                       at android.view.Choreographer.doCallbacks(Choreographer.java:670)
                                                                                       at android.view.Choreographer.doFrame(Choreographer.java:606)
                                                                                       at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
                                                                                       at android.os.Handler.handleCallback(Handler.java:739)
                                                                                       at android.os.Handler.dispatchMessage(Handler.java:95)
                                                                                       at android.os.Looper.loop(Looper.java:148)
                                                                                       at android.app.ActivityThread.main(ActivityThread.java:5417)
                                                                                       at java.lang.reflect.Method.invoke(Native Method)
                                                                                       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
                                                                                       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

Hi, seems there is no need to measure GONE child in stretchViews().

In the onMeasure method, child.measure may be called more than once (e.g. Called first in the first loop to determine the number of flex lines, then called later to be expanded/shrank based on flexGrow/flexShrink attributes also maybe called to be stretched based on alignItems/alignSelf attributes).

This may cause performance issue especially the child is a nested ViewGroup.
It will be efficient to defer the child.measure as much as possible to reduce the number of measurements of the same child.

i use this view. i want to get the count of line in this view. How can i do?
in this picture, it has 2 line of textview. how can i get the number 2?

For now, there is no way to add foreground on Flexbox-layout

Such as use cases where FlexboxLayout is more beneficial than other existing layouts.

Version 0.2.4 introduced a layout bug, I believe it was this commit.

A FlexboxLayout with height="wrap_content" is supposed to set its height to fit all contained elements. This does not work correctly when elements have a margin. The container height only matches the height of the element itself, without the margin, but then the element gets shrunk so that it fits into the container with the margin. This results in a part of the element being cut off by the margin, like in the following example:

The above label has a marginBottom of 6dp and it's cut off at the bottom by 6dp. The glitch goes away if we remove the margin (which it not desirable), or if we revert to 0.2.3.

Layout code for the above example (simplified):

    <com.google.android.flexbox.FlexboxLayout
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        app:flexWrap="wrap"
        app:justifyContent="flex_end">

        <TextView
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:layout_marginBottom="6dp"
            android:layout_gravity="top"
            android:layout_weight="1"
            app:layout_flexBasisPercent="50%"
            app:layout_flexGrow="1"
            app:layout_flexShrink="0"/>

Flexed items that are shrunk to fit 50% of the parent are leaving a considerable vertical gap equivalent to the size of the items before shrinking.

The flexbox layout attributes:

android:layout_width="match_parent" android:layout_height="match_parent" app:flexWrap="wrap_reverse" app:alignItems="stretch" app:alignContent="flex_start" app:flexDirection="row" android:id="@+id/flexbox"

The imageviews attribute:

lp.flexBasisPercent = 0.49f;

Reproduced result:

I've populated my flexbox beyond the screen size... how do i scroll it ?

I find,onResume() method perform addView(),but does not show， replaces by LinearLayout,it is normal.And sometimes,in onCreate() method,it also does not show.I want to see if you have any such situation.

I put a FlexboxLayout with layout_height set to wrap_content (and a bottom margin) in a RelativeLayout with a fixed height. When I filled the FlexboxLayout with items and called getMeasuredHeight() later it returned the same value as getHeight(), despite there being items that were past the end of its container (I should mention that the FlexboxLayout was set to invisible before the layout passes, in case that matters). It is my understanding that getMeasuredHeight() should return the height that the View would be if it weren't constrained by a container, so this result seems like a bug.

Is it possible to support absolute position for flexbox-layout?

I'm using FlexboxLayout 0.2.0, but I think that text is still not wrapping correctly.

<com.google.android.flexbox.FlexboxLayout
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:padding="16dp"
    app:flexWrap="wrap">

    <TextView
        android:id="@+id/text1"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:textSize="16sp"
        android:text="AAAAAAB"/>

    <TextView
        android:id="@+id/text2"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:textSize="16sp"
        android:text="CCCCCCCCCCCCCCCCCCCCCCCC"/>

</com.google.android.flexbox.FlexboxLayout>

This layout is rendered as top image, then I added 'D' (middle image), then another 'D' (bottom image). In top and bottom render FlexboxLayout wrapped text correctly, but in middle render there are missing 'B' from text1 and 'D' from text2.

When changed attribute layout_width to wrap_content, behavior is different, but still incorrect.

In first image is the same text as above, then added 'E', another 'E' and once again 'E'. In first and last is text rendered correctly. In second image there is missing half size of char 'E', in third image are missing half size of first char 'E' and completely missing second char 'E'.

After I've changed android:padding to android:layout_margin, text is rendering correctly in all of the above cases.

Is it possible to have a separator line in multi-line flexbox after every line to increase human readability?

LICENSE, line 190:

Copyright [yyyy] [name of copyright owner]

We're on 0.2.2. We had wanted a slight margin (4dp) in between items in the flexbox, as well as between the lines when the flexbox wrapped the items. However, after trying multiple variations of applying margin to the items in the flexbox it did not seem to comply. Is this possible? We resorted to using another FrameLayout around the LinearLayout for padding, but what wondering if this is a bug or just not supported functionality within flexbox?

For example here is the item we were using in the flexbox. It was not respecting the layout_marginBottom or layout_marginRight on the LinearLayout:

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
       xmlns:tools="http://schemas.android.com/tools"
       xmlns:app="http://schemas.android.com/apk/res-auto"
       android:cropToPadding="false"
       android:clipToPadding="false"
       android:clipChildren="false"
       android:layout_height="32dp"
       android:layout_width="wrap_content"
       android:layout_marginBottom="10dp"
       android:layout_marginRight="10dp">

    <ImageView
        android:id="@+id/icon"
        android:layout_width="14dp"
        android:layout_height="14dp"
        android:layout_gravity="center_vertical"
        app:srcCompat="@drawable/ic_tag"
        android:tint="@color/bluey_grey"/>

    <TextView
        android:id="@+id/text"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_gravity="center_vertical"
        android:ellipsize="end"
        android:maxLines="1"
        android:paddingEnd="8dp"
        android:paddingLeft="8dp"
        android:paddingRight="8dp"
        android:paddingStart="8dp"
        android:textColor="@color/bluey_grey"
        android:textSize="14sp"
        tools:text="Conversations"/>

    <ImageView
        android:id="@+id/delete_icon"
        android:layout_width="10dp"
        android:layout_height="match_parent"
        android:layout_gravity="center_vertical"
        app:srcCompat="@drawable/ic_delete"/>

</LinearLayout>

As per question on Stackoverflow Flexbox shrinks the content. Expected outcome was that, lets say, if just three categories only could be fitted in first, then, next items should appear in next line.

Any help would be appreciated. Thank you.

hi guys,
how does flexbox layout fit with constraintlayout ? we are looking to build interfaces inspired by the flexbox way of working.

we are unsure of how both these libraries fit with each other. Both are "google recommended". Constraintlayout is even part of "best practices" - https://developer.android.com/training/constraint-layout/index.html

what is even more puzzling is that flexbox-layout does not build on top of constraintlayout. if there was some info on how an end-user should think about using both of these.... that would be awesome.

Is Google planning to include this in the Android Support Library or SDK?

Bottom of the content is truncated unexpectedly when the parent FlexboxLayout has a padding and
alignItems is set to flex_end or (alignContent is set to flex_end and flexLines >= 2)

We upgrade our android-support-library to 24.0 recently,but flexbox used 23.0,so compile failed,is there any solution?

Description

On the sample application, I changed Flex Grow for the last item from 0.0 to 1.0. I expected it made the item expand to the end of the line. However, the width of the item didn't change and when I opened the dialog again, Flex Grow was 0.0.

Environment

• Mac OS X 10.11.5
• Android Emulator, Nexus One, API 17
• Android Studio 2.2 Beta 3

Steps

1. Open the sample app
2. Click the item 3
3. Change the value of Flex Grow from 0.0 to 1.0
4. Click OK on the dialog

Result

Nothing happens

Expected Result

The item 3 expands to the end of the line

Remarks

I found the below code and it seems the code failed to parse a text containing dots . as an integer, such as 1.0. In fact, when I input 1 instead of 1.0 at step 3, the result was as expected.

https://github.com/google/flexbox-layout/blob/master/app/src/main/java/com/google/android/apps/flexbox/FlexItemEditFragment.java#L376

I am wondering you might have to update your FlexEditTextWatcher so that it can accept a flow value as an input when the ID of the TextInputLayout is input_layout_flex_grow or input_layout_flex_shrink. I'm creating a small patch to fix it to clarify the point and will let you know when it's ready.

Thank you.

While it would certainly diverge from the CSS flexbox model upon which this library is based, there are some inherent inefficiencies for Android because of differences in cost in nesting ViewGroups in Android compared to nesting <div> elements in HTML.

For tabular data, the following is simple and efficient in HTML:

<div class="grid">
  <div class="grid__row">
    <div class="grid__item">1</div>
    <div class="grid__item">2</div>
  </div>
  <div class="grid__row">
    <div class="grid__item">1</div>
    <div class="grid__item">2</div>
    <div class="grid__item">3</div>
  </div>
  <div class="grid__row">
    <div class="grid__item">1</div>
    <div class="grid__item">2</div>
    <div class="grid__item">3</div>
    <div class="grid__item">4</div>
  </div>
</div>

And CSS flexbox can easily be applied to this. However for Android This would need to be done with a parent ViewGroup representing grid, containing an number for child grid_row ViewGroups, each containing a collection of Views representing the individual the individual cells. Such a hierarchy is somewhat inefficient both in terms of layout inflation, and during measurement and layout.

A couple of simple additions to FlexboxLayout could make it easy to flatten such layouts by removing the individual rows - FlexboxLayout manages a collection of FlexLine objects which get calculated during measurement - and this is much more efficient that having child ViewGroups representing individual rows. If it were possible to have some optional attributes which could control when we should wrap to a new FlexLine then the usefulness of FlexboxLayout would increase dramatically, I think. Specifically we could have a flexLineItems integer which would cause a wrap whenever the current FlexLine contains the specified number of items. In addition a LayoutParams.wrapAfter boolean (default to false) could be used to force a wrap after the current child View.

As I said, I appreciate that this is a deviation from the CSS flexbox model, but feel that it could be a really useful addition on Android.

有人集成在 minsdk 10么？或者兼容包

Such as the #59 would be a nice example that demonstrates usefulness of the FlexboxLayout, otherwise it would be tricky if building it with existing layouts.

in layoutHorizontal/layoutVertical, when JustifyContent is space_between/space_around, the
float denominator = flexLine.getItemCount() !=1 ? flexLine.getItemCount() - 1 : 1f;

getItemCount() includes the GONE child, which will result in incorrect spaceBetweenItem. It seems we should filter the GONE child?

hi. your lib is awesome, so I want to use it in my app. the problem is I want to change direction of items be right to left. can u help me?

When requestLayout is called, all flex items measurements are executed regardless of the diff from the last measurement.

It will be more efficient to execute a measurement for only affected flex items from the last measurement.
(E.g. if a new flex item is appended to the end of the flex container, existing flex items (or at least flex lines that aren't relevant to the new flex item) don't have to be re-measured)

At this moment, each flex item can be shrank down to the size of 0 (invisible) if layout_flexShrink is set.
min-width, min-height equivalent attributes are useful to set a lower bound.

This demo app is so amazing!
But I thought the theme was not good when I open the dialog with KitKat device.

This is the screen I saw.

Sony Xperia Z1f Android 4.4.2

I guess it needs the theme of android.R.style.Theme_Holo_Light_Dialog on between Honeycomb and Kitkat.

I want to know how many hits I accumulated in a 7 day free trail app that has been lost?

Setting padding to FlexboxLayout's parent adds left padding to FlexboxLayout itself. Did I misunderstand how some parameters work or is it a bug?

<?xml version="1.0" encoding="utf-8"?>
<FrameLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:padding="20dp">

    <com.google.android.flexbox.FlexboxLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:alignContent="flex_start"
        app:alignItems="flex_start"
        app:flexDirection="row"
        app:flexWrap="wrap"
        app:justifyContent="flex_start">

        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:padding="30dp"
            android:text="TEXTEXT"/>
        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:padding="30dp"
            android:text="TEXTEXT"/>
        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:padding="30dp"
            android:text="TEXTEXT"/>
        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:padding="30dp"
            android:text="TEXTEXT"/>
        <TextView
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:padding="30dp"
            android:text="TEXTEXT"/>

    </com.google.android.flexbox.FlexboxLayout>

</FrameLayout>

It doesn't happen often, but if the first flex item's initial length is large enough to be judged a line wrapping is required, an empty flex line is added to the flex container, which leads to an unwanted space when align_items=stretch and align_content="stretch"

It would be nice if performance comparison with existing layouts (LinearLayout or GridLayout) is explained.

FlexboxLayout is intended to offer flexible layout functionalities rather than performance improvement, but in some situations (like building a grid like layout with dynamic number of children), FlexboxLayout should reduce the nested ViewGroups.
It's useful to explain performance comparison in such cases, if it turns out FlexboxLayout has disadvantages compared to existing layouts, it will be also beneficial for recogniznig the room for optimization for FlexboxLayout.

hope to be added in order to limit the maxLines

I wrote some wiki pages in my repo in an effort to make the documentation more clear:

https://github.com/lii2/flexbox-wiki

*Added an installation page and attributes page
*Updated the sidebar to match
*Added a table of attributes so people could scan through the attributes easily

A question: Am I installing the flexbox layout correct? It seems to be running correctly on my smartphone, but the Android Studio XML design tab is running into rendering problems:

Exception raised during rendering: android.graphics.drawable.VectorDrawable_Delegate.nDraw(JJJLandroid/graphics/Rect;ZZ)I

css flexbox snippet:
https://gist.github.com/andrey-shikhov/f003d6c82ed307f6a1e24786207fcbeb

Result:

Android snippet:
`

    <LinearLayout android:layout_width="100dp"
                  android:orientation="horizontal"
                  android:layout_height="20dp">

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#fff"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#000"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#fff"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#000"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#fff"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#000"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#fff"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#000"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#fff"
                />

            <View
                android:layout_width="10dp"
                android:layout_height="match_parent"
                android:background="#000"
                />

    </LinearLayout>

    <com.google.android.flexbox.FlexboxLayout     xmlns:android="http://schemas.android.com/apk/res/android"
                                              android:layout_width="100dp"
                                              xmlns:app="http://schemas.android.com/apk/res-auto"
                                              app:flexDirection="column"
                                              android:layout_height="20dp">

            <View
                android:layout_width="20dp"
                android:layout_height="match_parent"
                android:layout_marginRight="20dp"
                android:background="#7b7bb9"
                app:layout_alignSelf="center"
                />

    </com.google.android.flexbox.FlexboxLayout>

</LinearLayout>

`
Result:

Seems to be css flexbox includes margin into the size of the item and after centers it, but in android flexbox centers item before and after applies margin.

Expected behavior:
same on both platforms.

There is an index mismatch between onMeasure and onLayout if the FlexLayout has a view whose visibility is gone.

Fixing it soon.

It would be nice to be able to specify a fixed amount of space between flex lines when using flexWrap="wrap" or flexWrap="wrap_reverse". This would handle the case when the FlexBoxLayout's width or height is wrap_content (where alignContent="space_between" and 'alignContent="space_around"` are not really applicable).

currently all the child in FlexboxLayout will push each other in the parent, there is no way to make the child view overlay show on other views.

FlexboxLayout#getFlexLines may return FlexLines including dummy ones (a FlexLine that doesn't have any flex items in it but used as determining alignment along the cross axis) depending on the alignContent property.

For example, when the alignContent property is set to center dummy flex lines are inserted as the first and the last flex lines.

The dummy flex lines need to be removed from the result of FlexboxLayout#getFlexLines.

I know, it's not a big deal but what do you think about removing hungarian notation from this repo?
In my opinion there is no positive reason to use that because here is the out side of AOSP.
Thx in advance.

Hope I'm using Flexbox correctly, but I occasionally see TextView within a Flexbox render text incorrectly.

Samsung S6; OS 5.1.1

Emulator; OS 6

To repro, add this layout

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:layout_width="match_parent"
    android:layout_height="wrap_content">

    <View
        android:layout_width="4dp"
        android:layout_height="match_parent"
        android:background="@color/primary1"/>

    <com.google.android.flexbox.FlexboxLayout
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:paddingBottom="4dp"
        android:paddingEnd="8dp"
        android:paddingLeft="8dp"
        android:paddingRight="8dp"
        android:paddingStart="8dp"
        android:paddingTop="4dp"
        app:flexWrap="wrap">

        <TextView
            android:id="@+id/content"
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
            android:layout_marginTop="8dp"
            android:textSize="14sp"
            app:layout_flexBasisPercent="100%"/>

    </com.google.android.flexbox.FlexboxLayout>
</LinearLayout>

and Activity

public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.comment_item_layout);
        TextView tv3 = (TextView) findViewById(R.id.content);
        tv3.setText(Html.fromHtml("<p>Since we&#x27;re on the subject of hard drives, I hope this will be helpful or " +
                "interesting:<p>It has been our experience that it is no longer possible to buy new, non-fraudulant " +
                "drives of <i>a sort of recent, but not brand new</i> drive model from Amazon.<p>So, for instance, in" +
                " early 2016 if you want to buy 4TB enterprise drives from Amazon, you will find them, they will be " +
                "classified as brand new, and they will be sold by some big amazon parts seller.<p>When you receive " +
                "them they will be nice and shiny brand new wrapped - perfectly sealed - and when you spin them up, " +
                "SMART stats will show 4000-6000 hours of use and that they are 2-3 years old.<p>This is almost " +
                "universal and has been happening for at least 3-4 years. These sellers are selling the drives as " +
                "brand new and they are anything but. When you complain, they will immediately exchange or refund - " +
                "there&#x27;s never a hassle there - and once in a while the seller will spout some bullshit about " +
                "the drives being &quot;new pulls&quot; ... that is, drives they stripped from unsold servers&#x2F;" +
                "desktops.<p>Hope that helps."));
    }
}

Support Lib Version: 23.3.0; CompileSDK 23; TargetSDK 22

FlexboxLayout is implemented as a subclass of the ViewGroup, so view recycles are not considered when used as a scrollable view (e.g. wrapped with the ScrollView).

Adding a new class as a subclass of RecyclerView.LayoutManager is more useful in that situation to take view recycles into account.

Android snippet:
https://gist.github.com/andrey-shikhov/6f65ca14bf3d44f0393a0f8ba6b9b764

Css snippet:
https://gist.github.com/andrey-shikhov/78d24b0724b1cc5f5690c2aa3597ddab

A Very weird behavior of children measuring when a child has only flexGrow value without width. In this example, android flexbox gives height to child equal to count of chars int text(child of child in flexbox).
It really different from css flexbox(css snippet above)