Client-side PDF Viewer fails when EnableToolbar="false" (18.3.0.35)

I have a client-side Blazor app and use the SfPdfViewer.  I use a custom toolbar and not the built-in one.  In v18.3.0.35, when I set EnableToolbar="false", this breaks the PDF Viewer.  I see errors like this in Visual Studio:

Cannot read property 'appendChild' of null
TypeError: Cannot read property 'appendChild' of null
    at t.createFileElement (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1381949)
    at t.intializeToolbar (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1351258)
    at t.initializeComponent (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1097694)
    at i.render (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1523694)
    at i.r.appendTo (http://localhost:64374/_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js:1:100247)
    at Object.initialize (http://localhost:64374/_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js:1:149360)
    at http://localhost:64374/_framework/blazor.webassembly.js:1:9805
    at new Promise ()
    at Object.beginInvokeJSFromDotNet (http://localhost:64374/_framework/blazor.webassembly.js:1:9773)
    at _mono_wasm_invoke_js_marshalled (http://localhost:64374/_framework/wasm/dotnet.3.2.0.js:1:171294)

Cannot read property 'style' of null
TypeError: Cannot read property 'style' of null
    at t.closeCommentPanelContainer (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1038098)
    at t.clear (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1054174)
    at t.clear (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1118972)
    at i.load (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1527990)
    at i.onPropertyChanged (http://localhost:64374/_content/Syncfusion.Blazor/scripts/pdfviewer-5b82fd.min.js:1:1525094)
    at i.e.dataBind (http://localhost:64374/_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js:1:83368)
    at i.r.dataBind (http://localhost:64374/_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js:1:100500)
    at i.e.setProperties (http://localhost:64374/_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js:1:82586)
    at Object.setModel (http://localhost:64374/_content/Syncfusion.Blazor/scripts/syncfusion-blazor.min.js:1:149904)
    at http://localhost:64374/_framework/blazor.webassembly.js:1:9805


Regards,
Arthur

2 Replies 1 reply marked as answer

AA Akshaya Arivoli Syncfusion Team October 6, 2020 12:20 PM UTC

Hi Arthur , 

Thank you for contacting Syncfusion support. 

We were able to reproduce the reported issue and confirmed that the issue is defect. We will fix the issue and it will be included in our upcoming weekly NuGet release on October 13, 2020 


Regards, 
Akshaya  



AA Akshaya Arivoli Syncfusion Team October 13, 2020 04:18 PM UTC

Hi Arthur , 

We have fixed the reported issue and the fix was included in our latest weekly release v18.3.0.40. Kindly upgrade to that version to get the issue resolved. 
 
Pacakages  
 
Client side package    
   
Blazor Client  
Blazor Sever 
Service side package    
ASP.NET Core :    
     
ASP.NET MVC:    
   
   
Regards,   
Akshaya   



Marked as answer
Loader.
Up arrow icon