fix(compare): horizontally scrollable comparison table on mobile - #1735

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Files matching PwaInstallButton:\n'
fd -a 'PwaInstallButton\.svelte$' . || true

printf '\nRelevant file outline:\n'
file="$(fd 'PwaInstallButton\.svelte$' . | head -n 1)"
if [ -n "${file:-}" ]; then
  wc -l "$file"
  ast-grep outline "$file" || true
  printf '\nFile contents with line numbers:\n'
  cat -n "$file"
fi

printf '\nSearch for pwaInstallStore / handleAppInstalled / install_success references:\n'
rg -n "pwaInstallStore|handleAppInstalled|install_success|appinstalled|userChoice|beforeinstallprompt" .

Repository: openfoodfacts/openfoodfacts-explorer

Length of output: 4605

🌐 Web query:

MDN BeforeInstallPromptEvent appinstalled event userChoice accepted developer.mozilla.org

💡 Result:

The BeforeInstallPromptEvent, userChoice, and appinstalled event are related components of the Progressive Web App (PWA) installation process, primarily supported in Chromium-based browsers [1][2]. BeforeInstallPromptEvent and userChoice When a browser detects that a web app is installable, it fires a beforeinstallprompt event [3]. If a developer catches this event (and calls event.preventDefault() to suppress the default browser prompt), they can save the event object and trigger a custom installation prompt later by calling the prompt() method [1][3]. The prompt() method returns a Promise that resolves with a userChoice object [4][2]. This object contains: - outcome: A string that is either "accepted" (the user clicked to install) or "dismissed" (the user closed the prompt) [5][4]. - platform: A string indicating the selected platform if the user accepted the installation [5][6]. appinstalled Event While userChoice allows developers to track the outcome of a specific prompt triggered via their own UI, it does not cover installations triggered through other browser UI mechanisms (e.g., the browser's address bar icon) [7]. The appinstalled event is the recommended way to track successful installations regardless of how they were initiated [7][8]. This event fires on the global window object as soon as the browser has successfully installed the page as an application [9]. It is commonly used by developers to hide custom in-app install promotions once the application is already installed [1][8].

Citations:

• 1: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/How_to/Trigger_install_prompt
• 2: https://developer.mozilla.org/en-US/docs/Web/API/BeforeInstallPromptEvent
• 3: https://developer.mozilla.org/en-US/docs/Web/API/Window/beforeinstallprompt_event
• 4: https://developer.mozilla.org/en-US/docs/Web/API/BeforeInstallPromptEvent/prompt
• 5: https://developer.mozilla.org/en-US/docs/Web/API/BeforeInstallPromptEvent/userChoice
• 6: https://github.com/mdn/content/blob/main/files/en-us/web/api/beforeinstallpromptevent/userchoice/index.md?plain=1
• 7: https://web.dev/articles/customize-install
• 8: https://web.dev/learn/pwa/detection
• 9: https://developer.mozilla.org/en-US/docs/Web/API/Window/appinstalled_event

🌐 Web query:

Chrome appinstalled event fires after beforeinstallprompt userChoice resolved accepted duplicate appinstalled

💡 Result:

The appinstalled event and the userChoice promise from the beforeinstallprompt event serve distinct purposes and are triggered by different stages of the installation process [1][2]. The userChoice promise resolves as soon as the user responds to the browser's install dialog (e.g., clicking "Install" or "Cancel") [3][2]. It provides the outcome of that specific interaction (either 'accepted' or 'dismissed') [3][4]. The appinstalled event fires only after the browser has successfully completed the installation of the Progressive Web App (PWA) [5]. While the userChoice promise indicates the user's intent to install, the appinstalled event serves as confirmation that the installation has actually occurred [1][6]. Because these events track different points in the lifecycle, appinstalled typically fires after the userChoice promise has resolved with an 'accepted' outcome, provided the installation succeeds [1][5]. Note that the appinstalled event is intended to fire regardless of the installation mechanism—whether triggered by your own UI via prompt or by the browser's own automated prompts [1][7]. Developers should use userChoice to track user intent and analytics, and use appinstalled to confirm the successful installation of the application [1][2].

Citations:

• 1: https://web.dev/articles/customize-install
• 2: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/How_to/Trigger_install_prompt
• 3: https://developer.mozilla.org/en-US/docs/Web/API/BeforeInstallPromptEvent/userChoice
• 4: https://developer.chrome.com/blog/app-install-banners-native
• 5: https://www.w3.org/TR/2019/WD-appmanifest-20190925/
• 6: https://stackoverflow.com/questions/60320837/appinstalled-event-is-fired-prematurely
• 7: https://web.dev/learn/pwa/installation-prompt