IssueTracker

Well the work around for this is something like:

<android.support.design.widget.TextInputLayout
      android:id="@+id/setup_camera_access_login_input_layout"
      android:layout_width="match_parent"
      android:layout_height="wrap_content"
      app:errorEnabled="true"
      android:hint="@string/setup_camera_access_login_label"
      android:layout_marginBottom="@dimen/space_small"
      >
    <EditText
        style="@style/EditText"
        android:hint="@string/setup_camera_access_login_label"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        />
  </android.support.design.widget.TextInputLayout>

As setting the hint to something via attribute stops "setFloatingText" being called.

I agree with Gabriel on that. Adding method setHintEnabled(boolean) to TextInputLayout would be a great addition to current API. In my case I need to only show error text and use default EditText hint (not the TextInputLayout floating label).

Moreover, reserving space for both error and hint labels is not a great idea - those should be shown ONLY when needed (use View.GONE instead of View.INVISIBLE).

#3: No, forms are supposed to be visually stable. You don't want everything moving just because an error has happened somewher.

@Chris Banes

Don't misunderstand me. It's ok to reserve space if someone is constantly using error, counter or hint label.

But if I do explicit call to setErrorEnabled(false) or setCounterEnabled(false) I'm 100% sure I don't need that particular feature in place where I call this method and I don't want to waste precious layout space.

has there is some workaround for it?

Released in v23.2.0.