Track PR #323

[tobie]

Following PR #323, file issues with:

• Rendering engines:
  • Gecko (https://bugzilla.mozilla.org/show_bug.cgi?id=1375829)
  • WebKit (https://bugs.webkit.org/show_bug.cgi?id=173767)
  • Chromium (https://bugs.chromium.org/p/chromium/issues/detail?id=736332)
  • Edge (https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12458893/)
• Testing:
  • web-platform-tests (Default to json operation web-platform-tests/wpt#6246)
  • idlharness.js (Default to json operation web-platform-tests/wpt#6246)
• Parsers:
  • widlparser (Remove serializer-related productions plinss/widlparser#25)
  • WebIDL parser (Remove serializer-related productions w3c/webidl2.js#73)
• Related specs:
  • PushSubscription (custom) in Push (WebIDL serializer has been deprecated in favor of toJSON operation w3c/push-api#266)
  • MediaDeviceInfo (own attributes) in Media Capture and Streams (WebIDL serializer has been deprecated in favor of toJSON operation w3c/mediacapture-main#469)
  • Performance (own attributes) in High Resolution Time Level 3 (WebIDL serializer has been deprecated in favor of toJSON operation w3c/hr-time#49)
  • PerformanceEntry (own attributes) in Performance Timeline Level 2 (WebIDL serializer has been deprecated in favor of toJSON operation w3c/performance-timeline#82)
  • PerformanceResourceTiming (own and inherited attributes) in Resource Timing Level 3 (WebIDL serializer has been deprecated in favor of toJSON operation w3c/resource-timing#112)
  • PerformanceNavigation (own attributes) in Navigation Timing Level 2 (WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72)
  • PerformanceTiming (own attributes) in Navigation Timing Level 2 (WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72)
  • PerformanceNavigationTiming (own and inherited attributes) in Navigation Timing Level 2 (WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72)
  • RTCSessionDescription (own attributes) in WebRTC 1.0: Real-time Communication Between Browsers (WebIDL serializer has been deprecated in favor of toJSON operation w3c/webrtc-pc#1419)
  • RTCIceCandidate (custom) in WebRTC 1.0: Real-time Communication Between Browsers (WebIDL serializer has been deprecated in favor of toJSON operation w3c/webrtc-pc#1419)
  • PaymentAddress (own attributes) in Payment Request API (WebIDL serializer has been deprecated in favor of toJSON operation w3c/payment-request#555)
  • PaymentResponse (own attributes) in Payment Request API (WebIDL serializer has been deprecated in favor of toJSON operation w3c/payment-request#555)
  • DOMPointReadOnly (own attributes) in Geometry Interfaces Module ([geometry] WebIDL serializer has been deprecated in favor of toJSON operation w3c/fxtf-drafts#200)
  • DOMRectReadOnly (own attributes) in Geometry Interfaces Module ([geometry] WebIDL serializer has been deprecated in favor of toJSON operation w3c/fxtf-drafts#200)
  • DOMQuad (own attributes) in Geometry Interfaces Module ([geometry] WebIDL serializer has been deprecated in favor of toJSON operation w3c/fxtf-drafts#200)
  • DOMMatrixReadOnly (own attributes) in Geometry Interfaces Module ([geometry] WebIDL serializer has been deprecated in favor of toJSON operation w3c/fxtf-drafts#200)
    Additionally, tracking [geometry] JSON serialization of a DOMRectList w3c/fxtf-drafts#199.

[tobie]

All issues filed; closing.

[domenic]

What about the parsers? They should start rejecting serializer syntax, and accepting toJSON if they don't already.

[tobie]

So the parsers already accept toJSON as it's just a regular operation (usage wasn't blocked at the grammar level). But you're right that they can get rid of lots of code now that serializers are removed. I hadn't thought about that. :)

[tobie]

Also filed bugs with vendors and test suites. Think I'm done this time.