Comment 2 for bug 1552928

I haven't looked at the BottomEdge from a developer point of view yet (will do soon). This report is really from a user point of view. While such a flick from the bottom edge has always been revealing the bottom edge for me with the old implementations, the new implementation always requires me to try at least 3 times until I manage to pull it up.

Now I have no clue if this is an issue in the component or the apps using the component. However, so far I have seen two apps using the new component (messages and clock) and both show this same issue, which led me to report the bug on the component. If it is indeed an issue of how the apps are using the component, we should mark all those apps as affects too in this report. However, as so far 100% of the apps would be using it wrongly, I can't help but think the API would suggest to be used wrongly and maybe could/should be improved still.