-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make text wrap examples not rely on the RNTester window width #44505
Conversation
This pull request was exported from Phabricator. Differential Revision: D57166025 |
…ok#44505) Summary: # Changelist: [Internal] - The RNTester/Text tests, that are related to text wrapping (such as "wrap mode", "ellipsize", "numberOfLines" ones) were written with the mobile form factor in mind, whereas the RNTester window is generally expected to be narrow and tall. Now, that we are running on other platforms as well, there is no guarantee about the RNTester window width, in general, so these tests relying on particular window width is not practical anymore. This makes the corresponding tests work in a useful way without making assumptions about the RNTester's window width. Differential Revision: D57166025
This pull request was exported from Phabricator. Differential Revision: D57166025 |
…ok#44505) Summary: # Changelist: [Internal] - The RNTester/Text tests, that are related to text wrapping (such as "wrap mode", "hyphenation", "ellipsize", "numberOfLines" ones) were written with the mobile form factor in mind, whereas the RNTester window is generally expected to be narrow and tall. Now, that we are running on other platforms as well, there is no guarantee about the RNTester window width, in general, so these tests relying on particular window width is not practical anymore. This makes the corresponding tests work in a useful way without making assumptions about the RNTester's window width. Differential Revision: D57166025
This pull request was exported from Phabricator. Differential Revision: D57166025 |
This pull request has been merged in f4996e0. |
This pull request was successfully merged by @rshest in f4996e0. When will my fix make it into a release? | How to file a pick request? |
Summary: # Changelog: [Internal] - A follow-up to facebook#44505, turns out this is also an issue for TextInput examples, which work of assumption of some of the text input fields being of limited width, but in practice growing to occupy the parent window width, which can be quite large on platforms different from the classic mobile ones. This diff makes the corresponding tests more practical, not expanding to the parent window anymore. Differential Revision: D57196308
…ook#44517) Summary: # Changelog: [Internal] - A follow-up to facebook#44505, turns out this is also an issue for TextInput examples, which work of assumption of some of the text input fields being of limited width, but in practice growing to occupy the parent window width, which can be quite large on platforms different from the classic mobile ones. This diff makes the corresponding tests more practical, not expanding to the parent window anymore. Differential Revision: D57196308
Summary: Pull Request resolved: #44517 # Changelog: [Internal] - A follow-up to #44505, turns out this is also an issue for TextInput examples, which work of assumption of some of the text input fields being of limited width, but in practice growing to occupy the parent window width, which can be quite large on platforms different from the classic mobile ones. This diff makes the corresponding tests more practical, not expanding to the parent window anymore. Reviewed By: christophpurrer Differential Revision: D57196308 fbshipit-source-id: 7018e8c51adb70fe6a03e50d71eff9ba997fd07a
…ok#44505) Summary: Pull Request resolved: facebook#44505 # Changelog: [Internal] - The RNTester/Text tests, that are related to text wrapping (such as "wrap mode", "hyphenation", "ellipsize", "numberOfLines" ones) were written with the mobile form factor in mind, whereas the RNTester window is generally expected to be narrow and tall. Now, that we are running on other platforms as well, there is no guarantee about the RNTester window width, in general, so these tests relying on particular window width is not practical anymore. This makes the corresponding tests work in a useful way without making assumptions about the RNTester's window width. Differential Revision: D57166025 fbshipit-source-id: 3305a31f7ca254d82c85d67c975c1140050adc28
…ook#44517) Summary: Pull Request resolved: facebook#44517 # Changelog: [Internal] - A follow-up to facebook#44505, turns out this is also an issue for TextInput examples, which work of assumption of some of the text input fields being of limited width, but in practice growing to occupy the parent window width, which can be quite large on platforms different from the classic mobile ones. This diff makes the corresponding tests more practical, not expanding to the parent window anymore. Reviewed By: christophpurrer Differential Revision: D57196308 fbshipit-source-id: 7018e8c51adb70fe6a03e50d71eff9ba997fd07a
Summary:
Changelist:
[Internal] -
The RNTester/Text tests, that are related to text wrapping (such as "wrap mode", "ellipsize", "numberOfLines" ones) were written with the mobile form factor in mind, whereas the RNTester window is generally expected to be narrow and tall.
Now, that we are running on other platforms as well, there is no guarantee about the RNTester window width, in general, so these tests relying on particular window width is not practical anymore.
This makes the corresponding tests work in a useful way without making assumptions about the RNTester's window width.
Differential Revision: D57166025