Skip to content

fix: prevent crashing due to JSException with WebView2#278

Open
SimonDD7 wants to merge 2 commits intoblazorblueprintui:developfrom
DragDay7:develop
Open

fix: prevent crashing due to JSException with WebView2#278
SimonDD7 wants to merge 2 commits intoblazorblueprintui:developfrom
DragDay7:develop

Conversation

@SimonDD7
Copy link
Copy Markdown

Description

Reloading page with some Blazor Blueprint components in standalone WebView2 app throws JSException JS object instance with ID X does not exist (has it been disposed?). It appears to be related to MAUI as I found the very same subject elsewhere - expected to be fixed but no ETA for this 2-3 year old issue.

Added code only to catch JSException on component disposals. Might not be needed here though.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • Refactoring (no functional changes)

Testing Checklist

  • Blazor Server
  • Blazor WebAssembly
  • Blazor Hybrid (MAUI)
  • Keyboard navigation / accessibility
  • Dark mode

Related Issues

Fixes similar case to #77 but with WebView2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant