Downgrade velocity.js 1.2.3 -> 1.2.2
Velocity.js 1.2.3 has broken passing an offset and a container to a scroll animation. When autoscrolling the sidebar after opening a folder, version 1.2.2 reliably scrolls the folder to the top of the...
View ArticleOn mouseover over a folder open link, remove any highlighting of sidebar links.
This removes a visual bug that could cause both the folder and the sidebar link to look highlighted.
View ArticleRemove autoscrolling of the sidebar when opening a folder.
It's never worked reliably, velocity.js does not react well to scrolling it, probably because it's surrounded by a container.
View ArticleUpdated rack-cache to upstream version 1.6.0
This version includes the new Noop backend, which doesn't persist response bodies. Using this backend means the disk will never fill up with old responses, but of course responses must be checked...
View ArticleWIP: when a feed scheduled update fails, attempt autodiscovery only if it's...
WIP: when a feed scheduled update fails, attempt autodiscovery only if it's been failing for a (configurable) time, instead of immediately. This helps with the case in which autodiscovery is too...
View ArticleIncluded fastclick 1.0.6 library, managed by Bower, along with its initializa...
Angular-touch 1.5 will deprecate and disable by default the removal of the 300ms delay in touchscreens. They recommend using fastclick or Tappy instead. This commit prepares for when angular 1.5 is...
View ArticleUpdated angularjs, angular-sanitize and angular-touch 1.4.8 -> 1.5.0
Important: angular-touch 1.5.0 deprecates and disables by default their ng-click version. This means that other means of removing the 300ms delay in touch events should be added (already taken care of...
View ArticleUpdated rack-cache gem 1.6.0 -> 1.6.1
1.6.0 was yanked because it introduced a bug for some users when using the Disk backend. It does not affect Feedbunch but better use a released version.
View ArticleWIP: perform some tasks (communicating with the server, mainly) in web workers.
This should leave the main thread with less work to do, which should result in a smoother UI.
View ArticleChanging the state (read/unread) of a single entry is performed in a web worker.
This means the main thread is not used for this ajax call, which makes the UI a bit more responsive, specially in multicore devices. This change does not improve performace a lot, because this ajax...
View ArticleMake the color of an entry while it's changing read/unread state...
Make the color of an entry while it's changing read/unread state undistinguishable from the read/unread color.
View Article