Welcome to the Blazor feedback portal. We’re happy you’re here! If you have feedback on how to improve the Blazor, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote
When testing different dialog sizes, window sizes, resolutions, devices, sometimes the PDFViewer Form Fields throw an exception causing form fields to be unfillable. Listed below.

Empty


Which corresponds to 

this.onWindowTouchEnd = function(e) {

    t.signatureAdded = !1,

    t.pdfViewer.element.contains(e.target) ||

    t.contextMenuModule.contextMenuElement.contains(e.target) || 

    t.pdfViewer.textSelectionModule && !t.isTextSelectionDisabled && t.pdfViewer.textSelectionModule.clearTextSelection()

}


Tested with your PdfViewerServer Modal example:

<div id="target" style="width:800px;height:500px">
    <SfButton @onclick="OnClick">Open PDF Viewer</SfButton>
    <SfDialog @ref="@dialog" Target="#target" Width="50vw" Visible="false" IsModal="true" Header=
    "@Header" ShowCloseIcon="true">
    <DialogEvents OnOpen="OnOpen"></DialogEvents>
<SfPdfViewerServer @ref="@viewer"/>
</SfDialog>
</div>

This code will break the fillable element but if you change the SfDialog size to:

 <SfDialog @ref="@dialog" Target="#target" Width="70vw" Visible="false" IsModal="true" Header=

Then the fillable elements will work.


I'm not exactly sure what's happening here, but it seems to be when the container is below some certain size threshold, mainly discovered in partial window sizes and mobile device aspect ratios.