TPE-Layout/2016-05-31

From MozillaWiki
Jump to: navigation, search

Weekly Report

Astley Chen

CSS Masking - positioned mask

  • bug 1258286 - default value for mask-origin property is border-box but padding-box
    • r- - 2nd review.

Boris Chiou

  • mfbt
    • bug 1276550 - Support operator-> for RangedPtr
      • file | r?
    • bug 1276573 - Add a new constructor accepting two RangedPtr<T> arguments
      • file | r?
  • Web Animations API
    • bug 1276193 - Use used values to compute distance for keyframe spacing
      • file
    • bug 1244590 - implement KeyframeEffectReadOnly spacing modes
      • WIP

CJ Ku

  • bug 1274692 - Using CSS filter on elements taller than 16383px causes element to be cropped at 2048px height
    • WIP
  • bug 1275451 - mask-source(SVG mask) should also respect mask-composite
    • landed
  • bug 1275026 - Too-much-recursion crash with background-clip:text and gradient background on root element
    • landed
  • bug 1276834 - Draw nothing when all mask-image refer to an unresolvable URL
    • r+
  • bug 1274236 - In GenerateMaskSurface , pass the created A8 surface to nsSVGMaskFrame::GetMaskForMaskedFrame
    • r?

Jeremy Chen

Initial-letter

  • bug 1223880 - Implement initial-letter (from CSS Inline Layout Module Level 3)
    • parsing & computing - 100%
    • rendering - OOAD | WIP

Others

  • bug 1275831 - [DEBUG only] Repair block layout debug flags in nsBlockDebugFlags.h
    • file | land
  • bug 1276180 - refactor block layout debug flags in nsBlockDebugFlags.h
    • file

PTO

  • sickleave 2.5 days

Tingyu Lin

Shape-outside

  • bug 1098939 - Implement CSS shape-outside property
    • Study 'float' layout.
    • WIP

Others (Provide information or comments, and triage bugs)

  • bug 1269175 - Convert nsStyleSVG::mStrokeDasharray to be nsTArray
    • land

Team

  • Mercurial extension to suggest reviewers (info provided by Xidorn Quan)
    • reviewers: Suggest potential reviewers for a patch.
    • bugs: Display the bugs that have touched the same files as a patch.
    • components: Suggest a potential component for a patch.

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)