From ad86bd1e7561cdf216f9bcb7cc2ff3e27a49d1ff Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Thu, 27 Feb 2020 00:03:08 +0000 Subject: [PATCH] Deploy website Deploy website version based on 49afce0c473e279e77bd0442b39d34202b505565 --- ...input-accessory-view-for-react-native.html | 4 +- .../index.html | 4 +- blog/page2/index.html | 4 +- docs/next/appstate.html | 143 ++++++++++++++---- docs/next/appstate/index.html | 143 ++++++++++++++---- docs/next/network.html | 8 +- docs/next/network/index.html | 8 +- 7 files changed, 246 insertions(+), 68 deletions(-) diff --git a/blog/2018/03/22/building-input-accessory-view-for-react-native.html b/blog/2018/03/22/building-input-accessory-view-for-react-native.html index 9d920d85688..8dd103b6744 100644 --- a/blog/2018/03/22/building-input-accessory-view-for-react-native.html +++ b/blog/2018/03/22/building-input-accessory-view-for-react-native.html @@ -71,7 +71,7 @@

Building <InputAccessoryView> For React Native

March 22, 2018

Peter ArganySoftware Engineer at Facebook

Peter Argany

Motivation

Three years ago, a GitHub issue was opened to support input accessory view from React Native.

-

In the ensuing years, there have been countless '+1s', various workarounds, and zero concrete changes to RN on this issue - until today. Starting with iOS, we're exposing an API for accessing the native input accessory view and we are excited to share how we built it.

+

In the ensuing years, there have been countless '+1s', various workarounds, and zero concrete changes to RN on this issue - until today. Starting with iOS, we're exposing an API for accessing the native input accessory view and we are excited to share how we built it.

Background

What exactly is an input accessory view? Reading Apple's developer documentation, we learn that it's a custom view which can be anchored to the top of the system keyboard whenever a receiver becomes the first responder. Anything that inherits from UIResponder can redeclare the .inputAccessoryView property as read-write, and manage a custom view here. The responder infrastructure mounts the view, and keeps it in sync with the system keyboard. Gestures which dismiss the keyboard, like a drag or tap, are applied to the input accessory view at the framework level. This allows us to build content with interactive keyboard dismissal, an integral feature in top-tier messaging apps like iMessage and WhatsApp.

There are two common use cases for anchoring a view to the top of the keyboard. The first is creating a keyboard toolbar, like the Facebook composer background picker.

@@ -140,7 +140,7 @@

Another example for Sticky Text Inputs can be found in the repository.

When will I be able to use this?

-

The full commit for this feature implementation is here. <InputAccessoryView> will be available in the upcoming v0.55.0 release.

+

The full commit for this feature implementation is here. <InputAccessoryView> will be available in the upcoming v0.55.0 release.

Happy keyboarding :)

Recent Posts

Building <InputAccessoryView> For React Native

March 22, 2018

Peter ArganySoftware Engineer at Facebook

Peter Argany

Motivation

Three years ago, a GitHub issue was opened to support input accessory view from React Native.

-

In the ensuing years, there have been countless '+1s', various workarounds, and zero concrete changes to RN on this issue - until today. Starting with iOS, we're exposing an API for accessing the native input accessory view and we are excited to share how we built it.

+

In the ensuing years, there have been countless '+1s', various workarounds, and zero concrete changes to RN on this issue - until today. Starting with iOS, we're exposing an API for accessing the native input accessory view and we are excited to share how we built it.

Background

What exactly is an input accessory view? Reading Apple's developer documentation, we learn that it's a custom view which can be anchored to the top of the system keyboard whenever a receiver becomes the first responder. Anything that inherits from UIResponder can redeclare the .inputAccessoryView property as read-write, and manage a custom view here. The responder infrastructure mounts the view, and keeps it in sync with the system keyboard. Gestures which dismiss the keyboard, like a drag or tap, are applied to the input accessory view at the framework level. This allows us to build content with interactive keyboard dismissal, an integral feature in top-tier messaging apps like iMessage and WhatsApp.

There are two common use cases for anchoring a view to the top of the keyboard. The first is creating a keyboard toolbar, like the Facebook composer background picker.

@@ -140,7 +140,7 @@

Another example for Sticky Text Inputs can be found in the repository.

When will I be able to use this?

-

The full commit for this feature implementation is here. <InputAccessoryView> will be available in the upcoming v0.55.0 release.

+

The full commit for this feature implementation is here. <InputAccessoryView> will be available in the upcoming v0.55.0 release.

Happy keyboarding :)

Recent Posts