TPEGFX/2015-04-16

Weekly Report

Boris Chiou

• bug 1144012 - Wrap HAL code from HwcComposer2D
  • WIP
  • Wrap HwcList

• Webide related topic
  • study
  • Remote Debugging Protocol
    • Javascript debugger, wedide related protocol

• Slides for presentation
  • Layerscope
  • RDP

Chiajung Hung

• bug 1154557 - Generate fence for each CompositiableHost to replace the FrameBufferSurface's fence
  • feedback

• BootAnimation
  • Study codeflow and find some strange paint before init logo from gaia

• DisplayList
  • Study CSS spec $8~$9.3
  • Check dirty region during BuildDisplayList

Ethan Lin

• bug 1146214 - Refactor fence delivery to reduce ipc messages and code duplication
  • r+
• bug 1154557 - Generate fence for each CompositiableHost to replace the FrameBufferSurface's fence
  • r?
• The flow of BuildContainerLayerFor
  • study

Jeremy Chen

• bug 1152263 - [Messages][Text Selection] Hard to drag the caret when there is an attachment in the beginning of a message
  • r?
• bug 1152502 - Long pressing on attached files will cause blue text-selection carets to appear around or under the file preview
  • f
• Clipboard Web API
  • study
  • implementation update - http://caniuse.com/#feat=clipboard

Jerry Shih

• bug 1141053 - 2.1s contact app scrolling performance
  • uplift
  • Overdraw problem.
  • Apply culling and adjust compositor thread priority to improve compositor performance.

• bug 1149492 - Handle the duplication of fd for thread link
  • r-
  • still under discussion with bent.

• N5-L vsync-rd problem
  • debug
  • Update base-image to android-l 5.1.

Morris Tseng

• bug 1147279 - The event region seems wrong if element becomes image layer.
  • r+

• bug 1152172 - [Text Selection] Left caret disappeared in view email
  • debug

Tingyu Lin

• bug 1153076 - Modify SelectionCarets StartWord() logic to support Android
  • r
• bug 988143 - Enable text selection and touch caret in Gecko on Fennec
  • r
• bug 1110039 - Refactor Touch/SelectionCarets
  • Refine documentation and attach patches for reviewing.
  • Make a state transition diagram: Copy_n_Paste#CopyPasteEventHub_State_Transition_Diagram
  • r?

Peter Chang

• bug 1144990 - Dump display items with class id and name
  • land

• bug 1127170 - Layer transaction spends more than 150ms when switch app
  • land

• Layout study

Team

• Team building Q2
• gfxhackathon

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)