- Mozilla firefox developer how to#
- Mozilla firefox developer update#
Use page background as "checkerboard" for APZC Web pages from the same domain are indiscernible in Firefox Start tiles Use mozIColorAnalyzer for autocomplete search result tiles Metro firefox Autocomplete results should open in a new tab when ctrl or shift is pressed Get talos tests running in Win8 Metro immersive modeĭetect if Direct2D has gone away before updating render mode Provide the ability to enter private browsing from within Firefox Metro
Mozilla firefox developer how to#
Provide an option for how to handle links and pinned secondary tiles Provide an option for how to handle links when Firefox is the default browser Provide site authors with the ability to display their site on the Desktop browser Share charm Win 8 Metro - Support IE10 markup to determine what is shared Investigate connecting up the new win8 spellchecking Product Backlog: View Bugzilla Full Query ID
Improve forecasts so that the stakeholders make the best decisions about the direction of the product. Support continual planning as the product emerges so the plan matches reality. Enable work to be prioritized so that the team is always working on the most important features. Given the volume of work remaining and our current velocity range, 9 - 31 points of work may carry over to the 31C-30A-29B release cycle.Īll work related to the ongoing development and maintenance of the Firefox for Windows 8 Touch Product are collected and prioritized in the Product Backlog. The remaining amount of work for the 30C-29A-28B release cycle totals 77 points for the final iteration: View Release Plan. Given the current median velocity there is a 90% likelihood that between 46 and 68 points of work, with a median value of 56, can be completed in the final iteration of the 30C-29A-28B release cycle. Team accomplished a 57% point closure rate during Iteration IT-30C-29A-28B.2. 27 points of work is Engineering related and 8 points is UX related. 35 points of work was not completed during Iteration IT-30C-29A-28B.2 and carried over. There was no change in the velocity range from the previous iteration. At a median velocity of 56, there is a 90% likelihood that the actual velocity for the upcoming iteration will fall between 46 and 68. Team velocity decreased by 1 point (57 to 56) from the previous iteration. Team completed 47 points across 17 bugs which resulted in a median velocity of 56 points per iteration. Mozilla firefox developer update#
Note: Next update on Monday March 17 following the conclusion of Iteration 30C-29A-28B.3Īt the conclusion of Iteration IT-30C-29A-28B.2: Metro Firefox is not planned to be released as part of main stream Firefox.ĭevelopment can continue on the project branch located at: 1.8.2 Iteration Planning/Status Meeting.
0 kommentar(er)
