TPE-Layout/2016-10-11: Difference between revisions
Jump to navigation
Jump to search
Astleychen (talk | contribs) (→tpe-layout: weekly report 2016W42) |
(→CJ Ku) |
||
Line 23: | Line 23: | ||
===CJ Ku=== | ===CJ Ku=== | ||
* {{Bug|1299715}} - Replace ContainerItemType::eSVGEffects with eMask and eFilter | |||
** r?. | |||
===Farmer Tseng=== | ===Farmer Tseng=== |
Revision as of 02:53, 11 October 2016
Weekly Report
Team
- A replacement for pdf.js to better PDF rendering support and form interaction.
- To resolve blurry issue while printing PDF due to DPI issue.
- Revamp of printing experience on FireFox.
Reference:
- iThome
- bug 1302489 - [meta] Printing Improvements Triage List
Astley Chen
- bug 1308239 - Remove CSS pref layout.css.masking.enabled
- land - pref control for SVG mask-type prop.
- bug 1271765 - Visual refresh of media controls
- WIP - prepare patches for review.
- bug 1301638 - Using runtime pref to enable/ disable CSS mask properties
- WIP
Boris Chiou
Cameron McCormack
CJ Ku
- bug 1299715 - Replace ContainerItemType::eSVGEffects with eMask and eFilter
- r?.
Farmer Tseng
Jeremy Chen
Initial-letter
- bug 1307402 - Use a more precise bounding box for initial letter texts
- file | land
layout code refactoring
- bug 1307728 - Convert LineReflowStatus to an enum class
- file | land
- followup: CSS Inline Vertical Alignment and Line Wrapping Around Floats by L. David Baron
- PR merged
- bug 1308077 - Add compile time protection while calling nsLineBox::BreakTypeToString
- file | land
Shing Lyu
Tingyu Lin
Details & Summary
- bug 1304441 - Assertion failure: !summary || !summary->IsMainSummary()
- land
AccessibleCaret
- bug 1307027 - The tip of caret is covered by input area
- file | land
- bug 1304263 - Investigate whether long tap injector is needed on Windows with touch support
- review
- bug 1307252 - Touch caret is shown when touch-keyboard or external keyboard is used
- r?
Fennec
- bug 1307100 - Floating toolbar does not hide when the selection highlight is scrolled out of viewport
- land
Tommy Kuo
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)