[Browser] White line at the bottom of the viewport

[Giorgio Venturi]

There's a white line at the bottom of the viewport (test on theverge.com & Blinkbox.com)

[Olivier Tilloy (osomon)]

Note that when rotating the device in landscape mode, the white line appears at the right edge of the screen.
It looks like the height of the webview is 1 pixel short to fill the screen.

[Olivier Tilloy (osomon)]

It actually seems to be an oxide bug: I can observe the white line at the bottom of the viewport with a plain oxide WebView opened with qmlscene on a device.

[Olivier Tilloy (osomon)]

I’m not seeing the issue on desktop, so it might be linked to the way the size of the viewport is computed using a non-integer device scale factor.

[Chris Coulson (chrisccoulson)]

There's also an extra pixel on the other axis - if you hold the device in portrait mode and then swipe from left to right and vice-versa, you will see the content scroll by a pixel in either direction

[Giorgio Venturi (giorgio-venturi-deactivatedaccount)]

Hi, I can still reproduce the bug with 14.10 (r243)

[Olivier Tilloy (osomon)]

Yes, it’s marked fixed in oxide (the project), but still triaged in oxide-qt (the package). It will be in the images when a package with this fix is released.

[Launchpad Janitor (janitor)]

This bug was fixed in the package oxide-qt - 1.3.3-0ubuntu1

---------------
oxide-qt (1.3.3-0ubuntu1) vivid; urgency=medium

  * Update to v1.3.3
    - Bump Chromium rev to 39.0.2171.42
    - Fix LP: #1260016 - Add support for application provided protocol
      handlers
    - Fix LP: #1301681 - Scroll the focused editable node in to view after
      a resize
    - Fix LP: #1337506 - Runtime abort with
      FATAL:texture_manager.cc(76)] Check failed: texture_count_ == 0u (1 vs. 0).
      Ensure that we keep the browser compositor GL context and associated
      resources alive as long as the Qt scenegraph holds the frontbuffer
    - Fix LP: #1377755 - Keyboard disappears when switching between text fields
    - Fix LP: #1290821 - WebView.loading is not false when receiving a LoadEvent
      with type == TypeStopped, so properties bound to this never receive an
      update. As "loading" and the main-frame document load events are delivered
      separately from blink, split this in to 2 signals
    - Fix LP: #1354382 - White line at bottom of viewport - fix rounding errors
      when calculating the view size in DIP which results in the view
      underflowing by a pixel in one axis and overflowing by a pixel in the
      other axis
    - Fix LP: #1221996 - Allow user scripts to be injected in to the main world
    - Expose redirect events to WebContextDelegateWorker
    - Fix LP: #1384460 - Delegate unhandled URL schemes to the system
    - Fix LP: #1386468 - Stop leaking V8 contexts

  [ Chris Coulson <email address hidden> ]
  * Add liboxideqtquick0 package
  * Refresh debian/patches/gross-hack-for-dual-ffmpeg-build.patch
  * Add libcups2-dev and libexif-dev build-deps, as the chromedriver build
    seems to pull them in. This is a temporary measure until we can figure
    out why

  [ Alexandre Abreu <email address hidden> ]
  * Add chromedriver to the packaging branch
 -- Chris Coulson <email address hidden> Thu, 23 Oct 2014 08:18:19 -0400