Last edit: @kyork in (via web) 8 months ago - Slack Archive

Your task, should you choose to accept it, is to parse a HTML document into a "DOM". The design of your parser MUST support optional scripting, and you will implement a simple scripting language (simpler than JavaScript) to verify that this works.

The specification is available at https://www.w3.org/TR/html5/ and your list of tests is at https://github.com/html5lib/html5lib-tests .

You MUST implement a test runner that can run all of the `tree-construction` tests on your parser and verify that it is correct. You SHOULD understand the use of these terms as per RFC 2119. 

History

Revision: 3582 by @kyork in (via web) 8 months agoSlack Archive

Your task, should you choose to accept it, is to parse a HTML document into a "DOM". The design of your parser MUST support optional scripting, and you will implement a simple scripting language (simpler than JavaScript) to verify that this works.

The specification is available at https://www.w3.org/TR/html5/ and your list of tests is at https://github.com/html5lib/html5lib-tests .

You MUST implement a test runner that can run all of the `tree-construction` tests on your parser and verify that it is correct. You SHOULD understand the use of these terms as per RFC 2119. 

Revision: 3581 by @kyork in (via web) 8 months agoSlack Archive

Your task, should you choose to accept it, is to parse a HTML document into a "DOM". The design of your parser MUST support scripting, and you will implement a simple scripting language (simpler than JavaScript) to verify that this works.

The specification is available at https://www.w3.org/TR/html5/ and your list of tests is at https://github.com/html5lib/html5lib-tests .

You MUST implement a test runner that can run all of the `tree-construction` tests on your parser and verify that it is correct. You SHOULD understand the use of these terms as per RFC 2119. 

Revision: 3580 by @kyork in #marvin-dev 8 months agoSlack Archive

x