Bump i18n-js to latest prerelease

User Story # 15318

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Correct configuration for i18n-js w/asset pipeline

`I18n::JS::Middleware` is only necessary if we're not using the Rails
asset pipeline.

See https://github.com/fnando/i18n-js#rails-app-with-asset-pipeline

If we migrate away from the asset pipeline, this commit should be
reverted.

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Remove erroneously committed translations file

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Remove redundant I18nJsHelper

Signed-off-by: Alex Coles <alex@alexbcoles.com>
remove no longer required experimental controller
Fix wrong styling in context menus

- fixed the wrong styling in context menus
Teach HALAPIResource to handle relative root path

Hyperagent Ajax queries will use jQuery's Ajax implementation rather
than Angular's $http (which automatically prepends the relative root
path, see f148c824).

Bug # 15314

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Test HALAPIResource relative root path handling

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Fix missing DetailsTabOverviewController dependency

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Unify work package context menu markup

- Set correct class for the icons

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Fix icon position on mypage

- fixed icon position on mypage
Fix workPackageContextMenu tests broken in 4825c0a3

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Merge pull request #1913 from opf/fix/15314-fix-hyperagent-relative-url-root

15314 Teach HALAPIResource (Hyperagent) to handle relative root path
enforces authorization for experimental api
removes no longer needed query menu items controller

This is now all handled via API.
remove unnecessary permissions
specs for json instead xml
Bump livingstyleguide to 1.2.0 release

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Allow horizontal scrolling in absolute layout mode

This is a quick fix to make elements that are currently unreachable,
reachable. The problem exists thanks to the `min-width: 1100px` set
on the <html>-element. A better solution would be to remove this
property and take care to make individual page components (especially
navigation) work responsively.

See 00506ca9.

Signed-off-by: Alex Coles <alex@alexbcoles.com>
Use flex-basis to set wp attributes base width

Signed-off-by: Alex Coles <alex@alexbcoles.com>