er sorry, I think Sunil's away for a bit. But I see Chromium engineer titouan has an account here on bugzilla and worked on the chromium code that I linked in comment 45, based on the blame UI shown on the page there -- hi titouan! Do you know if actually Chrome treats `198.18.*.*` as loopback addresses as [the spec seems to say it should](https://wicg.github.io/local-network-access/#non-public-ip-address-blocks) ? (If not, do you know if that spec-vs-implementation difference is know, and is that gap planned to be closed in one direction or the other?)
Bug 1980302 Comment 46 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
er sorry, I think Sunil's away for a bit. But I see Chromium engineer titouan has an account here on bugzilla and worked on the chromium code that I linked in comment 45, based on the blame UI shown on the page there -- hi titouan! Do you know if actually Chrome treats `198.18.*.*` as loopback addresses as [the spec seems to say it should](https://wicg.github.io/local-network-access/#non-public-ip-address-blocks) ? (If not, do you know if that spec-vs-implementation difference is known, and is that gap planned to be closed in one direction or the other?)