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

testharness.js feature tracking #841

Closed
jdm opened this issue Aug 31, 2013 · 4 comments
Closed

testharness.js feature tracking #841

jdm opened this issue Aug 31, 2013 · 4 comments
Labels
A-content/bindings The DOM bindings A-testing B-feature-tracking This issue tracks a particular high-level feature

Comments

@jdm
Copy link
Member

jdm commented Aug 31, 2013

This is a meta issue to keep track of what's required for getting testharness.js to work.

@Ms2ger
Copy link
Contributor

Ms2ger commented Oct 23, 2013

@Ms2ger
Copy link
Contributor

Ms2ger commented Oct 24, 2013

@jdm
Copy link
Member Author

jdm commented Nov 11, 2013

bors-servo pushed a commit that referenced this issue Nov 12, 2013
It's good enough for now, since we don't track document resources at all. Should be good enough for #841.
@jdm
Copy link
Member Author

jdm commented Apr 18, 2014

#2089 landed.

@jdm jdm closed this as completed Apr 18, 2014
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
…horship

Put authorship information into IndexedDB test files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-content/bindings The DOM bindings A-testing B-feature-tracking This issue tracks a particular high-level feature
Projects
None yet
Development

No branches or pull requests

2 participants