340901 - sort out enum nsDOMClassInfoID frozenness

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

The frozenness of the enum values in enum nsDOMClassInfoID is sort of a mess.  A whole bunch changed between 1.7 and 1.8 because stuff got added in the middle.  And the branch landings for 1.8.1 are creating a bit of a mess; things are ending up in a different order on branch and trunk.

If we want this to be frozen (for whom?  It's frozen, but why do we care?), we need to have big comments that say:

/******** IDs above this line are frozen as of Mozilla 1.8 ********/

/******** IDs above this line are frozen as of Mozilla 1.8.1 ********/

etc.  And there might have been some insertion-in-the-middle between 1.8 and 1.8.1, which we should fix before 1.8.1 ships.

(It might also be nice to get rid of the on-by-default ifdefs above those lines, but that's another issue.  Sort of.)

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I talked to jst about this on Friday and he thought we should give up on the idea that these IDs are frozen.

Comment 2

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Clearing blocking1.8.1 on that basis.

Comment 3

[Boris Zbarsky [:bzbarsky]]

nsDOMClassInfoID is gone as of bug 1442039, so I claim this is sorted out.