Skip to content

docs(common):Add another reason for js error #2451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 23, 2024
Merged

docs(common):Add another reason for js error #2451

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa96a10
docs(common):Add another framework reason for js error
NansiYancheva Oct 18, 2024
0aed742
update after review
NansiYancheva Oct 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions troubleshooting/js-errors.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,19 @@ You can check if this is the case by inspecting the Network tab of your browser

* A problem occurs during the deployment. See the [Deployment Troubleshooting]({%slug deployment-troubleshooting%}) article for more details.

* The application is navigating from an interactive page. If this is the case, register the `telerik-blazor.js` after the `<base href="/" />` in the `<head>` of the web page:

<div class="skip-repl"></div>

````HTML
<head>
...
<base href="/" />
<script src="_content/Telerik.UI.for.Blazor/js/telerik-blazor.js" defer></script>
...
</head>
````

### Defer Attribute

Sometimes, the JS Interop file is referenced correctly and returns successfully, but occasionally you get the error. This indicates a timing issue (for example, low machine performance or slow network) that causes the script to load and be parsed too late, after it is needed.
Expand Down
Loading