Skip to content
Merged
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion packages/docs/src/pages/docs/advanced/qwikloader.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -40,5 +40,5 @@ Below you can find a simple HTML with Qwikloader and a button with associated be
1. The browser downloads the HTML and executes the inlined Qwikloader script. The Qwikloader sets up global listeners for all browser events.
2. The user clicks on the `<button>`. The browser generates a `click` event that bubbles up the DOM until the Qwikloader's global listener intercepts it.
3. The Qwikloader retraces the event path and searches for `onClickQrl` attribute on the elements.
4. The Qwikloader uses the `onClickQrl` and `q:base` attributes along with the `document.baseURI` to build a full URL for fetching the laze-loaded handler. Assuming the original page was served up from `http://localhost/` the fetch URL becomes `http://localhost/build/myHandler.js`.
4. The Qwikloader uses the `onClickQrl` and `q:base` attributes along with the `document.baseURI` to build a full URL for fetching the lazy-loaded handler. Assuming the original page was served up from `http://localhost/` the fetch URL becomes `http://localhost/build/myHandler.js`.
5. Qwikloader retrieves the `clickHandler` symbol, exported from `http://localhost/build/myHandler.js` and invokes it.