Skip to content

Conversation

@captainsafia
Copy link
Member

Description

This PR reverts a change that was introduced in #23224 to ensure that circuits are not disconnected when protocol-based links (e.g. mailto: and tel:) are clicked or a download is programmatically triggered. This PR also:

  • Adds E2E tests for newly-identified customer scenarios
  • Adds an JavaScript API to give customers the flexibility to disconnect Blazor circuits whenever they want

Customer Impact

This change was made in response to customer feedback that a recent bug fix broke important scenarios for users. Without this change, customer applications that use protocol-based links or programmatic downloads would break.

Regression

This is a regression from a previous patch release of 3.1.

Risk

The risk of this change is low:

  • New end-to-end tests were added for the discovered scenarios
  • API was provided for users who want control over when disconnect call is made

* Add tests for failing disconnect scenarios

* Remove beforeunload call and add public API

* Add additional test case

* Update src/Components/test/testassets/BasicTestApp/GracefulTermination.razor

Co-authored-by: Steve Sanderson <[email protected]>

Co-authored-by: Steve Sanderson <[email protected]>
@ghost ghost added the area-blazor Includes: Blazor, Razor Components label Oct 14, 2020
@captainsafia captainsafia added this to the 3.1.x milestone Oct 14, 2020
@captainsafia captainsafia added the Servicing-consider Shiproom approval is required for the issue label Oct 14, 2020
@ghost
Copy link

ghost commented Oct 14, 2020

Hello human! Please make sure you've included the Shiproom Template in a comment or (preferably) the PR description. Also, make sure this PR is not marked as a draft and is ready-to-merge.

@mkArtakMSFT mkArtakMSFT added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Oct 15, 2020
@mkArtakMSFT mkArtakMSFT modified the milestones: 3.1.x, 3.1.10 Oct 15, 2020
@mkArtakMSFT
Copy link
Contributor

This was approved by tactics / @SteveCarrollMSFT
/cc @leecow FYI

@mkArtakMSFT
Copy link
Contributor

@dotnet/aspnet-blazor-eng this is approved. Please review so we can get this merged.

@captainsafia captainsafia merged commit 2eb851a into release/3.1 Oct 15, 2020
@captainsafia captainsafia deleted the safia/revert-disconnect branch October 15, 2020 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-blazor Includes: Blazor, Razor Components Servicing-approved Shiproom has approved the issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants