Age | Commit message (Collapse) | Author |
|
Using the same testing files as the previous patch,
the results are:
.---------------------------------------------.
|imgbufs | No patch | Patch #1 | Patch #2 |
|----------------------------------------------
|1imgA.html | 2/1 | 1/1 | 1/0 |
|2imgSA.html | 3/2 | 1/2 | 1/0 |
|3imgSA.html | 4/3 | 1/3 | 1/0 |
|----------------------------------------------
|2imgA.html | 4/2 | 2/2 | 2/0 |
|3imgA.html | 6/3 | 3/3 | 3/0 |
'---------------------------------------------'
n1/n2 means:
n1 imgbufs were created for first load (empty cache)
n2 imgbufs were created for reload (cached image)
Notes:
* Rendering is much faster. Easy to notice with Back operation.
* Between four to five times on www.welt.de.
* Corner cases can be more than ten times. Usually, it *feels* faster.
|
|
This is the first of a patch series for image code bugs that have
severe impact on performance.
With these testing files:
1imgA.html = <img src="maj00s.png" alt="img1">
2imgSA.html = <img src="maj00s.png" alt="img1">
<img src="maj00s.png" alt="img12">
3imgSA.html = <img src="maj00s.png" alt="img1">
<img src="maj00s.png" alt="img12">
<img src="maj00s.png" alt="img123">
2imgA.html = <img src="maj00s.png" alt="img1">
<img src="maj21s.png" alt="img12">
3imgA.html = <img src="maj00s.png" alt="img1">
<img src="maj21s.png" alt="img12">
<img src="c10s.png" alt="img123">
This are the results:
.------------------------------------------------------------------.
|imgbufs | No patch | Patched #1 |
| | first time | upon reload | first time | upon reload |
|-------------------------------------------------------------------
|1imgA.html | 2 | 1 | 1 | 1 |
|2imgSA.html | 3 | 2 | 1 | 2 |
|3imgSA.html | 4 | 3 | 1 | 3 |
|-------------------------------------------------------------------
|2imgA.html | 4 | 2 | 2 | 2 |
|3imgA.html | 6 | 3 | 3 | 3 |
'------------------------------------------------------------------'
|
|
show all at once
|
|
|
|
Not 'necessary' at present, but valgrind complains and it's always good
practice.
|
|
|
|
http://lists.dillo.org/pipermail/dillo-dev/2014-November/010303.html
for: "If an input has focus and you click on the page to give it focus instead,
and then the cursor leaves the page and returns to it, the input is given
focus instead."
|
|
thread http://lists.dillo.org/pipermail/dillo-dev/2014-September/010231.html
|
|
http://lists.dillo.org/pipermail/dillo-dev/2014-November/010299.html
and, from commit text for changeset eb902ac9fc66
"Starting with fltk-1.3.3, we can't use fl_oldfocus, this patch
fixes this problem.
IOW. this patch is necessary to link with fltk-1.3.3."
|
|
|
|
|
|
clang complains about this
|
|
|
|
to a quick glance, that looked like division could be involved.
|
|
|
|
|
|
|
|
|
|
|
|
An infinite loop situation (corner case race condition)
and also avoid rescaling already scaled rows (speed).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For cases like
<div style="line-height:1.7">
dillo dillo dillo dillo dillo dillo
dillo dillo dillo dillo dillo dillo
dillo dillo dillo dillo dillo dillo
dillo dillo dillo dillo dillo <sup>dillo</sup>
dillo dillo dillo dillo dillo dillo
dillo dillo dillo dillo dillo dillo
dillo dillo dillo dillo dillo <sub>dillo</sub>
dillo dillo dillo dillo dillo dillo
dillo dillo dillo dillo dillo dillo
</div>
this gives equally spaced lines and also seems to
replicate firefox behaviour.
|
|
at once.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|