-
Notifications
You must be signed in to change notification settings - Fork 48
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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.
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
TypeError: Cannot read properties of null (reading 'cssRules') #1194
Comments
@itsjwala this fixed the cssRules error but i still cant use the latest version it gives some unknown errors now not showing up in the log https://github.com/infor-design/enterprise-wc/actions/runs/4365577412/jobs/7637547882#step:10:29623 Just mentioning it in case you have an idea. If not i can try to get verbose logs turned on (is that possible I forget) when i have more time and make a new issue. |
@tmcconechy I see the visual changes are happening due to javascript being enabled. Is there any reason for enabling it? (If its Shadow DOM, then we support it since 1.19.2+) We noticed that the visual errors are a result of javascript side effects. Can you try disabling it and running the builds? |
@samarsault i disabled it on https://github.com/infor-design/enterprise-wc/pull/1165 but it a) still has a lot of errors b) the images dont look correct anymore. We do use shadowRoot (web components). But not sure i recall why we enabled it. I think support suggested it. Still this only is a problem moving up from 1.18.0 https://github.com/infor-design/enterprise-wc/actions/runs/4375912710 |
@tmcconechy we see some unusual diffs in your build and will take a look. Can you try using the latest version setting |
@samarsault still doing some weird things https://github.com/infor-design/enterprise-wc/actions/runs/4397781859/jobs/7716169624 https://github.com/infor-design/enterprise-wc/pull/1165 I would think we want JS and shadowRoot since these are JS components and they use web components/shadowRoot |
@samarsault should i be using the support at browser stack instead? My concern is we can no longer update and use percy so might need to look at other options before renewing. |
@tmcconechy For the enableJavascript: false case, I see the following classes of visual changes in your build
Also, is the cypress test failure happening because of percy? If yes, what is the error message? Edit: |
ok thanks @samarsault cant seem to get it to work with any configuration i can come up with. We use JS and and its all web components so Js off is not an option (will show nothing). Shadow root is also needed, without it will show nothing on the page. This is the last build https://github.com/infor-design/enterprise-wc/pull/1165 every time it just comes up with errors on each test i cant figure out. So will log a support ticket for now. Cheers |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
The problem
Upgraded from 1.18.0 to 1.20.1 and now get this error on most tests:
Environment
@percy/cli
version: 1.20.1Details
Example test https://github.com/infor-design/enterprise-wc/blob/main/test/ids-data-grid/ids-data-grid-percy-test.ts
Debug logs
https://github.com/infor-design/enterprise-wc/actions/runs/4315837554/jobs/7530775761#step:10:267
Code to reproduce issue
If needed:
"@percy/cli": "1.18.0",
to"@percy/cli": "1.20.1",
in package.jsonnpm i && npm run test
The text was updated successfully, but these errors were encountered: