TPEGFX/2015-05-28

Weekly Report

Boris Chiou

• bug 1144012 - Wrap HwcDevice from HwcComposer2D
  • r?

• bug 1161372 - [LayerScope] Add EventRegions fields
  • r+

• bug 1163908 - [LayerScope] Add Heat map in viewer
  • r

• bug 1168015 - (LayerScope) Texture dump performance improvement on B2G
  • r

Chiajung Hung

• bug 1159997 - Use a tight dirty region/rect for PaintFrame
  • WIP/Debug
  • Implement containerLayer based invalidation which roc proposed
  • Trying to move slightly toward Frame based invalidation: Use Frame based invalidation while container layer contains single layer.

Ethan Lin

• bug 1166173 - off-main-thread painting implemetation
  • wip
• bug 930218 - Canvas not wrapped by parent that has border-box sizing
  • study

Jeremy Chen

• bug 1155495 - refactor the part of android fence in TextureHostOGL
  • r+ | land
• bug 1167516 - Enable marionette text_selection_test.js
  • r
• bug 1168326 - Replace SpecialPowers in selection_helper.js
  • debug

Jerry Shih

• bug 1165161 - extend bootAnim playing time
  • f?
  • create our GonkSurface class to hook connect() function and stop the bootAnim in this hook.

• bug 1167535 - b2g crash when we have 4G up file.
  • land
  • uplift to v2.2
  • fanotify
  • monitoring filesystem events

• bug 1155424 - White bar flashes at screen bottom while coming out of full-screen video
  • reading mozFullScreenChange event

• bug 1158670 - setting app scrolling performance
  • reading tiled layer code.

Tingyu Lin

• bug 1161389 Skip AccessibleCaret frame if nsDisplayListBuilder doesn't build caret
  • land
• bug 1161392 - Enlarge the touch area for AccessibleCaret
  • land
• bug 1161384 - Do not fire content mutation event on changes to nsCanvasFrame's anonymous content
  • Debug

Peter Chang

• bug 1164744 - Associate layer transaction cost with dom element changes
  • wip
  • Study how to handle when frame is reconstructed becaused of restyle
• bug 1169115 - [marker]Dump dom info in RestyleTimelineMarker
  • wip
  • Able to see the class name/id in timeline tab

Team

• Health appointment
• Ignite
  • Performance program.
  • Quality Improvement Program

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)