Tasks

• [x] #401

• [x] #452

• [x] #508

• [x] #514

• [x] #521

• [x] #522

• [x] #526

• [x] #463

• URL & URLSearchParams we try to use node:url module solve problems about URL and URLSearchParams now.

• Document.URL & Document.documentURI I have implemented it in https://github.com/capricorn86/happy-dom/pull/520/commits/a71819f7bd813a3e0bc528f9fa8995a0896f52d7

• XMLHttpRequest finished.

References: https://github.com/souldreamer/xhr2-cookies https://xhr.spec.whatwg.org/#xmlhttprequesteventtarget https://developer.mozilla.org/en-US/docs/Web/API/Document/URL https://dom.spec.whatwg.org/#dom-document-url https://github.com/jsdom/jsdom

I am testing de-serializing an XML string into an object using jest and happy-dom

When I run the test I get:

ReferenceError: DOMParser is not defined

Code is below: switch(contentType) { case 'application/json': return JSON.parse(content); case 'application/xml': return (new DOMParser()).parseFromString(content, "text/xml"); | ^ default: return content;

Thanks :-)

The URL constructor at https://github.com/capricorn86/happy-dom/blob/57a8d33d4b1ba3bdd4df0f7f8bc02e0d06bd8e9e/packages/happy-dom/src/location/URL.ts#L23 does not support the second form of the URL constructor which takes a base url:

new URL(url)
new URL(url, base)

Quick test:

# expected
> new URL('', 'https://example.com').pathname
'/'
# actual
> new URL('', 'https://example.com').pathname
''

const element = document.createElement('div');
document.appendChild(element);
expect(element.matches('.nonexistent-class div')).toBe(false);

TypeError: Cannot read properties of undefined (reading 'split')

  296 |     ): { priorityWeight: number; matches: boolean } {
  297 |             const regexp = new RegExp(CLASS_REGEXP, 'g');
> 298 |             const classList = element.className.split(' ');
	  |                                                 ^
  299 |             const classSelector = selector.split(':')[0];
  300 |             let priorityWeight = 0;
  301 |             let match: RegExpMatchArray;

  at SelectorItem.matchesClass (src/query-selector/SelectorItem.ts:298:39)
  at SelectorItem.match (src/query-selector/SelectorItem.ts:91:24)
  at Function.matchesSelector (src/query-selector/QuerySelector.ts:107:27)
  at Function.matchesSelector (src/query-selector/QuerySelector.ts:113:15)
  at Function.matchesSelector (src/query-selector/QuerySelector.ts:113:15)
  at Function.matchesSelector (src/query-selector/QuerySelector.ts:113:15)
  at Function.match (src/query-selector/QuerySelector.ts:66:24)
  at HTMLElement.matches (src/nodes/element/Element.ts:734:24)

Resolves https://github.com/capricorn86/happy-dom/issues/484 Resolves https://github.com/capricorn86/happy-dom/issues/475

It's a very basic implementation mostly covering the API (at least what is common between audio and video and widely supported in browsers) timeRanges implementation coming from jsdom as the comment mentioned. I try to implement some basic logic but mostly is missing, I hope this can be good enough as a first step.

References: https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement https://html.spec.whatwg.org/#htmlmediaelement https://github.com/jsdom/jsdom

p.s.: should I need to add HTMLAudioElement and HTMLVideoELement to window.ts and index.ts or the changes is the packages/happy-dom/src/config/ElementTag.ts in enough for use?

Hi!

I decided to try happy-dom instead of jsdom for my Jest tests due to the advertised speedup. My code adds a function to Array.prototype:

Array.prototype.groupBy = () => ...

With jsdom, this works. With happy-dom, it doesn't. If I put a breakpoint right after the function has been added, I can see that the function is present ([].groupBy is a function) with jsdom but is undefined with happy-dom.

Do I have to configure happy-dom to allow adding to the prototype of native objects?

Hi there 👋🏻 ,

I hope it is the right place to ask, and I apologize if not. I'm currently trying to bump version of happy-dom from 2.51.0 to a greater one using vitest & vue 3 but I'm facing the following error:

happy-dom version: 3.1.0 (I've tried multiple version between this one and 2.51.0)
vitest version: 0.10.0

It seems to be related to usage of @headlessui/vue (version 1.5.0) but I haven't found yet the root cause.

Thanks in advance for your help, wish you a nice day ☀️

I was trying to replace JSDOM with Happy DOM and the app was failing to run something akin to:

const element = document.createElement('div');
const someAttribute = document.createAttribute('someattribute');
element.attributes.setNamedItem(someAttribute);

I see the current implementation is:

readonly attributes: { [k: string]: Attr | number };

Is there any chance there will be a switch to NamedNodeMapin the future?

Hi, looking to replace jsdom so I'm looking to add either just the insertAdjecentText method or the entire insert-adjecent suite of methods, depending on projects philosophy.

Looking at the code structure I wasn't quite sure how to split the methods. Guidance would be appreciated so I can put together a PR.

Thanks.

Kind of a question for help, I'm trying to use happy-dom instead of jsdom using vitest, it should be as simple as changing the vitest environment setting. However, when I switch over, it comes with many issues. Such line as,

    await $radios[0].trigger('click')
    expect(wrapper.vm.modelValue).toEqual('one')

Which worked fine before, doesn't seem to do anything.

I also get weird fails saying value.trim is not a function on vue-test-utils...

const wrapper = mount(FormSelectOptionGroup, {` 

Component mounting function.

Also, on some other mounting functions, some will fill with TypeError: Cannot set properties of undefined (setting 'hasOwnProperty'), while others in the same file seemingly have no issues.

Any help would be appreciated. Here's the repo, if anyone wants to take a deeper look and help me figure out what I'm doing wrong. https://github.com/cdmoro/bootstrap-vue-3/tree/main/packages/bootstrap-vue-3

I updated from ^2.55.0 to latest and this causes my github pipeline to get stuck after the tests are done. Oddly enough it works on windows. only linux and macos get stuck.

Am I overseeing something in the upgrade notes which can cause this?

I'm using vitest for testing.

link to repo: https://github.com/ueberbit/lib

Bumps json5 from 1.0.1 to 1.0.2.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

I've got the "Unexpected token 'export'" error when loading a vue + vite application. I'm assuming is not parsing the main javascript correctly, is this something that should be supported?

Describe the bug A clear and concise description of what the bug is.

Starting with version 7.8.0, setting the href property like this:

window.location.href = '/foo'

Will throw an exception: ERR_INVALID_URL.

To Reproduce Steps to reproduce the behavior:

1. Create a test with happy-dom
2. In the test, insert window.location.href = '/foo'
3. See error ERR_INVALID_URL

Expected behavior I can set the href property using a string which doest not represent a full url, in the same exact way in which both chrome and firefox works.

Screenshots

Device:

• OS: OS X
• Browser: Vitest
• Version: v0.25.6

Additional context This happens using happy-dom during tests.