https://github.com/abiyasa/marko-dom-node-bugs
A place to expose Marko bugs related to DOM node 🐞
https://github.com/abiyasa/marko-dom-node-bugs
marko
Last synced: 5 months ago
JSON representation
A place to expose Marko bugs related to DOM node 🐞
- Host: GitHub
- URL: https://github.com/abiyasa/marko-dom-node-bugs
- Owner: abiyasa
- Created: 2018-06-01T11:59:02.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2018-09-03T13:56:33.000Z (almost 8 years ago)
- Last Synced: 2025-06-21T23:08:31.602Z (about 1 year ago)
- Topics: marko
- Language: HTML
- Homepage:
- Size: 105 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Marko Bugs
This repo is a place to reproduce DOM node bugs on [Marko](https://markojs.com/) component.
**NOTE**: All bugs here are already fixed on the latest Marko 4.13.0 🎊🎉 For the details, please see:
- https://github.com/marko-js/marko/issues/1052
- https://github.com/marko-js/marko/issues/1051
## Install
We use Node.js v8.11.1, Marko v4.9.7, and the latest Yarn.
```bash
yarn install
```
## Starting the server
```bash
yarn start
```
Go to `http://localhost:8080/`.
## Bug Demos
### Client-side error on expander button
We got client-side error on expandable/accordion content.
```
Uncaught TypeError: Cannot read property 'parentNode' of null
at init-components-browser.js:259
...
```
To re-produce the bug: Run the server and go to:
- `http://localhost:8080/clickable-expander`.
- or `http://localhost:8080/clickable-expander-no-textual-display`
However, if we remove the client-side behaviour (no `component.js` and click event handlers), the error is gone: `http://localhost:8080/non-clickable-expander`
### Client-side error on dialog component
We got client-side error on clsoign and showing dialog component:
```
Component.js:542 Uncaught TypeError: Cannot read property 'nextSibling' of null
at Component.___forEachNode (Component.js:542)
at Component.___detach (Component.js:533)
...
```
To re-produce the bug: Run the server and go to:
- `http://localhost:8080/bug-dialog-close`.
However, if we simplified the dialog (simple text instead of nested component Textual Display),
the error is gone (`http://localhost:8080/bug-dialog-close-no-textual-display`)