Closed Bug 1303493 Opened 9 years ago Closed 9 years ago

HTML Contingency Bug #1

Categories

(DevTools :: General, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: MarcoM, Unassigned)

Details

No description provided.
Whiteboard: [devtools-html]
Assignee: mmucci → nobody
Summary: Sample HTML Contingency Bug #1 → HTML Contingency Bug #1
Flags: qe-verify-
Whiteboard: [devtools-html] → [reserve-html]
Whiteboard: [reserve-html] → [devtools-html]
No longer blocks: devtools-html-phase2
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Whiteboard: [devtools-html]
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Whiteboard: [devtools-html]
Status: REOPENED → NEW
This bug and the related ones are missing a description. Therefore it is impossible for anyone wanting to help with it to contribute a patch. So, please *always* provide a proper summary and at least a one-sentence description of what should be done. Sebastian
Marco can probably explain this better, but: This bug (and the other ones like it) are part of the devtools.html phase 2 project for which we are doing project management. Part of the process we have put in place includes making sure we have contingency bugs included in our plan so we can be fairly confident we'll reach our release target. So, as of now, we do not know what these bugs will be addressing. As new issues arise, we'll be using these contingency bugs by renaming them to the right thing.
Contingency used for: Bug 1304701 - Vertical layout is not initialized correctly in newly opened devtools
No longer blocks: devtools-html-phase2
Status: NEW → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → INVALID
Whiteboard: [devtools-html]
(In reply to Patrick Brosset <:pbro> from comment #2) > Marco can probably explain this better, but: > > This bug (and the other ones like it) are part of the devtools.html phase 2 > project for which we are doing project management. Part of the process we > have put in place includes making sure we have contingency bugs included in > our plan so we can be fairly confident we'll reach our release target. > > So, as of now, we do not know what these bugs will be addressing. As new > issues arise, we'll be using these contingency bugs by renaming them to the > right thing. Thank you for the clarification! It's still a bit strange, though, to create the bug reports before you actually encounter them. Part of the confusion was also that they got P5, which means that the team is not planning to work on them. Sebastian
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.