- Jul 26, 2018
-
-
Thomas Buckley-Houston authored
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.
- Jul 25, 2018
-
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
I'd added this before, but for some reason it went missing.
- Jul 24, 2018
-
-
Thomas Buckley-Houston authored
Trying to stop Kubernetes' regular health check probes from loading an actual raw text request.
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
My hunch is that, since the switch to using brow.sh as the default homepage, the extra page load time has an undesirable effect on subsequent requests for new tabs. For example, say that a new tab is requested but the original brow.sh tab hasn't completed, but it does complete halfway through another tab loading. Might it retake focus and prevent DOM load events triggering in the user-requested tab? So for now, the quickest fix is just to increase the wait time in the tests. The better fix, if my hunch is right, would be to detect and wait for the original launch-time tab to finish.
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
- Jul 21, 2018
-
-
Thomas Buckley-Houston authored
Such a big commit to provide a fix which really only involves a few lines in the graphics builder. It would seem that the very first time the BlockCharMono font is rendered it needs a little delay. So there's a refactor here to use a callback when requesting a screenshot with text. All the other code in this commit is just the scaffolding to try to fix this issue. It's all good stuff in itself. Basically stricter code triggers for the different stages of page load: tab load, DOM ready, page ready. I actually wonder if the TTY page loads feel snappier now? closes #46
-
Thomas Buckley-Houston authored
Only 'next-tab' is currently supported. You will need to run Browsh with `--debug` then press the key combination and watch the logs for something like; `TTY sending: /stdin,{"char":"\u001c","key":28,"mod":2}` That is the result of having `pressed CTRL+\`. Then add something like the following to your config file: ```toml [tty.keys] next-tab = ["\u001c", "28", "2"] ``` touches #52
-
Thomas Buckley-Houston authored
closes #132
-
Thomas Buckley-Houston authored
-
- Jul 19, 2018
-
-
Thomas Buckley-Houston authored
Version v1.4.6
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
What is that file!!? It's only on Travis and its 201Mb!
-
Thomas Buckley-Houston authored
Includes version bump to v1.4.3
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
Silly mistake. There's a few manipulations of `path` done before calling `os.exec()`, so they need to passed on, not ignored!
- Jul 18, 2018
-
-
msrahman07 authored
"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"
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-
Thomas Buckley-Houston authored
-