trailsy does not yet work on Chrome nor Firefox on Android 3.4.0

[smathermather]

[danavery]

Steve, can you let us know if this is still an issue? The mobile layout isn't complete, but it should hopefully produce something a little more useful now.

[smathermather]

I get a more meaningful page (see below) but no functional interactions and no visible map:

[danavery]

Thanks, Steve.
That's actually an improvement, and exactly what we're expecting at this point. It's obviously still under construction--if you click on the arrow at the top that should retract that detail panel and reveal the map underneath. The positioning of things isn't quite right yet. But it's getting there.

[smathermather]

It retracts, but doesn't reveal a map yet.

[smathermather]

Just a note-- this still doesn't work on Android in FF. It does work partially and slowly on Chrome (map displays, but is excruciatingly slow to switch between trails).

Also, see #183

[alanjosephwilliams]

@smathermather could you give us an update on this issue?

[smathermather]

You mean another? (I gave one 17 hours ago) :D

[alanjosephwilliams]

Ah good point. Anytime you can chime in again. We reduced the amount of data coming over the wire, so I am interested to know if there is any significant (or even worthwhile) improvement in load times.

[smathermather]

Gotcha. I'll check it out.

[smathermather]

Just for clarification-- trailsy-dev or trailsy or are they the same?

[danavery]

trailsy-dev is the staging/experimental setup. That'll have the most recent
changes, but slightly outdated data.

On Fri, Nov 8, 2013 at 1:22 PM, Stephen Mather notifications@github.comwrote:

Just for clarification-- trailsy-dev or trailsy or are they the same?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/114#issuecomment-28099085
.

[smathermather]

On FF on Android, I get no functionality (no trail loads, no ability to get to map, just blank screen with header at top, "Loading Nearest Trail..." blue bar near bottom).

On Chrome, it seems functional, but painfully slow.

[alanjosephwilliams]

Thanks @smathermather. We'll ask you for another test soon enough.

[alanjosephwilliams]

@smathermather mind taking another look? Dan has pushed some updates to trailsy-dev.herokuapp.com to improve performance, but we've been testing only on older versions of iOS thus far.

[smathermather]

initial load is fast on both, trails never load in chrome, cannot switch between trails in in FF (BTW, fast android device.. quad core nexus 4....)

[danavery]

@smathermather apologies for the questions...are you even getting trail lines on FF? Or just the trailheads?

[smathermather]

Hey @danavery, trail lines show up on FF, and I'll retract what I said-- it is possible to switch between trails, it's just slow. BTW, any debug mode I should be running that would be helpful?

[danavery]

I'm wondering if the media queries are getting thrown off there, and we're feeding a poorly-laid-out desktop version to large devices.

[smathermather]

It looks like a mobile version... (I think)... . screen shots in the am...

Dan Avery notifications@github.com wrote:

I'm wondering if the media queries are getting thrown off there, and we're feeding a poorly-laid-out desktop version to large devices.

—
Reply to this email directly or view it on GitHub.

[alanjosephwilliams]

@smathermather could you give an update on this whenever you have some time? Thanks!

[smathermather]

Sure. I'm running Ubuntu Touch on my phone at the moment (trailsy doesn't work well on that browser either, but it's a pre-alpha OS, so we won't hold that against trailsy... :), but will be switching back to Android in the next week or so.

[alanjosephwilliams]

Thanks Steve!

On Mon, Dec 2, 2013 at 11:52 PM, Stephen Mather notifications@github.comwrote:

Sure. I'm running Ubuntu Touch on my phone at the moment (trailsy doesn't
work well on that browser either, but it's a pre-alpha OS, so we won't hold
that against trailsy... :), but will be switching back to Android in the
next week or so.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/114#issuecomment-29685400
.

e: alan@neighborland.com
t: @alanjosephwilli
p: 817 713 6264