Closed Bug 463574 Opened 16 years ago Closed 15 years ago

repainting issues after using "all tabs"

Categories

(Core :: Web Painting, defect)

Product:
Core
Component:
Web Painting
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 469774

People

(Reporter: blassey, Unassigned)

References

Details

Attachments

(2 files)

screen shot
(deleted), image/png
Details
also effects find bar
(deleted), image/png
Details
Attached image screen shot (deleted) —
after using the "ctr-tab"-like replacement for the all-tabs drop down, there were a few painting problems.
Attached image also effects find bar (deleted) —
I've noticed that this only happens when I use the find bar of the ctrl-tabs screen.
Blocks: 436304
Component: Tabbed Browser → GFX
Product: Firefox → Core
QA Contact: tabbed.browser → general
Version: unspecified → Trunk
OS: Windows XP → All
Hardware: PC → All
Well, having it blocking a fixed bug isn't the best option. If all-tab will be included in Firefox 3.1 we should bind it to a currently open bug. And this is bug 465076. And it should be fixed for Firefox3.1. Asking for blocking.
Blocks: 465076
No longer blocks: 436304
Flags: blocking1.9.1?
(In reply to comment #3) > Well, having it blocking a fixed bug isn't the best option. It's the correct way to track issues that show up when a bug gets fixed.
So, bug 465076 is in fact orthogonal to this one. Restoring dependency.
Blocks: 436304
No longer blocks: 465076
Can you post some steps to reproduce?
Vlad, it should be reproducible with the try server build mentioned in bug 465076 comment 29. STR are in bug 465076 comment 38. I got it while testing on Vista.
control-tab was backed out for final, so taking this off the blocking list; but preemptively marking it blocking 1.9.2.
Blocks: 465076
Flags: blocking1.9.2+
Flags: blocking1.9.1?
Flags: blocking1.9.1-
Means ctrl-tab and all-tabs are the only core code snippets which could trigger such a repainting issue?
(In reply to comment #9) > Means ctrl-tab and all-tabs are the only core code snippets which could trigger > such a repainting issue? certainly not
They're not, and I'd be happy to look at a easier-to-reproduce testcase :p
vlad, bug 469774 has 100% reproducible steps for me on Mac, it that would help. Assuming that's the same bug, of course.
Blocks: 469774
Vlad, I remember a bug, which I've filed about a month ago for Ubiquity. Probably it could be based on the same issue. It should be reproducible on Windows. It's bug 463616.
Product: Core → Core Graveyard
Component: GFX → Layout: View Rendering
Product: Core Graveyard → Core
QA Contact: general → layout.view-rendering
No longer blocks: 469774
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Transferred blocking to bug 469774.
Flags: blocking1.9.2+
No longer blocks: 465076
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: