b387f66c69
This means that Browsh can now be entirely run just by running the CLI binary. The client launches Firefox as a subprocess, then connects to it via the Marionette protocol, installs the webextension and finally triggers a new tab with, currently, the Google homepage in it. I was trying to set this up for automated testing as well by installing the built webextension as a temporary addon, because otherwise you need to sign the extension everytime with a unique semantic version. However for some reason I can't quite recreate the environment that MDN's `web-ext` creates. The extension installs fine but fails to load the `content.js` script, I can't find a backtrace or any other details about the failure. So for now, we're just going to have to use `web-ext` as seperate process and have the client connect to that. Which is what one should do during development anyway, so it's not a huge loss.
25 lines
640 B
CSS
25 lines
640 B
CSS
@font-face {
|
|
/* A special font that only has unicode full blocks in it, so we can detect */
|
|
/* font colors and text visibility more easily. */
|
|
font-family: 'BlockCharMono';
|
|
src: url('/assets/BlockCharMono.ttf') format('truetype');
|
|
}
|
|
|
|
html * {
|
|
font-family: 'BlockCharMono' !important;
|
|
font-size: 15px !important;
|
|
line-height: 20px !important;
|
|
letter-spacing: 0px !important;
|
|
font-style: normal !important;
|
|
font-weight: normal !important;
|
|
}
|
|
|
|
/* Simulate emphasis because terminals don't usually support bold, italic, etc */
|
|
b, em, strong {
|
|
filter: brightness(10%);
|
|
}
|
|
|
|
sup, sub {
|
|
vertical-align: baseline !important;
|
|
}
|