TPEGFX/2015-05-21
From MozillaWiki
< TPEGFX
Contents
Weekly Report
Boris Chiou
- bug 1144012 - Wrap HwcDevice from HwcComposer2D
- WIP
- Remove render dependency
- Wrap mHwc from GonkDisplay
Chiajung Hung
- bug 1159997 - Use a tight dirty region/rect for PaintFrame
- WIP/Debug
- rebase to newer code base
- upload a WIP until now
Ethan Lin
- bug 1155495 - refactor the part of android fence in TextureHostOGL
- feedback
- bug 1166165 - B2G Assertion failure: Cannot compute with aOther null value, at at ../../dist/include/mozilla/TimeStamp.h:461
- land
- bug 1166173 - off-main-thread painting implemetation
- study
- also study bug 1083101 - Add Multithreaded DrawTargetTiled version to Moz2D
Jeremy Chen
- bug 1155495 - refactor the part of android fence in TextureHostOGL
- f+ | r-
- bug 1166191 - touch events in sms app iframe area are all blocked so that sms cannot change focus and function normally
- file
- maybe related to bug 1166193 and bug 1166171
- gfx rendering pipeline
Jerry Shih
- bug 1155797 - N5-L vsync source problem
- uplift to v2.2
- test with TPE-QA team
- bug 1165200 - can't play bootAnim in m-c
- r+
- fix the all black screen problem during bootAnim playing in m-c
- bug 1165161 - extend bootAnim playing time
- r?
- export animation stopping function to user
- bug 1164785 - refine systrace label in b2g
- land
- bug 1158670 - setting app scrolling performance
- debug
- reading tiled layer code.
Morris Tseng
- bug 709490 - Run WebGL on Web Worker with commit()
- r-
- Applied bug 1144906 manually and check where should be modified after applying that patch.
- bug 1155493 - Refactor event dispatching in Touch/SelectionCarets
- r+
- bug 1166251 - Compiler error: ./NodeListBinding.cpp:32:15: error: no matching function for call to 'StrongOrRawPtr'
- filed
- duplicated, bug 1165184
Tingyu Lin
- bug 1164233 - Intermittent test_touchcaret.py AccessibleCaretCursorModeTestCase.test_textarea_touch_caret_timeout,TouchCaretTestCase.test_contenteditable_move_caret_to_front_by_dragging_touch_caret_to_top_left_corner | AssertionError: u'!ABCDEFGHI' == u'!ABCDEFGHI'
- land
- bug 1068525 - [Text selection] Keep the size of AccessibleCarets during zooming
- land
- bug 1161389 Skip AccessibleCaret frame if nsDisplayListBuilder doesn't build caret
- r?
- bug 1161392 - Enlarge the touch area for AccessibleCaret
- r+
Peter Chang
- bug 1164744 - Associate layer transaction cost with dom element changes
- wip
- add dom attribute changes in frame and plan to add render statistics for performance
Team
- FxOS plan
- Perf is in high priority
- Finalize during whistler work week
Rule of Thumb
Status code:
- OOAD: In analysis or design phase.
- WIP: working on WIP patch.
- feedback(f): feedback a patch
- feedback?(f?): WIP is ready for feedback grant.
- feedback+(f+): Get positive feedback.
- feedback-(f-): Get negative feedback.
- review(r): review a patch.
- review?(r?): patch is under review
- review+(r+): get review+ and ready to check-in
- review-(r-): get negative review feedback. Fix problems and switch back to r? again.
- land: patch check in.
- debug: Figure out the root cause of a bug/ try to repro that bug, etc...
- file: file a bug
- PTO: take personal leave
- interview(I)
- study: Spend time on domain knowledge study, such as multimedia transport technology, compress format, real-time rendering.
- presentation
- Write a personal blog, which is relative to work, such as articles on MozTech, or what you experience in a work week.
- WIKI/ MDN article writing.
- If you write a technical blog or anything relative to work, it's welcome to share it on weekly report.
- Do a presentation of technical topics
Status code combination rule
Combine status code with "|". For example
** OOAD|WIP
Which means you work on both OOAD and WIP in the last week.
land status code
If your patch is target for specific branch, instead of central, postfix branch version. For exp
** land(1.4)