Closed Bug 141397 Opened 22 years ago Closed 12 years ago
Ensure Mozilla extensions begin with -moz-
This is intended to be a semipermanent bug that gets dealt with every few milestones but never gets marked fixed. It is, in a sense, a continuation of bug 3935. We should continue to audit the CSS properties, values, units, pseudo-classes, and pseudo-elements that Mozilla supports to make sure that all extensions begin with -moz-, and to ensure that properties that we don't support correctly are disabled or changed to -moz-. Given more testing or the stabilization of CSS3 drafts (to CR, or perhaps late-stage WD if they're known to be stable), we can also start adding support for non -moz-ed keywords back in (e.g., 'inline-table' and 'inline-block', if they're tested and bugs are fixed). We can add this easily for keywords while keeping the -moz- support by duplicating keywords in nsCSSProps.cpp (with care as to the order). I'd need to look at how to do it for properties, but I think it can be done without too much difficulty. The current issues I can think of off the top of my head, from bug 3935, are that we support a bunch of CSS3 selectors and 'text-align: start', and also support one unit without -moz- (I think 'ch').
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → mozilla1.1beta
Target Milestone: mozilla1.1beta → mozilla1.2alpha
Are there any cases still in need of fixing that we know of?
I just noticed :first-node and :last-node.
Whiteboard: [whitebox] → [whitebox][patch]
Target Milestone: mozilla1.2alpha → mozilla1.7final
Comment on attachment 145508 [details] [diff] [review] patch for :first-node and :last-node (checked in to trunk, 2004-04-07 16:25 -0700) r+sr=bzbarsky
Comment on attachment 145508 [details] [diff] [review] patch for :first-node and :last-node (checked in to trunk, 2004-04-07 16:25 -0700) This should have been fixed as part of a Mozilla1.0 blocker (bug 3935).
Attachment #145508 - Flags: approval1.7?
Comment on attachment 145508 [details] [diff] [review] patch for :first-node and :last-node (checked in to trunk, 2004-04-07 16:25 -0700) a=chofmann for 1.7
Attachment #145508 - Flags: approval1.7? → approval1.7+
shouldn't this bug be marked as RESOLVED FIXED?
I think having a bug open on this is no longer useful. I think we've been pretty good about ensuring this as part of the review process.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.