You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a mismatch between what I get with HappyDOM, and what I get with LinkedDOM or the actual DOM, so I'm pretty sure there's some bug in HappyDOM somewhere.
To Reproduce
cd into this folder https://github.com/vobyjs/voby/tree/master/demo/ssr_esbuild
npm install
Put this console.log(document.getElementById ( 'app' ).innerHTML)here, to log the HTML generated.
npm dev
Go to http:/localhost:3000/counter
Notice how there's a 0 below the <h1>Counter</h1>, as expected.
Go to http:/localhost:3000/counter and notice how the logged HTML doesn't have a 0 anymore. You'll still see one in the page because the page is re-rendered client-side, to turn that off comment out this line.
Expected behavior
HappyDOM's output should make LinkeDOM's and the browser's.
Additional context
I'm not exactly sure what the issue is, the only thing I can think of is that calling .nodeValue = 0 maybe doesn't work in Happy DOM, if that's not the issue I'm not sure what it is.
The text was updated successfully, but these errors were encountered:
Describe the bug
There's a mismatch between what I get with HappyDOM, and what I get with LinkedDOM or the actual DOM, so I'm pretty sure there's some bug in HappyDOM somewhere.
To Reproduce
cd
into this folderhttps://github.com/vobyjs/voby/tree/master/demo/ssr_esbuild
npm install
console.log(document.getElementById ( 'app' ).innerHTML)
here, to log the HTML generated.npm dev
http:/localhost:3000/counter
<h1>Counter</h1>
, as expected.npm install happy-dom-global
.linkedom-global
forhappy-dom-global
here.http:/localhost:3000/counter
and notice how the logged HTML doesn't have a 0 anymore. You'll still see one in the page because the page is re-rendered client-side, to turn that off comment out this line.Expected behavior
HappyDOM's output should make LinkeDOM's and the browser's.
Additional context
I'm not exactly sure what the issue is, the only thing I can think of is that calling
.nodeValue = 0
maybe doesn't work in Happy DOM, if that's not the issue I'm not sure what it is.The text was updated successfully, but these errors were encountered: