#850 closed task (fixed)
[release testing] ensure that widget tests have no failures
| Reported by: | alex | Owned by: | Dustin Machi |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | General | Version: | 0.3 |
| Keywords: | Cc: | [email protected]… | |
| Blocked By: | Blocking: |
Description
Change History (5)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
hey adam, I assume you filed these for some bug other than 0.3.1? Were any of them things that should be considered for the release? If not, can we close this bug?
comment:3 Changed 14 years ago by
| Cc: | [email protected]… added |
|---|
sorry for being vague. I filed each of these as separate bugs in trac without setting a milestone. A few ended up in the 0.3.1 release, but most did not. The most significant one worth fixing for 0.3.1 was #870. Also fixed include #885, #886, #874, #875.
I guess you can close this out unless you want me to re-run on a release candidate build tomorrow? dmachi filed FF issues in #927
comment:4 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I'm closing this. If you thought those other bugs were blockers, you probably would have filed them against the release ;-)
Note: See
TracTickets for help on using
tickets.
Ran through widget tests on win32 IE and Opera and filed ~25 mostly insignificant bugs