servo/tests/wpt/web-platform-tests/editing
2019-05-15 12:27:06 -04:00
..
data Update web-platform-tests to revision d3cf77a7b8c20c678b725238eaa8a72eca3787ae 2019-04-26 01:35:21 -04:00
include Update web-platform-tests to revision 50d6ee076e94273080d9f3b69be0bf4eeae156d3 2018-08-22 23:24:36 -04:00
manual Update web-platform-tests to revision 60220357131c65146444da1f54624d5b54d0975d 2018-07-18 22:07:44 +00:00
other Update web-platform-tests to revision a46616a5b18e83587ddbbed756c7b96cbb4b015d 2017-10-05 00:42:13 +02:00
run Update web-platform-tests to revision d7afcb8708eac08a614d161d5622a48172daf7e3 2019-05-15 12:27:06 -04:00
event.html Update web-platform-tests to revision dc5cbf088edcdb266541d4e5a76149a2c6e716a0 2016-09-09 16:17:14 +02:00
META.yml Update web-platform-tests to revision 60220357131c65146444da1f54624d5b54d0975d 2018-07-18 22:07:44 +00:00
README Update web-platform-tests to revision dc5cbf088edcdb266541d4e5a76149a2c6e716a0 2016-09-09 16:17:14 +02:00

Most of this directory tests conformance to the editing spec written long ago
by Aryeh Gregor.  Nobody actually implements the spec, but the tests are still
useful for regression testing.  The files in data/ were generated from a
JavaScript implementation of the specification using a complex procedure that
can't actually be replicated right now as-is.  Editing them manually is
possible, but they're not really meant to be human-readable.  If anyone is
interested, it would be possible for Aryeh to get the test generation procedure
working again.  Or you could look into the repository history and figure out
how to do it yourself, if you're brave.

There is also a directory other/ that contains additional editor-related tests.
They aren't necessarily based on any specification, but try to specify sensible
behavior, and are meant to be helpful with regression testing for existing
implementations and finding bugs in new implementations.