The code freeze is active now. That means the code will not be changed in favor of adding features. The developers then start to build the browser for the upcoming developer release. The estimated release date is now one day later too. For the coming week, it will be almost only polishing to get a robust and solid developer release.
Proposed beta 2 shedule
Note: This shedule is subject to change. But shows already when to expect the release.
| tree closed / frozen | November 4th |
| en-US builds generated | November 10th |
| l10n builds generated | November 11th |
| results QA tests | November 20th |
| release targeted | November 21th |
Testplans state:
The Testcase completion is already above the level (50%) it had to be for the beta 2 release. Testplan completion is coming a bit behind, because it didn't reached 100% yet. Probably it will not reach it too, before release.
| Testplan completion % | 86.30% (last week: 76,52%) |
| Estimated testcases: | 748 (last week: 762) |
| Testcase completion %: | 59.05% (last week: 59.05%) |
Various bug fixes and recently added features
Bug 453440 - Extend "Clear Private Data" dialog with time period option
Just like in chrome it is now possible to remove Private Data from the last hour, the last 2 hours, the last 4 hours, the last day or just everything.
Bug 428096 - Make clipboard and drag-and-drop import and export HTML on Mac.
This makes it possible to paste HTML into rich text editing widget and to copy HTML from the browser to programs supporting HTML.
Bug 449315 - Support WAV format in <audio> element.
Following the HTML5 spec the <audio>-tag should support WAV-files. This implements this, only 8-bit samples aren't implemented.
Bug 461891 - switch to using v2.2 safebrowsing servers.
The differences between the v2.1 and v2.2 aren't that big. So this bug only adds the ability to have empty add chunk as a way to fill in gaps in the chunk list.
Bug 17612 - view-source link-browsing
This bug adds the functionallity to click on links in the source-code of a page. That way it will be very easy to view the source and follow the stylesheets or javascripts that are in different pages. Normally it should already be in Firefox, but it isn't possible in the last nighlty yet.
Bug 449307 - Support duration attribute on media elements
Bug 462916 - Update liboggplay to pick up ability to compute Ogg duration
This bugs adds properties of duration, bufferedBytes, bufferingRate, and totalBytes for the <video>-tag. The big problem was the duration, because it isn't easable readable in the file. Normally it should be given in the header as X-content-duration, but that is mostly not the cause. Therefor it was needed to peek to the end of the file, to know the end timestamp. Now therefor the server need the ability to get only the last part of the file. As last it is also possible to read the file-size and estimate the length of the video
0 reacties:
Post a Comment