Better UI for Piwik 3, more responsive, faster, lots of other fixes (#10397)

* improved ui and responsiveness

* improve rss widget

* commit changes for ui again, got lost after the last commit

* fix more tests

* restoring files

* fix fonts

* fix more tests

* more test fixes

* fix some system tests

* fix tests

* fix system and ui tests

* fix updater tests

* make a page as loaded once the callback is called

* enable verbose

* more verbose output

* enable phantomjs debug flag

* debug should be a phantomjs option

* trying to fix installation tests

* fixes #10173 to not compile css files as less

* trying to minimize js/css requests to hopefully prevent random ui test fails

* disable verbose mode

* fix updater and installation

* lots of bugfixes and ui tweaks

* fix reset dashboard

* various bugfixes

* fix integration tests

* fix text color

* hoping to fix installation tests this way

* cache css/js resources for an hour, should speed up tests and prevent some random issues

* we need to avoid installing plugins multiple times at the same time when requesting resources

* finally getting the colors right again

* fix most tests, more tests for theme

* use an h2 element for titles for better accessibility

* fix headline color

* use actual theme text color (piwik-black)

* fix small font size was applied on all p elements

* fix tests

* now improving all the datatables

* trying to ignore images for visitor log

* Revert "trying to ignore images for visitor log"

This reverts commit ad1ff7267aae14ad905bef130e956c8593c4fb22.

* fix tests

* fix we had always ignored a max label width

* trying to fix file permissions

* fix more file permissions

* Improved plugins update API (#10028)

* refs #7983 let plugins add or remove fields to websites and better settings api

* * Hide CorePluginsAdmin API methods
* More documentation
* Added some more tests

* improved updates API for plugins

* better error code as duplicate column cannot really happen when not actually renaming a colum

Conflicts:
	core/Updates/3.0.0-b1.php
	plugins/CoreUpdater/Commands/Update/CliUpdateObserver.php

* fix DB field piwik_log_visit.location_provider too small (#10003)

* fixes #9564 fix DB field piwik_log_visit.location_provider too small

* use new plugins updater API

* DB field piwik_log_visit.visit_total_actions too small (#10002)

* fixes #9565 DB field piwik_log_visit.visit_total_actions too small

* change type of some db columns that are too small

* fix tests (#10040)
Conflicts:
	plugins/CoreAdminHome/Menu.php
	plugins/Goals/Menu.php
	plugins/MobileMessaging/Menu.php
	plugins/SitesManager/Menu.php
	plugins/UsersManager/Menu.php
	tests/PHPUnit/System/expected/test_apiGetReportMetadata__API.getWidgetMetadata.xml

* fix more file permissions

* repair more file permissions

* repair more file permissions

* trying to make ui tests work again, the table was missing

* fix some encoding issues

* cross browser fixes and usability improvement

* move back the config icon, need to find a better solution later

* more cross browser fixes

* bugfixes

* fix ui tests

* fix encoding issue

* fix various issues with the ui tests when a test gets aborted

* also skip this visitor log test when aborted

* there were 3 css files that were loaded separately, merge them instead into one css

* forgot to add the actual manifest

* do not add manifest if custom logo is specified

* load font css files first as it was before merging them into big css

* fix link icon was not aligned anymore

* minor fixes

* setting it back to 4px

* in popovers the font variable was always ignored and a different font loaded

* forgot to update screenshots

* fix remaining tests

* this should fix an update error

* added 3 new widgets system check, system summary and plugin updates

* tweak new widgets content

* no page reload when changing date or segment

* in admin home show only enabled widgets

* refs #10295 use getMockBuilder instead of deprecated getMock

* fix some ui tests

* fix various bugs

* fix more tests

* fix ui tests

* add a space between loading image and loading message

* fix docs so they appear on developer.piwik.org

* improved documentation

* introduce new Widget::renderTemplate method for consistency with controllers

* remove no longer needed files

* testing system fonts

* fix strong was not really bold

* more useful system summary

* remove ubuntu font

* fix most tests and removed most em elements

* fix tests

* fix headline was very thin

* update submodule

* update submodules

* update submodule

* fix failing ui tests

* update submodules

1 files changed, 13 insertions, 22 deletions

diff --git a/libs/bower_components/visibilityjs/README.md b/libs/bower_components/visibilityjs/README.md
index 3f072be38f..17ea5a71a0 100644
--- a/libs/bower_components/visibilityjs/README.md
+++ b/libs/bower_components/visibilityjs/README.md
@@ -1,32 +1,32 @@
-# Visibility.js
+# Visibility.js [![Build Status](https://travis-ci.org/ai/visibilityjs.svg)](https://travis-ci.org/ai/visibilityjs)
 
 <img align="right" width="100" src="http://ai.github.io/visibilityjs/logo.svg" title="Visibility.js logo by Eugenia Tuchapets">
 
 Visibility.js is a wrapper for the [Page Visibility API]. It hides vendor prefixes and adds high level functions.
 
-Page Visibility API allows you to determine whether your web page is visible to
-a user, is hidden in background tab or is prerendering. It allows you to use
+Page Visibility API allows you to determine whether your web page is either visible to
+a user or hidden in background tab or prerendering. It allows you to use
 the page visibility state in JavaScript logic and improve browser performance
 by disabling unnecessary timers and AJAX requests, or improve user interface
 experience (for example, by stopping video playback or slideshow when user
 switches to another browser tab).
 
 Moreover, you can detect if the browser is just [prerendering] the page while
-the user has not still opened the link, and don’t count this as a visit in your
+the user has still not opened the link, and don’t count this as a visit in your
 analytics module, or do not run heavy calculations or other actions which will
 disable the prerendering.
 
 Page Visibility API is [natively supported] by all browsers. For old browsers
 you can use `lib/visibility.fallback.js` with focus/blur hack (note that this
-hack have issue, that document become to be hidden, when browser just
-lose focus, but still visible for user).
+hack has an issue: when browser just lose focus but still visible for user, its state will change to [hidden]).
 
-Sponsored by [Evil Martians].
+<a href="https://evilmartians.com/?utm_source=visibilityjs">
+<img src="https://evilmartians.com/badges/sponsored-by-evil-martians.svg" alt="Sponsored by Evil Martians" width="236" height="54">
+</a>
 
 [Page Visibility API]: http://www.w3.org/TR/page-visibility/
 [prerendering]:        http://code.google.com/chrome/whitepapers/prerender.html
 [natively supported]:  http://caniuse.com/pagevisibility
-[Evil Martians]:       http://evilmartians.com/
 
 ## Translations
 
@@ -40,7 +40,7 @@ Currently the Page Visibility API supports three visibility states:
 * `visible`: user has opened the page and works within it.
 * `hidden`: user has switched to another tab or minimized browser window.
 * `prerender`: browser is just prerendering a page which may possibly be opened
-   by the user to make the apparent loading time lesser.
+   by the user to make the apparent loading time smaller.
 
 ## Timers
 
@@ -69,7 +69,7 @@ Visibility.every(minute, 5 * minute, function () {
 ```
 
 `Visibility.every` returns a timer identifier, much like the `setInterval`
-function. It cannot be passed to `clearInterval`, through, and you should use
+function. However, it cannot be passed to `clearInterval`, and you should use
 `Visibility.stop(id)` to stop the timer.
 
 ```js
@@ -88,7 +88,7 @@ both the hidden and visible pages.
 
 ## Initializers
 
-In another common use case you need to execute some actions upon a switch to
+Another common use case is when you need to execute some actions upon a switch to
 particular visibility state.
 
 ### Waiting until the page becomes visible
@@ -98,7 +98,7 @@ visible now, it will run `callback`, otherwise it will wait until state changes
 to `visible`, and then run `callback`.
 
 For example, let’s show an animated notification only when the page is visible,
-so if an user opens a page in the background, the animation will delay until
+so if some user opens a page in the background, the animation will delay until
 the page becomes visible, i.e. until the user has switched
 to a tab with the page:
 
@@ -116,7 +116,7 @@ will run the `callback` immediately.
 A web developer can hint a browser (using Prerendering API) that an user
 is likely to click on some link (i.e. on a “Next” link in a multi-page article),
 and the browser then may prefetch and prerender the page, so that the user will
-not wait after actually going via the like.
+not wait after actually going via the link.
 
 But you may not want to count the browser prerendering a page as a visitor in
 your analytics system. Moreover, the browser will disable prerendering if you
@@ -280,15 +280,6 @@ For Ruby on Rails you can use gem for Assets Pipeline.
    #= require visibility.core
    ```
 
-### CDN
-
-If you don’t use any assets packaging manager use [cdnjs](http://cdnjs.com/).
-Add to your site:
-
-```html
-<script src="//cdnjs.cloudflare.com/ajax/libs/visibility.js/1.2.0/visibility.min.js"></script>
-```
-
 ### Other
 
 If you need just a files, you can take already minified packages from