WebIDL serializer has been deprecated in favor of toJSON operation

[tobie]

Hi!

We recently deprecated WebIDL serializers. You can now directly specify toJSON operations instead, which you previously weren't allowed to do.

To deal with common cases, we added a new [Default] extended attribute which triggers the default toJSON operation that behaves similarly to how serializers={attributes} or serializers={attributes, inherit} used to. That is, it serializes all attributes that are of a JSON type into a vanilla JSON object.

It seems the following interfaces in this spec are impacted by this change:

• PerformanceNavigationTiming
• PerformanceTiming
• PerformanceNavigation

All of these seem good candidate for the default toJSON operation, so the below should be all you need, provided you also similarly update PerformanceResourceTiming and PerformanceEntry in their relevant specifications:

interface PerformanceNavigationTiming : PerformanceResourceTiming {
    readonly attribute DOMHighResTimeStamp unloadEventStart;
    // etc...
    [Default] object toJSON();
};

[Exposed=Window]
interface PerformanceTiming {
    readonly attribute unsigned long long navigationStart;
    // etc...
    [Default] object toJSON();
};

[Exposed=Window]
interface PerformanceNavigation {
    const unsigned short TYPE_NAVIGATE = 0;
    // etc...
    [Default] object toJSON();
};

I'm sorry for the inconvenience this causes, but our hope is that this ultimately makes things a lot simpler and clearer for everybody.

Please feel free to reach out if you have any questions.

Thanks!

[igrigorik]

@tobie ditto for this spec: w3c/resource-timing#112 (comment)

[tobie]

Yes, Respec got updated yesterday: w3c/respec#1300.

[igrigorik]

Resolved via #76