TPEGFX/2015-09-17: Difference between revisions
< TPEGFX
Jump to navigation
Jump to search
Vincent Liu (talk | contribs) |
|||
| Line 5: | Line 5: | ||
===Jerry Shih=== | ===Jerry Shih=== | ||
* {{Bug|1166173}} - off-main thread painting | |||
** OOAD, WIP | |||
** https://bugzilla.mozilla.org/attachment.cgi?id=8653877 | |||
* {{Bug|1194923 }} - Crash in mozilla::layers::CompositorOGL::BindAndDrawQuads | |||
** debug | |||
** https://wiki.mozilla.org/Mobile/Fennec/Android/AdvancedTopics#Enabling_C.2B.2B_debugging | |||
===Morris Tseng=== | ===Morris Tseng=== | ||
Revision as of 02:23, 17 September 2015
Weekly Report
Boris Chiou
Jeremy Chen
Jerry Shih
- bug 1166173 - off-main thread painting
- bug 1194923 - Crash in mozilla::layers::CompositorOGL::BindAndDrawQuads
Morris Tseng
Tingyu Lin
- bug 1203879 - Rethink the relationship between APZ, wheel event, and AccessibleCaret
- file
- bug 1204530 - The cursor position on "To:" is incorrect after pressing "enter", enter text, and delete text
- file
- bug 1204872 - Add gtest for AccessibleCaretManager
- r+
- Addressing reviewer's comments
- bug 1199161 - [feature] smarter copy & paster float panel to show related actions by matching patterns
- r?
- Add the selected text to CaretStateChanged event.
Vincent Liu
- 2D Canvas Worker
- Assert happens under stress test. Assertion on nsCSSParser because of thread competing.
- A threadsafe CSSParser is needed for both main/worker thread.
- Fail to draw canvas with text. mCanvasElement gets nullprt and fails to return in CanvasRenderingContext2D::SetFont()
- Collect font operations. More understanding on rule tree and style-context tree.
- Assert happens under stress test. Assertion on nsCSSParser because of thread competing.
- bug 1186826 - Implement an abstraction object for NativeWindow to hide hardware dependent operations
- A present to Milan/Jet to introduce about Fxos-update
- WIP
CJ
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)