* get deprecation workflow up to date
* fix routing.transition-methods deprecation
* fix this-property-fallback deprecation
* fix implicit-injections deprecation
* argument-less-helper-paren-less-invocation
* remove unmaintained ember-transition-helper which triggers deprecated-run-loop-and-computed-dot-access deprecation
* reset to only log but not throw on errors to not block other development
* reset double quote to single quote changes in templates and fix Prettier config
* fix JS linting
* ugprade ember-template-lint to fix parser
* replace ember-cp-validations with custom validation logic for poll creation
* refactor poll participation to not use ember-cp-validations
* drop ember-cp-validations from create.settings route
* remove unused leftovers from ember-cp-validations
* fix potential leak
* assertion thrown in CI tests (Firefox) indicate that listener is cleaned up automatically
* synchronize translations
Safari does not follow ES5 / ECMAScript 2015 date parsing rules. Per spec a date that has day + time but does not have an explicit time zone (e.g. "2019-01-01T00:00") should be parsed in local time. But Safari treats that one as UTC.
* mark string as html safe before passing to translation instead of bypassing HTML escape using {{{unsafe}}} syntax
* replace ember-i18n with ember-intl
Adds a <SaveButton> component that renders a save button similar to
<NextButton> but using a special icon that helps to distinguish both.
Also removes the block mode for <NextButton> component and some arguments
that aren't needed anymore.
Closes#294
Croodle shows a modal if saving a participation fails. The modal allows
a user to retry the save attempt. While it was always possible to close
the button by clicking on backdrop or using escape key, a button to do so
was missing. A user may not know about the user ways and may see reloading
the page as only possibilty to close the modal if he doesn't want to retry
again.
This adds the missing abort button and fixes some smaller bugs including:
- The modal was missing a title.
- If the modal was closed once it wasn't reopened on another failed saving
attemp unless the user has visit another page in between.
- Several arguments were passed to <BsModal> that weren't existing at all.
* upgrade Ember CLI to 3.13 and Ember Source + Ember Data to 3.12
Ember Source upgrade to 3.13 is blocked by Ember CP Validations,
which does not support Ember Source 3.13 yet.
Ember Data upgrade to 3.13 is blocked by Ember Data Model Fragments,
which does not support Ember Data 3.13 yet.
Also removes autofocus mixin and inlines the code as mixins are
considered an antipattern in latest Ember versions.
Removes some left overs in `"resolutions"` key. But that shouldn't have a real impact.
* Adds a loading spinner to form buttons as long as submission is pending.
* Does some refactoring of form navigation buttons.
* Updates expected bundle size.
- Drops floatthead and additional scrollbar
- Makes header and first column sticky
- Refactors code for readability
Sticky header is only working in Firefox. Chrome and Edge does not support `position: sticky` for `<thead>`. Haven't tested Safari.
Use test helpers provided by ember-cli-clipboard as they do not trigger confirmation in IE 11. Upgrades ember-cli-clipboard to latest version as the outdated version used before does not include these test helpers yet.
Also refactors test execution against BrowserStack to only run tests one by one. Not quite sure why but that fixes the IE 11 issue. Need to investigate later as that one slows down tests by requiring two additional builds.
This one requires a migration from deprecated ember-cli-qunit to ember-qunit.
ember-qunit throws in Unit tests cause they interact with runloop but didn't
awaited everything to finish. An assertion was thrown therefor:
> Assertion Failed: expected container not to be destroyed
Having both a Content-Security-Policy (CSP) in meta tag and per header
works fine together. They are merged and the strongest one is applied.
It makes Croodle safer for all users even if the hoster does not apply CSP
for some reason (e.g. they can't set custom headers).
It's still a good idea to recommend using a CSP header cause that ones
are applied earlier - even so this shouldn't be a problem cause we ensure
that CSP meta tag is present before any other link, style or script element.
This also fix a bug if user creates more than one croodle without reloading window
in between. In that case a data fragment is reused which throws.
It's also the first step in dropping {{simple-select}} which is very outdated.
Ember Bootstrap has changed a lot since the very outdated pre 1.0 release
which was used here. Changes are mostly about using composable components
and closure actions.
Also replaces PhantomJS with Chrome in CI cause PhantomJS is also very
outdated and causing test failure not related to any real world issues.
Ember CLI has replaced PhantomJS with Chrome in v2.15.1, which is the
upfollowing minor release to the version currently used.
