review of Navigation Timing's use of Web IDL

I gave myself ACTION-7 to review Navigation Timing’s use of Web IDL,
which I give here.

The spec has

  [Supplemental]
  interface Window {
    attribute Performance performance;
  };

but as plh pointed out, [Supplemental] is not (yet) defined in Web IDL.
I would recommend writing this as:

  [NoInterfaceObject]
  interface WindowPerformance {
    readonly attribute Performance performance;
  };

  Window implements WindowPerformance;

which has the desired effect using existing functionality in Web IDL.
(I think the attribute should be read only, too, if it doesn’t make
sense to be able to assign to window.performance.)

How mixin interfaces like WindowPerformance are written and handled in
Web IDL may change in the near future, which would you mean you’d write
it something like

  mixin interface WindowPerformance {
    readonly attribute Performance performance;
  };

  Window implements WindowPerformance;

but this wouldn’t have any practical effects on what you are aiming for
(i.e., a property named performance existing on the Window object).

I didn’t see any other issues.

-- 
Cameron McCormack ≝ http://mcc.id.au/

Received on Thursday, 17 March 2011 22:46:35 UTC