I think the direction of the influence would mostly works the other way round. If there&#x27;s an attribute on the HTML link tag that some browsers recognise as calling the browser&#x27;s client-side version of that library (with local&#x2F;CDN fallback for browsers that don&#x27;t) then users are going to notice that browser X seems to load a lot of websites more quickly than browser Y, which puts pressure on the vendor of browser Y to make sure it also supports these frequently-used js libraries (especially if they&#x27;re <i>large</i> frequently-used libraries with multiple minor version numbers and no widely-accepted-as-canonical CDN source)<p>This is still a shame if you&#x27;re maintaining a heavyweight alternative to jQuery or React which is far too obscure to be a consideration for browser vendors, but it&#x27;s a big boon for <i>users</i>, especially users on slow or metered connections that download several different version numbers of jQuery from several different CDNs every day.