Confirmed users
6,361
edits
QA/Firefox3/TestResults/RC1/RC2BugCandidates: Difference between revisions
QA/Firefox3/TestResults/RC1/RC2BugCandidates (view source)
Revision as of 02:16, 23 May 2008
, 23 May 2008→Bug Candidates for Triage
| Line 11: | Line 11: | ||
Bugs (as of 5/23/08): | Bugs (as of 5/23/08): | ||
*{{Bug|433340}} – bookmark dialog covers candidate window when using IME. Status: recommended for RC2 with patch in place. | *'''[RC2+]'''{{Bug|433340}} – bookmark dialog covers candidate window when using IME. Status: recommended for RC2 with patch in place. | ||
* Renom'd {{bug|433298}} EULA cut off checkbox/buttons on bottom - unusable on small (EeePC) screens for blocking-firefox3. Linux users in this mode have a minimal way to move forward with the installer. Status: patch ready. | *'''[RC2+]'''Renom'd {{bug|433298}} EULA cut off checkbox/buttons on bottom - unusable on small (EeePC) screens for blocking-firefox3. Linux users in this mode have a minimal way to move forward with the installer. Status: patch ready. | ||
* {{Bug|433942}} – Focus lost when going "Back" a page after dismissing a notification bar [tracy] | * {{Bug|433942}} – Focus lost when going "Back" a page after dismissing a notification bar [tracy] | ||
* {{Bug|324334}} - Cannot switch to Error Console in the "Window" menu. Per [https://bugzilla.mozilla.org/show_bug.cgi?id=324334#c8 c#8], it only affects error console and the Software Update window. | * {{Bug|324334}} - Cannot switch to Error Console in the "Window" menu. Per [https://bugzilla.mozilla.org/show_bug.cgi?id=324334#c8 c#8], it only affects error console and the Software Update window. | ||
;Crashers [ss] | ;Crashers [ss] | ||
* {{Bug|435047}} – Consistent Crash in nsHTMLReflowState::GetNearestContainingBlock when visiting site. depends on {{bug|398332}} | *'''[RC2+]'''{{Bug|435047}} – Consistent Crash in nsHTMLReflowState::GetNearestContainingBlock when visiting site. depends on {{bug|398332}} | ||
* {{bug|433525}} - crash [@ nsNavHistoryQueryResultNode::IsContainersQuery()]. Number 1 topcrash, is a recent regression which we should probably respin for. The bug has a patch ready to go. | *'''[RC2+]'''{{bug|433525}} - crash [@ nsNavHistoryQueryResultNode::IsContainersQuery()]. Number 1 topcrash, is a recent regression which we should probably respin for. The bug has a patch ready to go. | ||
* {{Bug|434401}} – crash [@ gfxWindowsFont::GetOrMakeFont(FontEntry*, gfxFontStyle const*)]. that may be happening in thebes or layout. dbaron believes thebes. Needs a developer, comments in stack aren't helpful. This is a crash on startup. | * {{Bug|434401}} – crash [@ gfxWindowsFont::GetOrMakeFont(FontEntry*, gfxFontStyle const*)]. that may be happening in thebes or layout. dbaron believes thebes. Needs a developer, comments in stack aren't helpful. This is a crash on startup. | ||
* {{Bug|434403}} – startup crash [@ nsDocShell::SetupNewViewer(nsIContentViewer*)]. recent regression. While we saw this crash in beta 5 (presumably from upgrading from beta 4), it's much greater this release and happens at a different address. If timeless is right in that bug, it's a pretty easy fix. but we'd need to test with a round of RC1 -> RC2, to confirm its been fixed. | * {{Bug|434403}} – startup crash [@ nsDocShell::SetupNewViewer(nsIContentViewer*)]. recent regression. While we saw this crash in beta 5 (presumably from upgrading from beta 4), it's much greater this release and happens at a different address. If timeless is right in that bug, it's a pretty easy fix. but we'd need to test with a round of RC1 -> RC2, to confirm its been fixed. | ||
;Accessibility [marcoz] | ;Accessibility [marcoz] | ||
* {{Bug|432970}} - Shutdown() of nsXULTooltipAccessible is not called. Affects Linux only, but can cause accessible tree corruption because tooltip accessibles from tabs that are already closed may still be around and accidentally accessed by the Orca screen reader. Again not a blocker, but a good candidate to tag along. | *'''[RC2?]'''{{Bug|432970}} - Shutdown() of nsXULTooltipAccessible is not called. Affects Linux only, but can cause accessible tree corruption because tooltip accessibles from tabs that are already closed may still be around and accidentally accessed by the Orca screen reader. Again not a blocker, but a good candidate to tag along. (Per [https://bugzilla.mozilla.org/show_bug.cgi?id=432970#c11 #c11], 2 related crashes) | ||
* {{Bug|434002}} - event show isn't fired for treecol accessible. This is an embarrassing oversight from review of fix for {{bug|413777}}. It basically means that event_show is never ever called for any accessible even if it needs to be. The most obvious use case we found isn't in Firefox but Thunderbird, when column | * {{Bug|434002}} - event show isn't fired for treecol accessible. This is an embarrassing oversight from review of fix for {{bug|413777}}. It basically means that event_show is never ever called for any accessible even if it needs to be. The most obvious use case we found isn't in Firefox but Thunderbird, when column | ||
* {{Bug|432467}} - firefox segfaults in plone kupu editor [@ nsDocAccessible::FlushPendingEvents]. This is a crasher reported by the RedHat folks that indicates a race condition between two things trying to release the same accessible. See comment #4 for the description. Assessment of risk is also in the bug. I wouldn't respin for this, but if it could tag along if RC2 is being done anyway, that would be very good I think. This can happen with other ajax-enabled stuff as well. | * {{Bug|432467}} - firefox segfaults in plone kupu editor [@ nsDocAccessible::FlushPendingEvents]. This is a crasher reported by the RedHat folks that indicates a race condition between two things trying to release the same accessible. See comment #4 for the description. Assessment of risk is also in the bug. I wouldn't respin for this, but if it could tag along if RC2 is being done anyway, that would be very good I think. This can happen with other ajax-enabled stuff as well. | ||