如何通过JS/PHP在Android WebView中强制打开Chrome访问指定URL

Yes, you can absolutely make this work with both JavaScript (client-side) and PHP (server-side). Below is a step-by-step breakdown, including how to detect the WebView environment and the specific methods to launch Chrome.

Step 1: Detect the Android WebView Environment #

You mentioned checking the User Agent (UA) string—here's the concrete logic to distinguish Android WebViews from the full Chrome browser:

• Android WebViews typically include a Version/X.X substring in their UA, but do not include Chrome/X.X.
• Full Chrome for Android will have both Chrome/X.X and usually skip the Version/X.X part (or include it alongside Chrome).

We'll use this check in both JS and PHP implementations.

JavaScript Implementation (Client-Side) #

This approach intercepts link clicks directly in the page, blocks the WebView's default behavior, and uses an Android Intent URL to launch Chrome.

// Check if we're in an Android WebView (not full Chrome)
function isAndroidWebView() {
  const userAgent = navigator.userAgent;
  return /Android/.test(userAgent) && /Version\/\d+/.test(userAgent) && !/Chrome\/\d+/.test(userAgent);
}

// Intercept all link clicks
document.addEventListener('click', (e) => {
  const link = e.target.closest('a');
  if (link && link.href && isAndroidWebView()) {
    e.preventDefault(); // Stop the WebView from opening the link internally
    const targetUrl = link.href;
    
    // Construct the Chrome Intent URL (this is the magic part)
    const chromeIntent = `intent://${targetUrl.replace(/^https?:\/\//, '')}#Intent;scheme=https;package=com.android.chrome;end`;
    
    // Try to launch Chrome
    window.location.href = chromeIntent;
    
    // Fallback: If Chrome isn't installed, open in the default browser after a short delay
    setTimeout(() => {
      window.location.href = targetUrl;
    }, 1000);
  }
});

How This Works: #

• The isAndroidWebView() function validates the UA to confirm we're not in full Chrome.
• We listen for all click events, find the nearest <a> tag, and block the WebView's default navigation.
• The intent:// URL is a special Android scheme that tells the OS to open the target URL in the Chrome app (specified by package=com.android.chrome).
• The timeout fallback ensures users without Chrome still get to the link via their default browser.

PHP Implementation (Server-Side) #

If you prefer handling this on the server, you can detect the WebView UA and redirect directly to the Chrome Intent URL.

<?php
$userAgent = $_SERVER['HTTP_USER_AGENT'];
// Detect Android WebView
$isAndroidWebView = preg_match('/Android.*Version\/\d+/', $userAgent) && !preg_match('/Chrome\/\d+/', $userAgent);

// If we're in a WebView and a target URL is provided
if ($isAndroidWebView && isset($_GET['url'])) {
  $targetUrl = filter_var($_GET['url'], FILTER_SANITIZE_URL);
  // Strip the http/https prefix for the intent
  $cleanUrl = preg_replace('/^https?:\/\//', '', $targetUrl);
  $chromeIntent = "intent://{$cleanUrl}#Intent;scheme=https;package=com.android.chrome;end";
  
  header("Location: {$chromeIntent}");
  exit;
}
?>

<!-- Example link in your HTML -->
<a href="open_in_chrome.php?url=https://your-target-url.com">Open in Chrome</a>

How This Works: #

• The server checks the incoming UA string to identify WebViews.
• If a valid url parameter is provided, it constructs the Chrome Intent URL and redirects the WebView to it, triggering the OS to launch Chrome.

Key Notes & Troubleshooting #

• Chrome Installation Check: The intent will fail if Chrome isn't installed—this is why the JS fallback is important. For PHP, you could add a secondary redirect to the regular URL if the intent doesn't work (though server-side can't directly detect this, so a client-side fallback is still better).
• WebView Restrictions: Some apps (like Skype) might have WebView settings that limit intent launches. Test thoroughly in your target environment—if direct intent links don't work, try loading a small intermediate page that runs the JS click interception logic.
• HTTPS Requirement: Most modern WebViews and Android intents prefer HTTPS URLs. Stick to HTTPS for your target links to avoid issues.

内容的提问来源于stack exchange，提问作者Michael Emmet