Pop the fragment in the backstack when custom tab is active and the onCloseWindow window callback of the BrowserChromeClient is triggered

[catalinradoiu]

Task/Issue URL: https://app.asana.com/1/137249556945/project/1211724162604201/task/1206984821130536?focus=true

Description

Custom tabs were not properly handling window closure during single sign-on flows. When an SSO flow opened a new window (which adds a fragment to the backstack), the window.close() callback from the OAuth provider would attempt to use regular browser tab logic (removing from tab repository and updating tab selection). This approach failed in custom tabs because they don't use the tab repository concept - they manage navigation through fragment backstack transactions. As a result, the SSO window remained open and prevented the login callback code from executing on the previous fragment, breaking the authentication flow.

Solution
Added custom tab-specific handling for window closure. When closeCurrentTab() is called in a custom tab context, it now triggers a fragment backstack pop operation instead of attempting repository-based tab removal. This properly closes the SSO fragment and returns to the calling fragment, allowing the authentication callback to execute correctly. Regular browser tabs continue to use the existing repository-based logic, ensuring no regression in standard tab behavior.

Steps to test this PR

Check steps in the attached task.

UI changes

No UI changes, only behavior changes.

---

Note

Introduce NavigateBackInCustomTab so closing in custom tabs pops the fragment back stack rather than deleting a tab; wire it in ViewModel/Fragment and add tests.

• Behavior change (Custom Tabs):
  • Add Command.NavigateBackInCustomTab.
  • Update BrowserTabViewModel.closeCurrentTab() to emit NavigateBackInCustomTab when isCustomTabScreen is true; otherwise keep deleting the tab from repository.
  • Handle NavigateBackInCustomTab in BrowserTabFragment by popping the fragment back stack when active custom tab.
• Tests:
  • Adjust/expand tests to cover non-custom-tab deletion path and custom tab back navigation command emission.

^{Written by Cursor Bugbot for commit 32d48b3. This will update automatically on new commits. Configure here.}

[catalinradoiu]

• Pop the fragment in the backstack when custom tab is active and the onCloseWindow window callback of the BrowserChromeClient is triggered #7410 👈 (View in Graphite)
• develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

Bug: Personal debug tag accidentally committed in log statement

The logcat call was changed from using the default tag to a personal debug tag "RadoiuC" (matching the author's name). This appears to be a debugging artifact that was unintentionally included. The log statement previously used the default class-based tag, which is more appropriate for production code.

 

[catalinradoiu]

reverted