Open Bug 412326 Opened 18 years ago Updated 3 years ago

gtk: tab's label focus indicator should be drawn natively

Categories

(Firefox :: Shell Integration, defect)

Product:
Firefox
Component:
Shell Integration
Platform:
x86
Linux
Type:
defect

Tracking

()

People

(Reporter: u294409, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9b3pre) Gecko/2008011404 openSUSE/10.3 Minefield/3.0b3pre Build Identifier: Mozilla/5.0 (X11; U; Linux i686; pl; rv:1.9b3pre) Gecko/2008011404 openSUSE/10.3 Minefield/3.0b3pre tab's label has wrong focus indicator (not drawn by gtk). Reproducible: Always Actual Results: wrong focus indicator. Expected Results: everything ok.
Blocks: 265698
Version: unspecified → Trunk
ping!
Summary: gtk: tab's label has non-gtk focus → gtk: tab's label dotted focus indicator should be replaced by native gtk's focus indicator
Why still isn't it fixed?
Because the focus is different that with most other elements. Unlike buttons, which paint their focus based on the size of the button, the tab must paint the focus based on it's children. That means I either need to introduce a new element into each tab (which I am apprehensive about doing since it would affect all platforms) -or- I could have some hackish code in the painting to undo padding/borders in order to achieve the correct box. Besides, if you haven't noticed from all of the other bugs, we've been working on other things
I know, I know, but this one is especially ugly bug... Lets kill 'em all :D !
Summary: gtk: tab's label dotted focus indicator should be replaced by native gtk's focus indicator → gtk: tab's label focus indicator should be drawn natively
Accepting since I have this mostly done (technically all done, but trying to get some other tab improvements involved
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
d'oh, I duped my own bug... I completely forgot about it.
This is a mass change. Every comment has "assigned-to-new" in it. I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.