948846: Need Argument to Prevent Default scroll

[KaviBharathi-SF5060]

Feature description

Need Argument to Prevent Default scroll

Requirement and specification document.

Shared the task with the specification document on the feature implemented.

Task: https://dev.azure.com/EssentialStudio/Ej2-Web/_workitems/edit/948846

Output screenshots

Feature matrix document

Feature matrix document updated against this feature and committed in this [common location]

• Yes

• NO

• NA

Provide the details about the areas or combinations which have been tested against this code changes.

• Tested against feature matrix.

Feature acceptance criteria (Test-case document)

Draft the test cases in excel and attach it in the MR itself. The automation must be covered based on this positive and worst-case test-cases.

Automation details

Mark 'Is Automated' field as (Yes, Manual, Not Applicable) in corresponding JIRA task once the feature is automated.

• BUnit, share corresponding MR.

• E2E or Manual Automation using tester - Make sure all items are automated with priority before release which can be tracked in automation dashboard.

Test bed sample location

Provide the test bed sample on the Minimum and Maximum zooming.

https://gitea.syncfusion.com/essential-studio/blazor-sfpdfviewer-playwright-tests/pulls/438

Feature completion checklist

UX changes got approval if UI is added or modified?

• Yes. Provide Task link.

• NO

• NA

Drafted UG for this feature?

• Yes, provide MR link.

• NO, provide task link.

• NA

Content team reviewed the UI content changes.

• Yes. Provide MR or Task link.

• NO

• NA

Is this the common feature which needs to be addressed in the same component or on other components in our platform?

• Yes. If we need to check in other components, tag "needs-attention-coreteam"

• NO

Is there any existing behavior change due to this code change?

• Yes. If So, add breaking-change label.

• NO

Blazor Checklist

Confirm whether the ensured feature is in both Blazor Server and WASM.

• Yes

• NO

• NA

Do the code changes cause any memory leak and performance issue?

• Yes

• [x ] NO

Reviewer Checklist

• Reviewed feature matrix document modifications and reviewed developer testing report against the feature matrix reviewed.

• Testbed sample ensured.

• Coverage report checked.

• Ensured the code changes meet the coding standard.

• Confirming script changes made in this merge request can't be achieved in C#.

Created task in Blazor to synchronize if the feature is not available and applicable.

• NA

• Yes, task link.

• NO, share reason.

[SyncfusionBuild]

Build Status: INPROGRESS 🔃
Build Location: EJ2-948846-asp-dialog

[SyncfusionBuild]

CI Status: FAILURE ❌
Source Compilation: SUCCESS ✅
Failure Reason: CI Failure with violation
Build Location: EJ2-948846-asp-dialog
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 2
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0

[SyncfusionBuild]

Build Status: INPROGRESS 🔃
Build Location: EJ2-948846-asp-dialog

[SyncfusionBuild]

CI Status: SUCCESS ✅
Source Compilation: SUCCESS ✅
Build Location: EJ2-948846-asp-dialog
Technical Error(s): 0
Spelling Error(s): 0
Image Alt Text Error(s): 0
Image Size Error(s): 0
Image Name Error(s): 0
Front matter Error(s): 0
File Path Error(s): 0
CodeSnippet File Path Missing Error(s): 0
Toc Anchor Tags Validation Error(s): 0
MD Tag Validation Error(s): 0