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

[Docs] Fix scrolling issue on iOS devices. #7731

Closed
wants to merge 1 commit into from
Closed

[Docs] Fix scrolling issue on iOS devices. #7731

wants to merge 1 commit into from

Conversation

Andreyco
Copy link
Contributor

@Andreyco Andreyco commented May 25, 2016

It was not possible to scroll due to overlaying (and visually not present) docs navigation layer.

Fixes issue introduced in PR #7669, see this comment
Additionally, script makes sure only single target is "in" and closes any other target with "in" state.

@facebook-github-bot
Copy link
Contributor

By analyzing the blame information on this pull request, we identified @vjeux and @janicduplessis to be potential reviewers.

@facebook-github-bot facebook-github-bot added GH Review: review-needed CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. labels May 25, 2016
@vjeux
Copy link
Contributor

vjeux commented May 25, 2016

@facebook-github-bot shipit

@vjeux
Copy link
Contributor

vjeux commented May 25, 2016

Thanks!!

@ghost ghost added GH Review: accepted Import Started This pull request has been imported. This does not imply the PR has been approved. and removed GH Review: review-needed labels May 25, 2016
@ghost
Copy link

ghost commented May 25, 2016

Thanks for importing. If you are an FB employee go to Phabricator to review.

@ghost ghost added Import Failed and removed Import Started This pull request has been imported. This does not imply the PR has been approved. labels May 25, 2016
@ghost
Copy link

ghost commented May 25, 2016

I tried to merge this pull request into the Facebook internal repo but some checks failed. To unblock yourself please check the following: Does this pull request pass all open source tests on GitHub? If not please fix those. Does the code still apply cleanly on top of GitHub master? If not can please rebase. In all other cases this means some internal test failed, for example a part of a fb app won't work with this pull request. I've added the Import Failed label to this pull request so it is easy for someone at fb to find the pull request and check what failed. If you don't see anyone comment in a few days feel free to comment mentioning one of the core contributors to the project so they get a notification.

@janicduplessis
Copy link
Contributor

Import failed because of a merge conflict.

@vjeux
Copy link
Contributor

vjeux commented May 25, 2016

what @janicduplessis said, would you mind rebasing?

@ghost
Copy link

ghost commented May 30, 2016

@Andreyco updated the pull request.

1 similar comment
@ghost
Copy link

ghost commented May 30, 2016

@Andreyco updated the pull request.

@Andreyco
Copy link
Contributor Author

@janicduplessis @vjeux sorry for little delay, fork is up to date

@janicduplessis
Copy link
Contributor

@facebook-github-bot shipit

@ghost ghost added the Import Started This pull request has been imported. This does not imply the PR has been approved. label May 30, 2016
@ghost
Copy link

ghost commented May 30, 2016

Thanks for importing. If you are an FB employee go to Phabricator to review.

@vjeux
Copy link
Contributor

vjeux commented May 30, 2016

fbobjc/Libraries/FBReactKit/js/react-native-github/website/src/react-native/css/react-native.css
Hunk #1 FAILED at 480
Hunk #2 FAILED at 554
2 out of 2 hunks FAILED -- saving rejects to file fbobjc/Libraries/FBReactKit/js/react-native-github/website/src/react-native/css/react-native.css.rej
patching file fbandroid/java/com/facebook/catalyst/js/react-native-github/website/src/react-native/css/react-native.css
Hunk #1 FAILED at 480
Hunk #2 FAILED at 554

@Andreyco
Copy link
Contributor Author

I see, but have no idea why it's failing... Any heads up? TY

@vjeux
Copy link
Contributor

vjeux commented May 30, 2016

I think that the issue is that when we do the patch, it's against the 9 days ago version and not master. Could you update it such it is only one commit on-top of master?

screen shot 2016-05-31 at 12 57 13 am

It was not possible to scroll due to overlaying (and visually not present) docs navigation layer.
@ghost
Copy link

ghost commented May 30, 2016

@Andreyco updated the pull request.

@Andreyco
Copy link
Contributor Author

PR is single commit and on top of master branch.

@vjeux
Copy link
Contributor

vjeux commented May 30, 2016

@facebook-github-bot shipit

@ghost
Copy link

ghost commented May 30, 2016

Thanks for importing. If you are an FB employee go to Phabricator to review.

@ghost ghost closed this in d31a54a May 31, 2016
mkonicek pushed a commit that referenced this pull request Jun 6, 2016
Summary:
It was not possible to scroll due to overlaying (and visually not present) docs navigation layer.

Fixes issue introduced in PR #7669, see this [comment](#7669 (comment))
Additionally, script makes sure only single target is "in" and closes any other target with "in" state.
Closes #7731

Differential Revision: D3344927

Pulled By: vjeux

fbshipit-source-id: b2c64d90a2a6e531a9be79b936d6a5da61a69b22
zebulgar pushed a commit to nightingale/react-native that referenced this pull request Jun 18, 2016
Summary:
It was not possible to scroll due to overlaying (and visually not present) docs navigation layer.

Fixes issue introduced in PR facebook#7669, see this [comment](facebook#7669 (comment))
Additionally, script makes sure only single target is "in" and closes any other target with "in" state.
Closes facebook#7731

Differential Revision: D3344927

Pulled By: vjeux

fbshipit-source-id: b2c64d90a2a6e531a9be79b936d6a5da61a69b22
bubblesunyum pushed a commit to iodine/react-native that referenced this pull request Aug 23, 2016
Summary:
It was not possible to scroll due to overlaying (and visually not present) docs navigation layer.

Fixes issue introduced in PR facebook#7669, see this [comment](facebook#7669 (comment))
Additionally, script makes sure only single target is "in" and closes any other target with "in" state.
Closes facebook#7731

Differential Revision: D3344927

Pulled By: vjeux

fbshipit-source-id: b2c64d90a2a6e531a9be79b936d6a5da61a69b22
mpretty-cyro pushed a commit to HomePass/react-native that referenced this pull request Aug 25, 2016
Summary:
It was not possible to scroll due to overlaying (and visually not present) docs navigation layer.

Fixes issue introduced in PR facebook#7669, see this [comment](facebook#7669 (comment))
Additionally, script makes sure only single target is "in" and closes any other target with "in" state.
Closes facebook#7731

Differential Revision: D3344927

Pulled By: vjeux

fbshipit-source-id: b2c64d90a2a6e531a9be79b936d6a5da61a69b22
react-one pushed a commit to react-one/react-native that referenced this pull request Sep 24, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Import Started This pull request has been imported. This does not imply the PR has been approved.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants