Error with FAST button #6785
Labels
FREQUENCY: level 1
SYSTEM: hammerhead
TYPE: bug
The described behavior is considered as wrong (bug).
Milestone
What is your Scenario?
There is an error with TestCafe when a site contains a
fast-button
element from Microsoft's FAST components.When I run tests with TestCafe, I get the following error:
I see the same error using the Hammerhead playground from master here.
What is the Current behavior?
An exception occurs when a page containing a
fast-button
is run using TestCafe. The error does not occur normally on the page.From my debugging, it seems the error occurs here in the compilation of the
fast-button
. It appears thatattributes
does not get updated to reflect that an attribute was removed during the call toremoveAttributeNode
, so in the next iteration of the for-loop, the same attribute is attempted to be removed again, causing the exception.Note: I did not try every FAST component, so the issue may occur with more than just the button.
What is the Expected behavior?
The page should load successfully.
What is your public website URL? (or attach your complete example)
Public website: https://explore.fast.design/components/fast-button
I've also attached a simple Angular app containing only a fast-button.
TestCafeError.zip
What is your TestCafe test code?
Not relevant. I reproduced this directly using the Hammerhead playground.
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
To reproduce using public site:
https://explore.fast.design/components/fast-button
in the text box and click "Proxy"To reproduce using the attached app:
npm install
npm run start
and see a page with a button open to localhost:4200http://localhost:4200
in the text box and click "Proxy"TestCafe version
testcafe-hammerhead version 24.5.9
Node.js version
16.13.0
Command-line arguments
N/A
Browser name(s) and version(s)
Chrome: Version 96.0.4664.45 (Official Build) (64-bit)
Platform(s) and version(s)
Windows
Other
No response
The text was updated successfully, but these errors were encountered: