TPE-Layout/2017-02-21

Weekly Status

Boris Chiou

stylo animations

• bug 1338087 - stylo: Stop storing StyleAnimationValue
  • land
• bug 1339704 - stylo: The property value with !important level doesn't override that with animation level
  • file
• bug 1340445 - stylo: use DOM slots for EffectSet
  • file
• bug 1340506 - stylo: avoid doing composeStyle for overridden animation properties
  • file
• bug 1339704 - stylo: Filter out the CascadeLevel which doesn't need to be styled in GetServoAnimationRule
  • file
• bug 1340961 - stylo: handle missing final keyframe with !important on CSS Animations properly
  • file
• bug 1334036 - stylo: Support off-main-thread animations
  • wip

stylo

• bug 1341003 - stylo: we wait for visited coloring forever in test_animations_omta.html
  • file

Shing Lyu

Stylo

• Reviewed overall test plan progress
• Bug 1329919 - Landed tp5 crash fix
• Bug 1337305 - Identified talos g2 crash root cause
• Bug 1337229 - Rebase
• Testsed real website diff testcase from cpterson

Evangelism

• NTU School program coordination
• Student project mentoring

Tingyu Lin

• bug 1326407 - Implement the rendering of basic shape inset() for CSS shape-outside
  • land
• bug 775624 - Refactor nsReflowStatus
  • r?
• bug 1339797 - Using "Select all" option in Text selection menu in a text box dismisses the menu
  • r+
• bug 1326409 - Implement the rendering of basic shape polygon() for CSS shape-outside
  • OOAD

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