[Toolbar] Bottom edge swipe is detected 2gu away from edge

[Oren Horev]

currently I can grab the toolbar with an initial touch at more than 10GU away from the edge, a natural position to flick a web page.

This makes the bottom edge swipe conflict with scrolls

expected behaviour
-----------------
edge detection area shouldn't exceed the shell threshold of 2gu

Update
------
This issue is occurring across all apps. Seems that edge detection / toolbar triggering with a bottom edge swipe is not consistent with detection other behaviours of other edges

[Olivier Tilloy (osomon)]

This is happening because the browser currently doesn’t use the SDK’s toolbar, it implements its custom solution.
This will change in the future. In the meantime, we need to ensure the trigger zone has the same height as in the SDK. That’s currently 2 grid units.

[Olivier Tilloy (osomon)]

Lowering the importance: while annoying, it’s not something that renders the app unusable. Definitely an issue to fix soon, but not a showstopper.

[Olivier Tilloy (osomon)]

It looks like we could make use of the GenericToolbar type that’s in the SDK. Unfortunately at the moment it’s an internal type, meaning it’s not publicly exported.

[Oren Horev (oreneeshy)]

Though demoing today I had tripped on that one I agree it's not a show stopper :-)

[Olivier Tilloy (osomon)]

I had a look at how we can fix that properly, and it appears it’s far from trivial.
The current custom implementation of the toolbar in the browser differs a lot from the one in the SDK. The GenericToolbar in the SDK is not publicly exposed, so we can’t use it. I tested copying the necessary components from the SDK and adapting the browser’s code to them, but it results in a huge diff, and broken interactions in many subtle ways.
This requires more work, and there’s no way we can fix it safely in time for the demo. Sorry.

[Olivier Tilloy (osomon)]

The SDK now exposes a generic Panel component, that the browser will use to replace its custom RevealingBar component.

[Oren Horev (oreneeshy)]

reopened this bug as this i still happening on browser as well as all apps. i suspect it is a problem with the toolbar triggering - you can swipe the toolbar in even when starting the the edge swipe a few GU into the view.

[Olivier Tilloy (osomon)]

Right, but is it really as bad as 8 gu away from the edge? If not, please file a new bug instead of re-opening this one.

[Oren Horev (oreneeshy)]

you are probably right it's only 2-3GUs but still off the edge significantly. Which project owns this bug? Unity8 or toolkit?

[Olivier Tilloy (osomon)]

I’d say the UITK (ubuntu-ui-toolkit).

[Tim Peeters (tpeeters)]

The "triggerSize" is 2 grid units, and this was done on purpose.

On a phone, less may work well, but on desktop the toolbar will become unusable. So I propose to fix this bug only in combination with fixing this one: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1182734 where perhaps on desktop we should always have the toolbar active so that the users don't have to position the mouse cursor in the bottom few pixels of the application window?

[Tim Peeters (tpeeters)]

If the triggerSize of 2 GU is too large, this is a different bug from the original bug described here.
If the triggerSize needs to be changed, please open a new UITK bug for that. Note that we will first need a solution for opening the toolbar on desktop before reducing the triggerSize.