Public bug reported:
Some page of dota2.com is rendered bad on mako RTM#11, but I'm not able
to reproduce the same thing on desktop.
Depending on the page, the entire page is cut on the left (like
http://www.dota2.com/shiftingsnows), or background images are moved to
the left (like http://blog.do
Public bug reported:
If a WebView is used to browse to a page that requests continuous
position updates, the LocationProvider should be paused when the
application goes in the background, and resumed when it gets back in the
foreground.
This could be implemented by making oxide::qt::LocationProvi
I'm not sure what you expected to happen when you have a div that is
relative positioned with "left: 50%" and a left margin of -800px on a
screen that is about 341px wide. By my calculation, that puts the left
edge of it at about -630px. With the div containing an absolute
positioned element with "
OK, maybe I imagined this happening more frequently then. Perhaps the
issue is only with the page using large tables.
Can you check that page? That is the page that definitely worked a few
weeks ago, and I don't see any overflow:hidden uses, so it is perhaps a
separate issue.
http://www.dancecent
Nevermind, I'm seeing the same behaviour now on other browsers.
After a little more investigation with archive.org, it seems that the
website in question has been changed recently, so it's no longer
viewable. Sorry for wasting your time.
** Changed in: oxide
Status: New => Invalid
--
You
Yes, "left: 50%" on a relative element will place it in the middle of
the containing block. But in this case, the containing block is the
document element and the width of the document element is the width of
the visible viewport minus the width of the vertical scrollbar if there
is one (in this ca
** Changed in: oxide
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1402975
Title:
Wrong render of dota2.com on mako RTM #11
Status in Oxide
Public bug reported:
We currently have no tests for input events (eg, keyboard, mouse or
touch). We should add tests for all of these, ensuring that we run tests
for positioned events (mouse, touch) at more than one device scale.
** Affects: oxide
Importance: Medium
Status: Triaged
8 matches
Mail list logo
