Hey! > to ensure Mozilla is aware this happening?
I am filing an issue for this > What can you say about usage in the wild here? In regards to this I believe no more data was collected, one example of usage where two arguments may be used was pointed out here https://github.com/whatwg/url/pull/735#issuecomment-1397898382 other than this I havent been able to come up with another example maybe it is possible to collect data on the type of argument being used in those sites? is that possible and would that be helpful here? On Friday, May 12, 2023 at 2:09:21 PM UTC+5:30 Philip Jägenstedt wrote: > It looks like this was spec'd in https://github.com/whatwg/url/pull/735, > with participation from Chromium and WebKit folks. > https://bugzilla.mozilla.org/show_bug.cgi?id=1831587 was filed for Gecko, > but there's no clear position. Would you mind filing an issue at > https://github.com/mozilla/standards-positions/issues/new to ensure > Mozilla is aware this happening? > > https://chromestatus.com/metrics/feature/timeline/popularity/4478 is > pretty low, but was any analysis done of sites that reach this use counter? > It's honestly higher usage than I'd expect for an argument that didn't do > anything before, so likely the value passed doesn't make sense and will > result in the parameter not being deleted for delete(), which could be a > problem. What can you say about usage in the wild here? > > +Andreu Botella > > On Fri, May 12, 2023 at 9:30 AM Debadree Chatterjee <debad...@gmail.com> > wrote: > >> Contact emailsdebad...@gmail.com >> >> ExplainerNone >> >> Specificationhttps://url.spec.whatwg.org/#dom-urlsearchparams-has >> >> Summary >> >> This feature adds the ability to pass a `value` argument to >> URLSearchParams's has() and delete() methods which allow for deleting >> tuples stored in URLSearchParams either by the `name` parameter or by the >> combination of `name` and `value` >> >> >> Blink componentBlink >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink> >> >> TAG reviewNone >> >> TAG review statusNot applicable >> >> Risks >> >> >> Interoperability and Compatibility >> >> Compatibility with existing websites were tested by means of a Counter in >> chromium, ref: >> https://github.com/whatwg/url/pull/735#issuecomment-1441503315 and no >> significant chances of breaking were found >> >> *Gecko*: No signal >> >> *WebKit*: No signal >> >> *Web developers*: Has Shipped ( >> https://github.com/WebKit/WebKit/pull/13500) >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None expected >> >> >> Debuggability >> >> None >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)? >> Yes >> >> Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >> ? >> Yes >> >> Flag name >> >> Requires code in //chrome?False >> >> Tracking bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1442916 >> >> Estimated milestones >> >> No milestones specified >> >> >> Anticipated spec changes >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> None Expected >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5147732899004416 >> >> Links to previous Intent discussionsIntent to prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CFBE060E-9D1C-4B8D-A4FB-B0279D73E6F4%40gmail.com >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com/>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to blink-dev+...@chromium.org. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/A73025EA-70D7-4818-9CFF-AE14B48875F0%40gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/A73025EA-70D7-4818-9CFF-AE14B48875F0%40gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6adac07b-7eae-42cf-ba66-d25e1f9446a5n%40chromium.org.
