Side navigation
#14818 closed feature (fixed)
Opened February 18, 2014 05:02PM UTC
Closed April 15, 2014 01:50PM UTC
Remove integration tests for Sizzle
| Reported by: | markelog | Owned by: | markelog |
|---|---|---|---|
| Priority: | high | Milestone: | 1.11.1/2.1.1 |
| Component: | misc | Version: | 2.1.0 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
In order for Sizzle tests to work we use some various ugly hacks and undocumented features of QUnit, since soon Sizzle will be tested even in more browsers then jQuery, we could try to live without them.
Attachments (0)
Change History (4)
Changed February 18, 2014 05:06PM UTC by comment:1
| component: | unfiled → misc |
|---|---|
| description: | → In order for Sizzle tests to work we use some various ugly hacks and undocumented features of QUnit, since soon Sizzle will be tested even in more browsers then jQuery, we could try to leave without them. |
| owner: | → markelog |
| priority: | undecided → high |
| status: | new → assigned |
Changed February 18, 2014 05:07PM UTC by comment:2
| description: | In order for Sizzle tests to work we use some various ugly hacks and undocumented features of QUnit, since soon Sizzle will be tested even in more browsers then jQuery, we could try to leave without them. → In order for Sizzle tests to work we use some various ugly hacks and undocumented features of QUnit, since soon Sizzle will be tested even in more browsers then jQuery, we could try to live without them. |
|---|
Changed March 04, 2014 02:33PM UTC by comment:3
| milestone: | None → 1.11.1/2.1.1 |
|---|