LGTM3 On Monday, July 20, 2026 at 12:51:46 PM UTC-4 [email protected] wrote:
> LGTM2 > > On Monday, July 13, 2026 at 11:35:54 AM UTC-7 [email protected] wrote: > >> LGTM1 on the condition that we have histograms along with UKMs for this. >> Bugs are going to be gnarly to find, so understanding where/how this >> happens in the field will be critical. Would also encourage integration >> with the Reporting API and perhaps marking these in some way that is >> visible in the Performance Timeline, but those are non-blocking. >> >> On Thursday, July 9, 2026 at 3:25:08 AM UTC-7 Anna Sato wrote: >> > On Thursday, July 9, 2026 at 7:08:10 PM UTC+9 Yoav Weiss wrote: >>> >>> What happens with POSTs? E.g. The user clicked twice on a "submit" button >>> >>> This feature does not affect POST requests. To be considered a duplicate >>> and ignored, both navigations must be GET requests with no form data. >>> >>> You can find the proposed criteria in the github issue here: >>> https://github.com/whatwg/html/issues/11743#:~:text=The%20navigations%20are%20both%20GET%2C%20no%20form%20data >>> >> On Thu, Jul 9, 2026 at 4:24 AM Anna Sato <[email protected]> wrote: >>> >>> On Thursday, July 9, 2026 at 12:26:14 AM UTC+9 Alex Russell wrote: >>> >>> Presumably this will not impact cases where users cancel navigation (via >>> the "x") and then navigate again, either by reload or re-issuance of the >>> first navigation? >>> >>> Yes. This optimization only applies when there is an ongoing navigation >>> to preserve. >>> >>> >>> On Monday, July 6, 2026 at 7:34:00 AM UTC-7 Anna Sato wrote: >>> >>> Am I right to assume that this is only web observable on the server? >>> >>> You are correct; this is primarily observable on the server side, as >>> duplicate requests that would previously have been sent will now be ignored >>> before being sent to the server. >>> >>> >>> Did we get any feedback on the PR? >>> >>> We have added reviews to the PR and pinged the relevant individuals to >>> move that forward. >>> >>> >>> Could we write WPTs for this feature? >>> >>> We currently only have browser tests for this feature. In Chromium, we >>> disable this feature during automated testing to ensure it does not >>> interfere with rapid programmatic navigations in existing test suites. >>> However, we believe writing WPTs is possible, and I have filed a bug to >>> track this work for the future: https://issues.chromium.org/is >>> sues/530823824. >>> >>> Thanks, >>> Anna >>> >>> On Fri, Jul 3, 2026 at 5:42 PM Yoav Weiss (@Shopify) < >>> [email protected]> wrote: >>> >>> Am I right to assume that this is only web observable on the server? >>> >>> On Fri, Jul 3, 2026 at 10:15 AM Chromestatus < >>> [email protected]> wrote: >>> >>> *Contact emails* >>> [email protected], [email protected] >>> >>> >>> >>> *Explainer* >>> *No information provided* >>> >>> *Specification* >>> https://github.com/whatwg/html/pull/11765 >>> >>> >>> Did we get any feedback on the PR? >>> >>> >>> >>> *Summary* >>> Prevents an ongoing navigation from being unnecessarily canceled by a >>> new, identical navigation that is initiated in quick succession. This >>> optimization improves performance and the user experience by not wasting >>> resources on a duplicate request, which can be caused by accidental >>> double-clicks. >>> >>> *Blink component* >>> UI>Browser>Navigation >>> <https://issues.chromium.org/issues?q=customfield1222907:%22UI%3EBrowser%3ENavigation%22> >>> >>> *Web Feature ID* >>> Missing feature >>> >>> *Motivation* >>> We observe users sometimes navigate to the same URL in quick succession, >>> likely by accident. Because new navigations take precedent over an older >>> one, this means it will waste the earlier navigation that's already in >>> progress, potentially wasting a response that is already in flight for the >>> navigation and causing the user to wait longer (from the time the first >>> navigation kicks off). To mitigate this waste, the feature will ignore the >>> duplicate navigation and let the first navigation continue. >>> >>> *Initial public proposal* >>> https://github.com/whatwg/html/issues/11743 >>> >>> *TAG review* >>> https://github.com/w3ctag/design-reviews/issues/1240 >>> >>> *TAG review status* >>> Issues open >>> >>> *Goals for experimentation* >>> We have already conducted experimentation which showed positive results >>> in reducing duplicate queries sent to servers. >>> >>> *Risks* >>> >>> >>> *Interoperability and Compatibility* >>> The user-facing behavior will remain identical, as we only target >>> duplicate navigations under specific conditions, such as same URLs and >>> close start times. One minor change to web-exposed behavior is that the >>> initial navigation is now maintained instead of being replaced by the >>> subsequent duplicate request. >>> >>> *Gecko*: No signal (https://github.com/mozilla/standards-positions/issue >>> s/1307) >>> >>> *WebKit*: No signal (https://github.com/Web >>> Kit/standards-positions/issues/563) >>> >>> *Web developers*: No signals >>> >>> *Other signals*: >>> >>> *Ergonomics* >>> N/A >>> >>> *Activation* >>> N/A >>> >>> *Security* >>> The feature prevents cross-site leak risks by ensuring that an initiator >>> document cannot detect or infer cookie changes made by other documents. No >>> cross-site state information is ever exposed during the duplicate >>> navigation check. >>> >>> *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? >>> To minimize compatibility risks, navigation callbacks and history >>> entries preserve their legacy behavior, preventing application breakage. >>> >>> >>> *Debuggability* >>> N/A >>> >>> *Will this feature be supported on all six Blink platforms (Windows, >>> Mac, Linux, ChromeOS, Android, and Android WebView)?* >>> Yes >>> We are currently rolling out this feature on WebView. On other >>> platforms, the experiment has already concluded and we are shipping it. >>> >>> *Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >>> No >>> >>> >>> Could we write WPTs for this feature? >>> >>> >>> >>> >>> >>> *Flag name on about://flags* >>> *No information provided* >>> >>> *Finch feature name* >>> IgnoreDuplicateNavs >>> >>> *Rollout plan* >>> Will ship enabled for all users >>> >>> *Requires code in //chrome?* >>> False >>> >>> *Tracking bug* >>> https://crbug.com/366060351 >>> >>> *Launch bug* >>> https://launch.corp.google.com/launch/4428715 >>> >>> *Availability expectation* >>> Feature is available only in Chromium browsers. It is not clear if/when >>> other browsers will follow. >>> >>> *Adoption expectation* >>> Feature is considered a best practice for some use case within 12 months >>> of reaching Web Platform baseline. >>> >>> *Non-OSS dependencies* >>> >>> Does the feature depend on any code or APIs outside the Chromium open >>> source repository and its open-source dependencies to function? >>> No. >>> >>> *Estimated milestones* >>> Shipping on desktop151 Shipping on Android151 Shipping on iOS151 >>> >>> *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). >>> Standard criteria for duplicate navigations are being finalized within >>> the WHATWG HTML specification. >>> >>> *Link to entry on the Chrome Platform Status* >>> https://chromestatus.com/feature/5137490012930048?gate=6446755898064896 >>> >>> 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 [email protected]. >>> To view this discussion visit https://groups.google.com/a/ch >>> romium.org/d/msgid/blink-dev/6a476fa6.198129d7.1d0cd0.0224.G >>> AE%40google.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a476fa6.198129d7.1d0cd0.0224.GAE%40google.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 [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6e0ad350-0dc3-402c-98c8-36ff6f13dc09n%40chromium.org.
