servo/tests/wpt/web-platform-tests/editing
2018-01-31 12:24:47 -05:00
..
data Update web-platform-tests to revision 10168e9a5d44efbc6e7d416d1d454eb9c9f1396c 2018-01-31 12:24:47 -05:00
include Update web-platform-tests to revision 58eb04cecbbec2e18531ab440225e38944a9c444 2017-04-22 14:17:10 +02:00
manual Update web-platform-tests to revision 58133dd71b16037669a0aa011b2afd448b52d434. 2015-08-12 08:21:50 +02:00
other Update web-platform-tests to revision a46616a5b18e83587ddbbed756c7b96cbb4b015d 2017-10-05 00:42:13 +02:00
run Update web-platform-tests to revision 8a2ceb5f18911302b7a5c1cd2791f4ab50ad4326 2017-10-12 12:36:21 -04:00
event.html Update web-platform-tests to revision dc5cbf088edcdb266541d4e5a76149a2c6e716a0 2016-09-09 16:17:14 +02:00
OWNERS Update web-platform-tests to revision 95aad3bd9b82b5c65d84d53517b65ba084de9394 2016-02-12 09:41:14 +01: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.