Conversation
StaticRange.p.toRange isn’t part of any spec, so this change marks it non-standard. Related BCD change: mdn/browser-compat-data#10288
|
Per https://mdn-bcd-collector.appspot.com/tests/api/StaticRange/toRange this isn't actually in Chrome. Looks like it was removed in https://chromium.googlesource.com/chromium/src/+/e2b8278dd5aaf5a6ec415aa5e7dd828f17b644f6 and this entry should actually be removed entirely. |
StaticRange.p.toRange isn’t part of any spec, was only ever implemented in Chrome — but way back at Chrome 60. So this change removes it, per mdn#10288 (comment) Related MDN change: mdn/content#4723
2006f87 to
9469034
Compare
OK, I’ve amended the commit to remove it — as well as updating the PR description accordingly. |
foolip
left a comment
There was a problem hiding this comment.
https://developer.mozilla.org/en-US/docs/Web/API/StaticRange/toRange also needs to be removed, so approving but not merging, so this could go together with a MDN PR.
StaticRange.p.toRange isn’t part of any spec, and was only ever implemented in Chrome — but way back at Chrome 60. So this change removes it, per mdn/browser-compat-data#10288 (comment) Related BCD change: mdn/browser-compat-data#10288
OK, I’ve amended the mdn/content#4723 change to remove it completely from MDN. |
StaticRange.p.toRange isn’t part of any spec, and was only ever implemented in Chrome — but way back at Chrome 60. So this change removes it, per mdn/browser-compat-data#10288 (comment) Related BCD change: mdn/browser-compat-data#10288
StaticRange.p.toRangeisn’t part of any spec, was only ever implemented in Chrome — but way back at Chrome 60. So this change removes it, per #10288 (comment)Related MDN change: mdn/content#4723