Age | Commit message (Collapse) | Author | Files | Lines |
|
This speeds up the initial rendering of the page. For a long history
(> ~1000 items) the lazyloading JS creates a noticeable delay (>500ms)
depending on the cpu power of the machine.
Disable lazy loading for the first items so that these are loaded
normally by the browser parallel to the scripts execution.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Don't force users to name all their files asciinema.json. Give them
some room for descriptive names.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Email verification is pretty basic since we use the framework function
right now. This might change in the future.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Change the username to fit within the username restrictions.
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>
|
|
Chromium apparently requires a <br> or some text to be present for a
line to be copied to the clipboard.
Firefox interprets the \n at the end as line break and copies that if
there is no content. Adding an explicit <br> makes chromium work
correctly, but firefox still converts the \n. Fix this by putting the
\n in an HTML comment. That way the output is still somewhat readable,
but both browsers do the correct thing.
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 might help users if they run their own installation, but forget to
set the URL in the client config and then run into this error.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
We actually don't need to hide this from the user. The error should be
shown rather than a blank page being returned.
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>
|
|
I think this is left over from developing the feature. This seems to
have been incorrect in the inital commit of the code. Just drop it.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Already in \libraries\Exif
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>
|
|
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>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This is necessary for future use of docker-compose
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>
|
|
Same fix as in 7e4912fc03111ab5071e8e7478db48422597777a.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Proper fix this time. container is not necessary here.
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>
|
|
Keep this field private for now. I may be exposed at a later time.
The returned values are already normalized so they can be safely
exposed.
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
This could lead to XSS if the html attribute values weren't quoted with
double quotes. By default htmlentities only encodes double quotes and
not single quotes. If the quotes are ever changed this could lead to
exploitable XSS.
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>
|
|
The documentation already refers to 2.1.0 and lists a new feature of
the file/history endpoint, but requests for 2.1.0 are not yet accepted
because the server doesn't know that it actually supports this version.
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>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|
|
Signed-off-by: Florian Pritz <bluewind@xinu.at>
|