javascript - Is there a way to debug rendering problems in a famo.us app? -
is there way turn debugging on or command show rendering problems when using famo.us?
log statements helpful or other way of telling going when app being rendered.
edit: here rendering problems have seen far
1- layout inconsistent across browsers (not talking ie yet!!!!).
safari 7.02:
chrome35:
android firefox 29:
2- scrolling famo.us screwed.
i have 3 main sections app (website):
- header (which scrollcontainer 4 surfaces).
- footer (which scrollcontainer 1 surface).
- content (2 scrollcontainers on left side , 2 scrollcontainers inside deck component on right side. each text/paragraph surface in respective scrollcontainer).
now, if go app, notice scrolling screwed , have no idea why! don't know how can debug mess.
p.s: code left un-minified , comments on purpose.
but wait there more. scrolling confusing user the user has no idea view scrollable because no scrollbars visible. you can see on famo.us demo page. go , try scroll :). way can scroll if go left side of page ...
3- deck component seem arrange cards randomly on initial load based on browser! if things aren't screwed enough. see screenshot below:
chrome35 desktop renders green card first:
ff29 desktop renders red card first:
with above issues. have no idea how fix them or why happening. list of things me developer debug problems famo.us:
- enable debug logging when using components.
- throw js errors when using components incorrectly.
- warn me potential layout problems if using components known issues.
- have better documentation. read code base understand how use because famo.us docs not adding value without having examples whereas open source code does.
- more articles talking layout , page structure. fundamental thing. if can't right, there no point playing animations on page not viewable correctly!
i have noticed ff29 on desktop lags when interact deck of cards whereas on chrome doesn't. backing 60fps claim across devices start. show performance metrics , comparisons prove claim.
i want use famo.us , contribute fixes if time this how feel famo.us.
yes, great if there gave more info. famoushint or something. use jshint @ least helps common javascript errors.
also, has saved me few times well. http://famo.us/guides/pitfalls
but agree little buggy @ point, i've been having trouble scrollview.
Comments
Post a Comment