Re:Groundwork - A Responsive HTML5, CSS and JavaScript Frame...
by davej on Tuesday February 19, 2013 @07:32AM
(#5243925)
I assume Belhor means the UI responsiveness. The :hover transitions are a bit too long for my tastes and it definitely creates a laggy feeling.
[ Parent
| on HN ]
Re:Groundwork - A Responsive HTML5, CSS and JavaScript Frame...
by yalooze on Tuesday February 19, 2013 @07:53AM
(#5243974)
Scrolling up and down the page feels a little laggy too (Chrome 24, Win7). Is that a drawback of how the 'responsiveness' is coded?
Re:Groundwork - A Responsive HTML5, CSS and JavaScript Frame...
by PavlovsCat on Tuesday February 19, 2013 @09:56AM
(#5244562)
Going to the URL of the iframe directly is much faster for me: http://groundwork.sidereel.com/home.html
Re:Groundwork - A Responsive HTML5, CSS and JavaScript Frame...
by LandoCalrissian on Tuesday February 19, 2013 @05:16PM
(#5247439)
That completely made the difference, they should probably consider changing that.
Re:Groundwork - A Responsive HTML5, CSS and JavaScript Frame...
by hbogert on Tuesday February 19, 2013 @12:38PM
(#5245694)
Indeed, went from unusable to smooth on a nexus 7
Re:Groundwork - A Responsive HTML5, CSS and JavaScript Frame...
by ghepting on Wednesday February 20, 2013 @11:04PM
(#5255297)
Thank you all very much for the feedback on this, I wasn't aware of the negative impact the viewport resizer was having on these mobile devices. It is to be expected that iframes would perform poorly on them and I had included a regex to redirect mobile user agents to the home.html page to avoid them having that served up. Perhaps the mobile device detection needs a more reliable method... Any suggestions? :)