TPE-Layout/2016-08-09: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 5: Line 5:


===CJ Ku===
===CJ Ku===
* {{Bug|1234485}} - (mask-image) Compose mask at compositor.
** prototyping
* {{Bug|1288812}} - When serializing a url() with the local url flag set, it must serialize as just the fragment
** land
* {{Bug|1291280}} - Declare nsStyleImageLayers::Layer::mSourceURI as FragmentOrURI
** land
* {{Bug|1269990}} - mochitests for clip-path basic shapes trigger fatal "Assertion failure: aArray1->Item(1).GetIntValue() == aArray2->Item(1).GetIntValue() (expected matching geometry-box values)
** r?


===Jeremy Chen===
===Jeremy Chen===

Revision as of 03:30, 9 August 2016

Weekly Report

Astley Chen

Boris Chiou

CJ Ku

  • bug 1234485 - (mask-image) Compose mask at compositor.
    • prototyping
  • bug 1288812 - When serializing a url() with the local url flag set, it must serialize as just the fragment
    • land
  • bug 1291280 - Declare nsStyleImageLayers::Layer::mSourceURI as FragmentOrURI
    • land
  • bug 1269990 - mochitests for clip-path basic shapes trigger fatal "Assertion failure: aArray1->Item(1).GetIntValue() == aArray2->Item(1).GetIntValue() (expected matching geometry-box values)
    • r?

Jeremy Chen

Initial-letter

  • bug 1223880 - Implement initial-letter (from CSS Inline Layout Module Level 3)
    • hack for size argument of initial-letter
    • uppercase vs. lowercase
  • float uppercase

    float uppercase

  • float lowercase

    float lowercase

  • non-float uppercase

    non-float uppercase

  • non-float lowercase

    non-float lowercase

  • bug 1293210 - add cap height support to nsFontMetrics
    • file | study

Shing Lyu

Tingyu Lin

Shape-outside

  • bug 1288626 - Add shape-outside support to the style system
    • file | r?

Layout

  • bug 1291110 - The inline element overlaps with the float elements
    • file

AccessibleCaret

  • bug 1195722 - Improve text selection with touch on Windows (turn on accessible touch caret)
    • review

Team

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)
Retrieved from "https://wiki.allizom.org/index.php?title=TPE-Layout/2016-08-09&oldid=1143230"