Closed
Bug 1033984
Opened 10 years ago
Closed 10 years ago
Nested-OOP support for v2.1
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
People
(Reporter: jeliu, Assigned: mchen)
References
Details
(Whiteboard: [FT:Stream3][2.1-feature-qa+])
No description provided.
Reporter | ||
Updated•10 years ago
|
Blocks: Stream3_2.1
Reporter | ||
Updated•10 years ago
|
Whiteboard: [FT:Stream3]
Reporter | ||
Updated•10 years ago
|
feature-b2g: --- → 2.1
Comment 1•10 years ago
|
||
What is this meta bug about? Is that a followup to nested content processes?
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Comment 2•10 years ago
|
||
This is the meta bug of nested-oop related features which will be committed by Stream3 team for v2.1 scope.
However, we only include the essential bugs for now, not all of them.
Comment 3•10 years ago
|
||
Isn't this the same as bug 1020135?
Reporter | ||
Comment 4•10 years ago
|
||
This bug only contains the essential nested-oop features we're going to support for v2.1.
The scope of bug 1020135 is much bigger than this one.
Rename this bug to avoid confusion.
Summary: Nested-OOP support → Nested-OOP support for v2.1
Reporter | ||
Updated•10 years ago
|
Blocks: nested-oop
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to Fabrice Desré [:fabrice] from comment #1)
> What is this meta bug about? Is that a followup to nested content processes?
The list here is came out by the discussion with Kan-ru.
In order to show up widget on nested oop iframe, we need to fix them at least in the V2.1.
Updated•10 years ago
|
QA Whiteboard: [2.1-feature-qa+]
Updated•10 years ago
|
QA Whiteboard: [2.1-feature-qa+] → [2.1-feature-qa?]
Updated•10 years ago
|
QA Whiteboard: [2.1-feature-qa?]
Whiteboard: [FT:Stream3] → [FT:Stream3][2.1-feature-qa+]
Updated•10 years ago
|
Flags: in-moztrap?(fyen)
QA Contact: fyen
Reporter | ||
Updated•10 years ago
|
Target Milestone: --- → 2.1 S3 (29aug)
Comment 6•10 years ago
|
||
Jenny, are you planning to land this in 2.1? Or, just to master?
If it's going to land to master only, maybe we can remove feature-b2g:2.1.
What do you think?
Flags: needinfo?(jeliu)
Comment 7•10 years ago
|
||
And, can you assign a component(not General)? Thanks!
General component is used for bugs that we don't know which components we should assign.
Assignee | ||
Updated•10 years ago
|
Component: General → DOM: Content Processes
Product: Firefox OS → Core
Reporter | ||
Comment 8•10 years ago
|
||
Yes, we already have a plan before to discuss on it within the team at the end of this week.
Thanks for your suggestion, Kevin. :)
Flags: needinfo?(jeliu)
Updated•10 years ago
|
Assignee: nobody → mchen
Comment 9•10 years ago
|
||
Confirmed with EM/EPM, and this can be landed before FL.
Updated•10 years ago
|
Flags: in-moztrap?(fyen)
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Flags: in-moztrap-
Comment 10•10 years ago
|
||
No end-user QA verification needed, so marking verified.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•