You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has been over three months since the first final version of the Foundry
18
-
release has been made public. Today, I am glad to announce the release of the
19
-
6.2 version! This new version focuses on two areas of improvements:
18
+
release has been made public. Today, I am glad to announce the release of the 6.2 version! This new version focuses on two areas of
19
+
improvements:
20
20
21
21
1.[Accessibility](https://en.wikipedia.org/wiki/Computer_accessibility), and more specifically integration with _VoiceOver_ and _TalkBack_ screen readers;
22
22
2. Richer [model-based
@@ -168,8 +168,9 @@ This is where <APIReference name="HTMLElementModel" member="getReactNativeProps"
168
168
169
169
The purpose of this field is identical to <APIReferencename="HTMLElementModel"
170
170
member="reactNativeProps" /> field. It only differs in that instead of a plain
171
-
object, it is a method which takes two arguments, `tnode` (the Transient Node)
172
-
and `element` (the DOM node) and returns a plain object (see <APIReference
171
+
object, it is a method which takes three arguments. A `tnode` (the Transient Node),
172
+
the `preGeneratedProps` (props generated by the TRE such as accessibility props, see next section)
173
+
and and `element` (the DOM node). Finally, it returns a plain object (see <APIReference
173
174
name="ReactNativePropsDefinitions" />).
174
175
175
176
In the example below, a custom `nav-widget` tag is registered. This time, we
0 commit comments