8000 selector not work when use uppercase node name · Issue #3612 · jsdom/jsdom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

selector not work when use uppercase node name #3612

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

Jump to bottom
Closed
flybywind opened this issue Oct 24, 2023 · 3 comments · Fixed by #3854
Closed

selector not work when use uppercase node name #3612

flybywind opened this issue Oct 24, 2023 · 3 comments · Fixed by #3854
Labels
has to-upstream test This bug has a failing to-upstream web platform test waiting to be fixed selectors CSS Selectors support

Comments

@flybywind
Copy link

Basic info:

  • Node.js version: v20.6.1
  • jsdom version: 22.1.0

Minimal reproduction case

test("check jsdom uppercase nodeName", () => {
  const mockDocument = new JSDOM(`
  <!DOCTYPE html>
  <html lang="en">
  <body>
    <h1>test mask solution</h1>
    <div class='box'>
      <div>
        <p id="p1"></p>
        <p id="p2"></p>
      </div>
    </div>
  </body>
  </html> `);
  const { document } = mockDocument.window;

  const result = document.querySelector("div.box");
  expect(result).not.null;
  const result1 = document.querySelector("DIV.box");
  expect(result1).to.null;
});

if I use div.box then the result was expected, but DIV.box yield a null

How does similar code behave in browsers?

works in both case

(Link to a jsbin or similar strongly suggested.)
@sqs
Copy link
sqs commented Oct 25, 2023

I am seeing this as well. It causes https://github.com/gmmorris/simmerjs to fail when using the latest version of jsdom. (Just posting that in case anyone searches and ends up here.)

@DiogoDoreto
Copy link

I found out that the issue comes from nwsapi dependency. On my tests, v2.2.3 introduced the bug.

@dormesica
Copy link

I also experience this. It used to work on v21.1.0.

domenic added a commit that referenced this issue Mar 30, 2025
@domenic
Add failing selectors test for case-insensitive tag names
8ec0fe3 
See #3612.
domenic added a commit that referenced this issue Mar 30, 2025
@domenic
Add failing selectors test for case-insensitive tag names
4036424 
See #3612.
@domenic domenic added the has to-upstream test This bug has a failing to-upstream web platform test waiting to be fixed label Mar 30, 2025
domenic added a commit that referenced this issue Mar 30, 2025
@domenic
Add failing selectors test for case-insensitive tag names
3c6005b 
See #3612.
@asamuzaK asamuzaK mentioned this issue Apr 15, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
has to-upstream test This bug has a failing to-upstream web platform test waiting to be fixed selectors CSS Selectors support
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add dom-selector CSS engine once again asamuzaK/jsdom
5 participants
@sqs @DiogoDoreto @domenic @flybywind @dormesica
0