lazerbeak12345 / bad-mitten-browser Goto Github PK

May need to wait for #1

may need to wait for #1

May need to wait for #1 and #10

The Standard for WebDriver is maintained by the W3C. Both of the below documents are work-in-progress.

• W3C working draft https://www.w3.org/TR/webdriver2/ (stable)
• W3C Editor's Draft https://w3c.github.io/webdriver/ (unstable)

I'll be writing the code to conform to the latest working draft.

This initial WebDriver support will be considered "good enough for now" once the API can be used to run the WPT.

In particular the following sections will at least need to be done, to support some of these tests.

• §6. Protocol
• §7. Capabilities
• §8. Sessions
• §10. Navigation
• §11. Contexts
• And parts of various other sections.

Many sections will require JavaScript support of some sort. From my current understanding, none of these sections will be needed to run the specific Web Platform tests I would like to run.

It should be noted that WPT provides tests for the webdriver protocol. Live demo here: https://wpt.live/webdriver/

• #27
• New session tests https://wpt.live/webdriver/tests/new_session/

This is an issue to add a named font family on the css font-family attribute.

May need to wait for #1

Add a command-line flag to run the browser in "webdriver mode" where, as per standard, a new window will be opened on a new session, as soon as the first address to open is known.

• Overhaul main.rkt to have actual command-line parsing.

Because of racket/typed-racket#1111 once that code is released (and related code) this should now be possible.

• Close buttons
• Reorder tabs

may need to wait for #1

May need to wait for #1

This may need to wait until I finish #1

may need to wait for #1

Test any http(s) url in the browser, and you will get this error: racket/typed-racket#1285

may need to wait for #1

This includes:

• normal
• bold
• lighter
• bolder
• numbers 100 - 900 (400 is normal 700 is bold)
• and the global inherit initial and unset

May need to wait for #1

It's a bit easier to reason about.

What I'm imagining is this for the order of where things are checked:

• Someplace in /tmp (as mentioned in this comment it might be /tmp/bm-browser)
• Some sort of IPFS cashe using ipfs streaming magics
• Actually contacting the webserver.

The last two steps can be checked paralell.

may need to wait for #1

may need to wait for #1

I'm not sure how to go about this. I might be wrong but it seems the only way to do this is by using mixins provided by framework. This is only a problem because typed/racket doesn't yet support macros even though racket does.

This includes the following values:

• normal
• italic
• oblique
• initial
• inherit

Here's the FSF's page on this

It boils down to this:

• Get a copyright disclaimer from your employer or school.
• Give each file the proper copyright notices. Make sure to clearly identify which versions of the license users can use.
• Add a COPYING file with a copy of the GNU GPL or GNU AGPL.
• Also add a COPYING.LESSER file with a copy of the GNU LGPL, if you use that.
• Put a license notice in each file.
• (Optionally) make the program display a startup notice.
• (If using the AGPL) make the program offer copies of its source code.

The licence notice needs to look like this (copied from the source above):

    This file is part of Foobar.

    Foobar is free software: you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    Foobar is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with Foobar.  If not, see <https://www.gnu.org/licenses/>.

The browser need to be able to run tests from https://github.com/web-platform-tests/wpt

• Run the WPT test suite when running raco test style tests.
  • Must be able to "skip" tests, using rackunit conventions (if any are present)
  • Must be able to use all racket test-tooling to interact with these tests, wherever possible.
• #26

May need to wait for #1