| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Fixes #10590
(cherry picked from commit 9493839f23b6ff71aacb9cb8fe8fde6c8d0ecd61)
|
|
|
|
| |
(cherry picked from commit 337e4110b0cb60c73bb27be2e2b855a75a0c4b2e)
|
|
|
|
|
|
| |
Fixes #10748
Closes gh-1417
(cherry picked from commit faefab842bc79f212ccee227b7a37c7630b1573c)
|
|
|
|
|
| |
Closes gh-1403
(cherry picked from commit c89cb74893c4f99d6163e29110c36d9e02dc7df1)
|
| |
|
|
|
|
| |
Fixes #10437
|
|
|
|
| |
Refs #10140
Closes gh-1303
|
|
|
|
|
|
|
| |
Remove an incorrect fix introduced in 47cd5b6f that causes
width calculations to be incorrect once the correct fix
was introduced in c03cb807
Fixes #10140
|
|
|
|
|
| |
Fixes #10351
Closes gh-1292
|
|
|
|
|
| |
Fixes #10148
Closes gh-1279
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a compound test page for draggable+resizable, which had no coverage
before. Using that page shows that there is no way to reproduce the behaviour
described in the original ticket that caused this workaround, since its not
possible to resize an element beyond the window boundaries. Therefore removing
the workaround, which is 6+ years old and has no test coverage, seems like the
sanest approach.
Fixes #6939
Closes gh-1210
|
| |
|
|
- By executing https://gist.github.com/jzaefferer/893fcf70b7eebc1dc271;
Fixes #9464
Closes gh-1029
|