Axel Faust

By using "should" instead of "must" I wanted to soften the IE requirement. All in all, I wanted to express we should require support of one standards-compliant browser (either one...

Thanks for the input/submission Nicolas. I don't know if CmisSync falls in a category of addons we have already considered in our discussions regarding any review / acceptance criteria -...

As already expressed on the Alfresco IRC channel today, there should never have been a config option for this. [Other console tools show](https://github.com/Alfresco/share/blob/master/share/src/main/resources/alfresco/site-webscripts/org/alfresco/components/console/application.get.js#L41) how the license / edition of Alfresco...

Well.... looks like Alfresco 7.0 was released (or at least tagged), and it still contains the same issue, as there has been no change to the [default configuration](https://github.com/Alfresco/share/blob/alfresco-share-parent-7.0.0/share/src/main/resources/alfresco/share-config.xml#L132) which breaks...

The amount of redundant "I have the same error", different "solutions" (some of them dirty hacks), false claims of "does not work" etc. on this issue is honestly astounding. Too...

I have implemented some changes to InfiniteScrollService and AlfSortablePaginatedList to allow programmatically triggering a load for "more data". The [branch](https://github.com/AFaust/Aikau/tree/listPayloadHandlingAndInfiniteScrollingConsolidation) is not yet ready for opening a PR as I...

As a minor aside: I don't know the reason why it doesn't, but the access to the metadata fragment of the payload should also follow the same fallback pattern as...

4 CPUs, 8 GiB memory (you snooze - you loose). 100% CPU reported by "top" means 1 of 4 CPU is occupied. No other processes (i.e. Java / Jetty) seemed...

Nothing has really changed after downgrading Node to v6.0.0, disabling Firefox, reinstalling Grunt AND Selenium. I even explicitly uninstalled the v6.3.1 to make sure it isn't somehow used accidentally. Still...

Nothing is happening (no unit tests, only the 100% CPU use by Node) and after waiting 15-20 minutes, I typically Ctrl+C the Grunt CLI and kill the Node process...