Skip to content
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

Change QUnit fixture reset behavior #195

Merged
merged 1 commit into from
Feb 14, 2012
Merged

Conversation

conzett
Copy link
Contributor

@conzett conzett commented Feb 1, 2012

Change for issue #194

Essentially, cache a clean copy of
the fixture node on load and replace subsequent fixture nodes with that.

On load, clone qunit-fixture element and set config.fixture equal to
that. Change the reset function to replace the entire qunit-fixture
element with a deep copy of the clone.

Added tests to check if properties on the fixture are cleared between
tests.

On load, set clone qunit-fixture element and set config.fixture equal to
that. Change the reset function to replace the entire qunit-fixture
element with a deep copy of the clone. Essentially, cache a clean copy of
the fixture node on load and replace subsequent fixture nodes with that.

Added tests to check if properties on the fixture are cleared between
tests.
@jzaefferer jzaefferer merged commit b9010d4 into qunitjs:master Feb 14, 2012
@jzaefferer
Copy link
Member

Thanks, landed.

jzaefferer added a commit that referenced this pull request Feb 29, 2012
…tfix.

This reverts commit b9010d4.

That change turned out to cause very sublte bugs in jQuery UI testsuites, where the browser form memory would cache values between testruns. Which doesn't happen with the previous reset implementation. Unfortunate, but not worth the trouble.
@jzaefferer
Copy link
Member

I had to revert this patch, as it caused very subtle trouble downstream in jQuery UI. The type of failure is bad enough that I don't want anyone else to experience that again, so have to change this (and #194) to "wontfix". I will update the documentation accordingly.

For your particular case, just leave the fixture element as-is and use a wrapper or child.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants