- 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.
* upgrade ember-power-calendar for IE11 support
* Ember Bootstrap feature branch fixing IE 11 with unsupported input type
* upstream fix has been merged (but not released)
* fs-extra dependency of in-repo-addon was not listed explicitly
* refactor: inclusion of api in build for readability
* fix: 'readdirSync' is assigned a value but never used
* cherry-pick needed helpers from ember-math-helpers
This reduces the build size by 1.2 KB after gzip.
* dep: remove ember-array-helper
array helper already provided by ember-composable-helpers
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.
All major browsers support standard by now. Only IE11 has limited support
for X-Content-Security-Policy. But that support is limited to sandbox
directive, which isn't used by Croodle.
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.
