Closed Bug 85276 Opened 23 years ago Closed 20 years ago

tracking - CSS issues

Categories

(Tech Evangelism Graveyard :: English US, defect)

Product:
Tech Evangelism Graveyard
Component:
English US
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: eric, Unassigned)

References

(
URL
)

Details

(Keywords: meta, Whiteboard: [TRACKING][STANDARDS][CSS] aok)

This is a tracking entry for CSS issues with Mozilla, reports of incorrect CSS, and related problems. More information will follow.
Whiteboard: [TRACKING][STANDARDS][CSS]
Depends on: 84464
Depends on: 45621
Depends on: 85088
bug 85088 is not about evangelism.
No longer depends on: 85088
No longer depends on: 45621
Håkan is correct, and I've removed all dependencies to bugs which are not in the evangelism component. Apologies for the mistake.
Depends on: 44567
Depends on: 77050
Depends on: 72183
Depends on: 79116
Depends on: 63541
Depends on: 32345
Depends on: 52421
Depends on: 59825
Depends on: 83646
Depends on: 57123
Depends on: 58745
Depends on: 66206
Depends on: 52556
Marking confirmed and meta.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: meta
reassigning to eric
Assignee: bclary → emeyer
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Summary: CSS issues → tracking - CSS issues
Whiteboard: [TRACKING][STANDARDS][CSS] → [TRACKING][STANDARDS][CSS] aok
tech evang june 2003 reorg
Assignee: emeyer → english-us
QA Contact: zach → english-us
Can this bug be closed now - all of the bugs are now resolved.
There are a lot of other bugs related to CSS but I do not think it is worth to have a tracking bug for them. Especially since the last useful comments of this bug go back to 2001. Marking FIXED.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.