When browser & sidestage co-exist, an unwanted shadow appears

[John McAleely]

(from: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AnhaJaYdDD6udHN1V1owS1ZLc2xFZkxZNmhGaFEwTlE#gid=2)

"the sidestage shadow is back in the browser", from andypowers. This is an unwanted 3d shadow effect (seen on Manta, untested on flo), which is visible when the browser shares the screen with a sidestage app"

[Michał Sawicz (saviq)]

Can you provide more details (an image, ideally)?

If you mean the translucent dark-grey bar on the left of the side stage (the "handle"), then that's expected, currently main and side stage apps don't "share" the screen, but sidestage app is overlaid on top of main stage app, and this shadow is meant to signify that.

Split mode (where main stage app will be ~square) is planned, but wasn't yet implemented.

[John McAleely (john.mcaleely)]

As I understand from andy powers (original reporter), the drop shadow on the bar between the side stage and the main stage app is being removed/redesigned.

It's possible this new design has not yet stabilised, and so the current behaviour on the tablet is the best we can do. From his choice of language (he's not in today), I assume he's seen builds where it had been removed.

[John McAleely (john.mcaleely)]

Whilst I think it would be interesting to confirm if andy powers is correct - ie there have been builds without this, I don't think that fixing this is high priority for the MWC build, unless it's trivial.

I note that it is 'medium' here: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AnhaJaYdDD6udHN1V1owS1ZLc2xFZkxZNmhGaFEwTlE#gid=2

[John McAleely (john.mcaleely)]

nb - I think the jpeg is rotated 90 degrees, so the vertical line on the N10 screen is running nearly horizontal on this image.

[Andrew Powers (andrew-powers)]

I'm not sure that's it, John. I opened the browser on the N10 on the ubuntu.com/phone page and as it loads that shadow effect appears 2/3rds of the way across the screen immediately, i.e. no side stage app has been activated yet. It remained even when you reloaded the page.

[John McAleely (john.mcaleely)]

Ah, ok, in which case that's bug #1281088. I think that means this bug is worth taking off the mwc hitlist then