There is still a lot of work to do on mobile, but this makes it
slightly better. Increases the default scale to something sane.
Fix the bug where we don't layout using entire width.
window.outerWidth is somehow completely busted on mobile.
Change-Id: Id574d6ee14ba59f6e835725d378f228796ff7ccf
Was caused by incorrectly building child component props in
willReceiveProps() before new props are actually set.
Simplified code to always rebuild child component props in render().
Removed overly-clever code that was trying to filter out some
prop updates. We don't send spurious prop updates in any case that
I can think of.
Change-Id: Ie067b2d667517c24524863eac62baef0178608cb
The web UI was implying 'folderness' by looking for certain claims against
permanodes. This won't allow us to represent empty dynamic folders, which seems
wrong.
Thus I've changed it to just represent all pemanodes as folders. In the future,
if there are more specific types of permanodes, we can handle that.
Change-Id: I73523634114c61f33705a88a4147e13ad60c59d6
1) We don't need the isMounted() check anymore because we're not poking at the DOM.
2) Detail() now needs a history param.
Change-Id: I420e3211fde40673e3123a2b18460d0d12f32a70
Was basically caused by layout<->scrollbar interaction loop. Fix was to
calculate size of scrollbar and take it into account during layout.
At the same time, I decided to clean up the code and put the search results
scrollbar actually within BlobItemContainer, rather than having
BlobItemContainer reach up and change scroll styles of document.
This necessitated getting rid of some of the clever transform origin
stuff I was doing before, but it is less needed now.
Change-Id: I8641d87d8e593336aed48acef8b31680a52d7e6c
The scroll position doesn't restore when navigating back to the
search page from the detail page. That will be interesting.
Change-Id: I5a008cdd6d1c83a4b8031d14ee26cfd9e383d73d
This improves the performance of the piggy animation by doing it in hardware
and eliminating a layout pass on every frame.
Change-Id: I02cf8b521af60af0e61f70c7f732f97074bdcdc1
Still left to do: update the nav in response to selection changes,
implement nav items, drag and drop.
Change-Id: I3f7cd0b8bdccd11a5816dce2bc214e60f844a130
The effect you were seeing was a difference between hardware and
software compositing paths.
Chrome was promoting the content area to a hardware-accelerated
layer during animation, but dropping it back to software after the
animation was complete. There were little animations for the
checkmarks that were causing us to flip in and out of hardware mode
as you moused around.
Solution: force us to stay in hardware mode the entire time the
nav is open (translate: scale3d() is a well-known way to do this).
Bonus: the scaled text rendering looks better in hardware mode.
BUG: https://code.google.com/p/camlistore/issues/detail?id=284
Change-Id: I62f6c86d1ae12ba043f34c0659633bb5195dc50c
Brad Fitzpatrick