TPE-Layout/2016-07-19

Weekly Report

Tingyu Lin

Shape-outside

• bug 1098939 - Implement CSS shape-outside property
  • Hacking border-raius with shape-box.

AccessibleCaret on Fennec

• bug 1285273 - Crash in nsLayoutUtils::FindNearestCommonAncestorFrame
  • land
  • Request uplift to aurora and beta.

Layout

• bug 1273049 - Move the relevant info of frame bit flag from in block-and-line.html to nsFrameStateBits.h
  • r-
• bug 1286468 - Rename line related functions in nsBlockFrame to conform to Mozilla coding style
  • file

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)