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

[WebView] Support opening WebView links in external browser on iOS #1355

Closed

Conversation

masonicboom
Copy link

No description provided.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 20, 2015
@@ -17,6 +17,7 @@
@property (nonatomic, assign) UIEdgeInsets contentInset;
@property (nonatomic, assign) BOOL shouldInjectAJAXHandler;
@property (nonatomic, assign) BOOL automaticallyAdjustContentInsets;
@property (nonatomic, assign) BOOL openLinksInExternalBrowser;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BOOL openLinksInExternalBrowser;

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@a2 What does that mean? Does that line have a mistake?

@arunshan
Copy link

I tried using your PR and I am not able to get the links to open in external browser. I think this only works with but not with jquery on click listeners.

@masonicboom
Copy link
Author

@arunshan can you post some code that exposes the issue you're seeing?

@brentvatne brentvatne changed the title Support opening WebView links in external browser on iOS [WebView] Support opening WebView links in external browser on iOS Jun 1, 2015
@ghost
Copy link

ghost commented Aug 5, 2015

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

@paramaggarwal
Copy link
Contributor

@arunshan Yes, that is expected. The URL is never seen by the native webview itself if the click is handled completely by jQuery/JS. It would be an AJAX call and not a complete page reload.

All, any other concerns with this PR?

@satya164
Copy link
Contributor

Any updates on this?

@facebook-github-bot
Copy link
Contributor

@masonicboom updated the pull request.

@satya164
Copy link
Contributor

Closing since no activity on the PR. let's re-open if you wanna work on it again.

@satya164 satya164 closed this Jan 26, 2016
ayushjainrksh pushed a commit to MLH-Fellowship/react-native that referenced this pull request Jul 2, 2020
* removed v0.5

* remove easily and swap obvious

* remove just and swap easy

* fixes for s thru end of alphabet

* a thru e

* f thru m

* last of them except navigator

* oops idk why i put that inline

* last fixes for pop

* pr resolve conflict

* update ignore rule to include the word

* add back 0.6
hsjoberg pushed a commit to hsjoberg/react-native that referenced this pull request Aug 25, 2022
…nks (facebook#1355)

Messenger Desktop is a multi-window application (chat, calling, settings, …) and we maintain the various windows with a windowNativeModule which allows JS interaction.

When receiving deep-links from other apps we don’t want to necessary re-open the lastWindow open as the deep-link might contain information about a particular scenario (open login page, start a call). Hence, we need to disable this behavior app wide and use our windowNativeModule to forward the specific window related to the deep link.

- This change has 0 effect on other apps
- We could make this property an ivar, but then we need to manually register RCTLinkingManager.mm ….
- We could append a special url property to deep-links, but I think that would make the ‘API’ harder to use`
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants