27 karma · joined November 15, 2011
Apparantly there are issues with looping (http://www.schillmania.com/projects/soundmanager2/demo/api/) but it points to (http://www.flickr.com/photos/schill/4499319436/) as a way to fix sound loops.
Regarding other technical problems: I've had that issue too with Chrome beta, using csstransforms caused my textboxes to be unclickable(but still tab-able). My solution was to downgrade to the normal Chrome version and hoped it'll be fixed by the time it hit stable.
- No clear 'what to do' on the first page
- Not enough validation errors. I typed in something weird and it didn't present an error. Just a refresh of the page. Maybe a blinking of a field in some cases.
- Where there were validation errors, it doesn't provide feedback on the type of input is acceptable (password)
- Last page of the project creation, 3. Create tasks, there was no clear indication that those were text input fields.
It looks like each page is defined inside a <script type='text/plain' data-kibi='{pathname:'',id:'',location:''}'></script>
Where data-kibi is metadata to specify when, with what data(jsonp) the content inside should be rendered?