** Changed in: ubuntu-ux
Assignee: (unassigned) => James Mulholland (jamesmulholland)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575191
Title:
plus.google.com re-layouts horizontally when
+Olivier Tilloy Never hiding it in desktop mode should be very
obvious... but this is something of a middle ground where it's being
used in tablet mode. The screen is large enough to switch into the
tabbed mode, but it's still using a touch interface on a small screen...
I'm not sure what the
I’ve asked design to comment on the proposed solution (never auto-hide
the top bar for larger screens, like the M10), which sounds reasonable
to me. Let’s see what they say about it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually I agree, it seems the correct solution is not to hide the
location bar on larger screens (which would be a UI improvement anyway
IMHO).
James the Google UI elements auto-hiding won't change the viewport size
or the width so that won't affect the scaling so that should be fine.
--
You
+Chris Coulson
I'm not disputing what you say, since I'm not in a position to fix this
issue, however if the solution suggested by +Daniel Bull is not correct
then can you clarify what would be the correct solution, since currently
on the M10 tablet, Google+ is unusable.
If I'm reading your post
I already explained why the viewport size has to be changed when the
location bar moves - content that's fixed to the viewport (CSS position:
fixed or scrollbars) will be positioned incorrectly and could be outside
of the webview if it's not. Not resizing the viewport is not going to
happen.
Our
Actually that's a good point +Daniel Bull, I guess it makes sense not to
change the viewport size... the question is what should it be set to...
the site looks better (no blank borders) with the viewport set to the
largest size it's going to be... but by rights, if the page tries to
render inside
I can understand why google is changing the width based on the viewport height,
there is some logic behind it...
They want the page to render in a way that prevents posts being vertically
cropped too much (which would result in the user only being able to view a
small part of the post and
Could it be that the site is sending some different HTML based on the
browser string on the device?... perhaps we need to alter the user agent
string depending on whether the browser is operating in "mobile" format,
or desktop "tabbed" format?
--
You received this bug notification because you
I should re-phrase "website bug" as something else ("website issue",
perhaps?) because it probably isn't a bug in the traditional sense - it
has a responsive UI that most likely doesn't expect the viewport size to
change as a result of scrolling.
--
You received this bug notification because you
There's basically nothing we can do about this in Oxide - as Olivier has
pointed out, this is a website bug and is specific to the desktop
version of Google Plus. Oxide correctly changes the viewport height
after the location bar changes position, otherwise elements fixed to the
bottom of the
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
12 matches
Mail list logo
