fix(sort): indicator hint not showing up on mobile

[devversion]

• Due to the fact that the sort module uses the (longpress) event, the custom HammerJS gesture config needs to be provided.

Related to #12940

[jelbourn]

LGTM

[josephperrott]

@devversion Can you rebase when you have a chance?

[devversion]

@josephperrott Done! thanks for the ping.

[mmalerba]

~40 targets failing in google3 with an error like: TypeError: Cannot read property 'type' of undefined

[devversion]

@mmalerba Thanks for trying to sync it. I can't think why this would happen as there is nothing special with providing the gesture config (we do this for other components as well). Can we figure out where this error is thrown?

[mmalerba]

Looks like an issue when compiling the components in some tests. Here's the stack trace (edited to remove any google3-specific details):

TypeError: Cannot read property 'type' of undefined
    at JitCompiler._addAotSummaries compiler/src/jit/compiler.ts?l=95
    at JitCompiler._addAotSummaries compiler/src/jit/compiler.ts?l=91
    at JitCompiler._addAotSummaries compiler/src/jit/compiler.ts?l=91
    at JitCompiler.loadAotSummaries compiler/src/jit/compiler.ts?l=79
    at CompilerImpl.loadAotSummaries platform-browser-dynamic/src/compiler_factory.ts?l=75
    at TestingCompilerImpl.loadAotSummaries platform-browser-dynamic/testing/src/compiler_factory.ts?l=97
    at TestBedViewEngine._createCompilerAndModule core/testing/src/test_bed.ts?l=438
    at TestBedViewEngine.compileComponents core/testing/src/test_bed.ts?l=361
    at Function.TestBedViewEngine.compileComponents core/testing/src/test_bed.ts?l=160
    at compileComponents ...
    at step (tslib/tslib_closure.js?l=199)
    at Object.next (tslib/tslib_closure.js?l=147)
    at tslib/tslib_closure.js:119:65

[devversion]

Closing this now as we will be removing HammerJS anyway in v9.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}