Skip to content
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

Fix compose box obscured by keyboard on long message, in stream view. #3595

Merged
merged 1 commit into from
Aug 27, 2019

Conversation

jainkuniya
Copy link
Member

Fixes: #3369

@jainkuniya jainkuniya self-assigned this Aug 25, 2019
@gnprice gnprice merged commit 3574b12 into zulip:master Aug 27, 2019
@gnprice
Copy link
Member

gnprice commented Aug 27, 2019

Thanks @jainkuniya ! Merged.

rk-for-zulip added a commit to rk-for-zulip/zulip-mobile that referenced this pull request Oct 4, 2019
At present, when loading content into the WebView, we inject all
non-image assets as part of the generated HTML. This is more than a
bit wasteful, considering that large swaths of the supporting CSS and
JavaScript is entirely static from invocation to invocation;
additionally, it makes KaTeX support somewhere between "nontrivial"
and "impossible".

This commit creates a build subsystem which can inject static
webview-supporting assets into the application bundle, into a
`webview` directory.

We also create a stub directory for the subsystem copy assets from; at
present this contains only a README.md file (which will *not* be
copied), but this will be expanded in the following series of commits.

Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many
other issues.
rk-for-zulip added a commit to rk-for-zulip/zulip-mobile that referenced this pull request Oct 4, 2019
At present, when loading content into the WebView, we inject all
non-image assets as part of the generated HTML. This is more than a
bit wasteful, considering that large swaths of the supporting CSS and
JavaScript is entirely static from invocation to invocation;
additionally, it makes KaTeX support somewhere between "nontrivial"
and "impossible".

This commit creates a build subsystem which can inject static
webview-supporting assets into the application bundle, into a
`webview` directory.

We also create a stub directory for the subsystem to copy assets from;
at present this contains only a README.md file (which will *not* be
copied), but this will be expanded in the following series of commits.

Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many
other issues.
rk-for-zulip added a commit to rk-for-zulip/zulip-mobile that referenced this pull request Oct 9, 2019
At present, when loading content into the WebView, we inject all
non-image assets as part of the generated HTML. This is more than a
bit wasteful, considering that large swaths of the supporting CSS and
JavaScript is entirely static from invocation to invocation;
additionally, it makes KaTeX support somewhere between "nontrivial"
and "impossible".

This commit creates a build subsystem which can inject static
webview-supporting assets into the application bundle, into a
`webview` directory.

We also create a stub directory for the subsystem to copy assets from;
at present this contains only a README.md file (which will *not* be
copied), but this will be expanded in the following series of commits.

Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many
other issues.
rk-for-zulip added a commit to rk-for-zulip/zulip-mobile that referenced this pull request Oct 10, 2019
At present, when loading content into the WebView, we inject all
non-image assets as part of the generated HTML. This is more than a
bit wasteful, considering that large swaths of the supporting CSS and
JavaScript is entirely static from invocation to invocation;
additionally, it makes KaTeX support somewhere between "nontrivial"
and "impossible".

This commit creates a build subsystem which can inject static
webview-supporting assets into the application bundle, into a
`webview` directory.

We also create a stub directory for the subsystem to copy assets from;
at present this contains only a README.md file (which will *not* be
copied), but this will be expanded in the following series of commits.

Inspired by zulip#2690. Assists with zulip#2660, zulip#3595, and potentially many
other issues.
gnprice pushed a commit that referenced this pull request Oct 11, 2019
At present, when loading content into the WebView, we inject all
non-image assets as part of the generated HTML. This is more than a
bit wasteful, considering that large swaths of the supporting CSS and
JavaScript is entirely static from invocation to invocation;
additionally, it makes KaTeX support somewhere between "nontrivial"
and "impossible".

This commit creates a build subsystem which can inject static
webview-supporting assets into the application bundle, into a
`webview` directory.

We also create a stub directory for the subsystem to copy assets from;
at present this contains only a README.md file (which will *not* be
copied), but this will be expanded in the following series of commits.

Inspired by #2690. Assists with #2660, #3595, and potentially many
other issues.
jainkuniya added a commit to jainkuniya/zulip-mobile that referenced this pull request Jul 19, 2020
Remove scroll view from input wrapper (which was added in zulip#3595).
This fixed zulip#3614. Also just checked it works fine on Android as well. So
basically zulip#3595 was not a completely right solution for zulip#3369.

Now inputs are wrapped with simple view, which is self aligned as
vertically center. ComposeMenu and SendButton are self aligned as
vertically end. And wrapper of all this three has justifyContent
as space-between, which makes them spread whole over horizontal space
available.

This removes alignItems: 'flex-end' from `composeBox`, which was pushing
input to vertically bottom, idealy it should be at vertically center.

Fixes: zulip#3614
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compose box obscured by keyboard on long message, in stream view
2 participants