Confirmed users
2,023
edits
Mobile/AsyncSubframePanning: Difference between revisions
→2013-07-02
| Line 144: | Line 144: | ||
===2013-07-02=== | ===2013-07-02=== | ||
;done | |||
* BenWa hit testing | * BenWa hit testing | ||
** layout assumed that root frames were container frames, which isn't correct | ** layout assumed that root frames were container frames, which isn't correct | ||
| Line 149: | Line 150: | ||
** two code paths (with root APZC and w/o APZC) | ** two code paths (with root APZC and w/o APZC) | ||
** seems like enforcing that there is always a root APZC would be the best route | ** seems like enforcing that there is always a root APZC would be the best route | ||
;next | |||
* BenWa will finish hit testing before going on PTO | |||
** when he gets back from PTO, hook up hit testing | |||
* Kats will make sure that there is no code assumeing that there is only one APZC | |||
** will require making APZC owned by layer tree not compositor parent, compositor parent will hold a reference to layer tree | |||
* Kats will defer continuing to work on input event transformation | |||