• Profile a startup/reload, sort profile by heaviest calls
• The DomListener-type is a heavy hitter and takes ~45ms of which ~80% are spend in setting up the Gesture

CPU-20171109T111657.cpuprofile.txt

It seems that adding the touch{start/move/end/} events takes a lot longer than other event listener... Suggestions:

• don't have a listener per BaseActionItem but per container (action bar)
• disable gesture when target device does support touch