With the browser on Firefox OS the URL bar fades out once the page is loaded, but on SUMO it's displayed permanently. Since we also have the browser navigation bar at the bottom and the SUMO header on top it takes away precious screen real estate for the content. We should make sure the URL bar fades after a few seconds leaving more room for the content.
Summary: URL bar should go fade away on SUMO → URL bar should fade away on SUMO
If this is possible with js, it should be easy. So 1pt or WONTFIX.
Whiteboard: u=user c=general p= s=2013.5 → u=user c=general p=1 s=2013.5
Looked into this
Assignee: nobody → rdalal
Oops accidentally hit save... Looked into this and the way that the items are positioned this is likely going to be very difficult and any solution is likely to cause scrolling issues on iOS/Android. I'm leaning towards WONTFIX.
Rehan, can you outline the non-hacky solution to this issue? The one that might mean a major rewrite. I would like to at least know what we are up against when I explain why we are not going forward with that.
:atopal The non-hacky solution to this would be to restructure the way the page is marked up and change a lot of the positioning. Right now everything is positioned absolute and it mocks `position: fixed;` by using div scrolling. We would need to change this so the body of the page flows normally and the other static elements (header, menus, footer) would need to be position fixed. The one deficiency of this method is that position fixed is still not completely cross platform (http://mobilehtml5.org/ --- you can see a list of supported devices/browsers there --- I am not sure how many of those we care about). And on a number of devices that it is supported on, it is still very jittery or does not behave exactly as expected. But support should only improve.
Converting this to a research bug. We'll file a followup based on a final decision.
Summary: URL bar should fade away on SUMO → [research] URL bar should fade away on SUMO
Implementation bug filed here: Bug 852570
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.