Age | Commit message (Collapse) | Author | Files | Lines |
|
The default value has been changed to `from-image` and at least with
Firefox 76 and Chromium 83 this leads to double rotated images.
Disabling the automatic rotation with `image-orientation: none` in CSS
leads to incorrectly scaled images, (likely, but unverified) because the
width/height are returned incorrectly/rotated in jquery/javascript.
Whatever it may be, the easier fix is to just check for the new default
value and if the browser handles orientation automatically, we disable
our own code.
https://github.com/w3c/csswg-drafts/issues/3799
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This fixes some weird small-width popovers on the thumbnail history
when a thumbnail is being moved around.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Also drop in all the non minified version because we can and it might
be useful for debugging in the future.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Apparently firefox doesn't like html code in <pre> and adds incorrect
linebreaks when copying the code. This does not happen with chromium.
Fix it by switching to <code> instead of <pre>. Also change the CSS to
refer to the element by class instead of by type so future changes are
simpler.
Not sure why, but in chroium changing the container element type breaks
the ordering of the lines. Adding display: table to the .code-container
fixes this.
References:
http://stackoverflow.com/questions/24851173/why-does-text-copied-from-a-set-of-pre-tags-have-double-line-breaks#comment41552816_26408656
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This bypasses require.js for asciinema because apparently require.js
can't deal with the embedded React library. The result is that React is
not loaded properly and the asciinema player is unable to find it.
Just load it like upstream tells you to.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Also make the navigation fixed because otherwise this looks hideous and
the space is already occupied anyway.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This reverts commit f0d3b633f04c9afa2237b1dad83ad8240da68b38.
That commit causes breakage on the history page due to missing padding.
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
If the thumbnail placeholders are properly positioned via css we can
display them early.
We can also take some work off lazyload by setting a placeholder color
in css thus making rendering for lots of thumbnails faster.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
- Make buttons fixed so you don't have to move the mouse
- Support h/l for vimperator users
- Document mappings so users actually know about them
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
- Incorrect path to .js file
- Autoloading and the data-api don't work so load and run it explicitly
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Support range selection on history page
by adding jquery.checkboxes
|
|
./data/local is not moved because it contains likely untracked files
and moving it would throw an error when updating.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|