Closed Bug 3482 Opened 26 years ago Closed 26 years ago

CSS CLASSES don't work in XUL documents

Categories

(Core Graveyard :: Tracking, defect, P2)

Product:
Core Graveyard
Component:
Tracking
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: law, Assigned: hyatt)

Details

(Whiteboard: RN:M3)

Style classes don't seem to take effect in XUL documents so I am forced to use inline styles. That works pretty well, but I'd much prefer the reusability of style classes. We can use this bug to make sure we don't forget about fixing this.
QA Contact: 3853 → 3849
Whiteboard: RN:M3
Target Milestone: M4
Can Release Note for M3. Setting to M4.
QA Contact: 3849 → 4015
setting Gerardo as QA contact
Status: NEW → ASSIGNED
Summary: style classes don't work in XUL documents → CSS CLASSES don't work in XUL documents
Target Milestone: M4 → M5
moving to m5
This bug has been fixed. It was delightfully trivial. I just forgot to call a function that was already written and working correctly. I can't check in until the tree opens I guess, so right now I'm still holding on to the fix on my machine. This might be a good candidate to slip into M4 though. It's safe.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Fixed and checked in.
Fixed and checked in.
Moving all Apprunner bugs past and present to Other component temporarily whilst don and I set correct component. Apprunner component will be deleted/retired shortly.
Bill, can you help us verify this bug? If you agree the resolution is correct, please mark it as Verified. Thanks!
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.