TPEGFX/2016-02-25: Difference between revisions

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


* {{Bug|1244049}} - Use scoped enum for nsCSSPseudoElement::Type
* {{Bug|1244049}} - Use scoped enum for nsCSSPseudoElements::Type
** land
** land
* {{Bug|1250820}} - Use scoped enum for nsCSSPseudoClasses::Type
** file


* {{Bug|1234403}} - Document/CSSPsuedoElement.getAnimations() should return animations associated with pseudo elements
* {{Bug|1234403}} - Document/CSSPsuedoElement.getAnimations() should return animations associated with pseudo elements

Revision as of 08:51, 24 February 2016

Weekly Report

Astley Chen

Boris Chiou

  • bug 1249212 - Make ComputedTiming.endTime handling match (soon-to-be) updated spec
    • r
  • bug 1244049 - Use scoped enum for nsCSSPseudoElements::Type
    • land
  • bug 1250820 - Use scoped enum for nsCSSPseudoClasses::Type
    • file
  • bug 1234403 - Document/CSSPsuedoElement.getAnimations() should return animations associated with pseudo elements
    • r?
  • bug 1241784 - Implement Animatable interface for (CSS)PseudoElement
    • r-
  • bug 1248340 - Implement step-middle
    • study
    • Check the differences between Gecko and Chromium(WebKit)
  • bug 1249219 - Animation mutation observers do not support animations on pseudo elements
    • study

CJ

Ethan Lin

Jeremy Chen

Jerry Shih

Morris Tseng

Peter Chang

Tingyu Lin

Details & Summary

  • bug 1249556 - Support toggle <details> and <summary> by keyboard
    • file | r-
    • Need to address bz comments.

AccessibleCaret on Fennec

  • bug 1246918 - AccessibleCaret disappears when swiping down the page
    • land
  • bug 1097398 - Match Android L text selection handles
    • r?
    • Need to address reviewer's comments.
  • bug 1248847 - Add DEBUG-only assert for AccessibleCaretEventHub refcount > 1
    • file | land
  • bug 1249201 - Continue showing AccessibleCaret when scrolling for panning the page
    • file | WIP
    • Discuss with kats about the possible approaches.

Other (Provide information or comments, and triage bugs)

Vincent Liu

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)