In Firefox 63 an old syntax for Marionette commands was deprecated.
Updating mostly just meant prepending `WebDriver` to existing commands.
This should fix most problems in #232
This means that there's now a canonical script that allows other
distributers to build Browsh. The only caveat being that the web
extension cannot be built (Mozilla only allows one signed `.xpi` per
version), so it is downloaded.
"If all you have is a 3kbps connection tethered" --> "If you only have a 3kbps internet connection"
"But traditional text-based browsers..." --> "However, traditional text-based browsers"
"lack JS support and all other modern HTML5 goodness." --> "lack JS and all other modern HTML5 support."
"few more hours life" --> "few more hours of life"
Changed "Why?" to "Why use Browsh?"
Removed avoidable phrases such as "that" and "and uses that"
Divided a run-on sentence by using a period
Switched "Firefox =>57" to "Firefox 57 (or higher)
Shortened the documentation sentence and link
After moving to Tcell and implementing its screen diff updates, we can
no longer watch STDOUT to get frames during integration tests. Instead
we need to use Tcell's SimulationScreen and which has a GetContents()
method. This is actually also a much more robust way of being able to
see what Browsh actually outputs during testing.
In the endless struggle to squash a Travis-specific bug, we now have
screenshots. Currently the screenshots are of the custom block font
state, so you can't read the text. But I'm planning on changing the
default state of the page to use a normal font - such that the
frame builder needs to toggle the block font on to build a frame. This
will make it more likely that screenshots will contain actual text.
Using mirrors in Dockerfile because default ones were down at
time of writing.
Refactor all build commands into 1 RUN command to try and reduce
the number of cached build layers and thus reduce the size of
the finished image.
