Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
Technical question, apart from the (valid IMO) political arguments: Google&#x27;s idea to implement this is to append the text fragment to the URL in a &quot;#targetText&quot; pseudo-query-argument in the URL fragment part. This sounds like it would extremely easily break existing web pages who use the fragment part for their own state.<p>In the blog post, there doesn&#x27;t seem to be anything addressing this (or even just specifying how Chrome would combine the &quot;targetText&quot; fragment with an already existing fragment part)<p>Did they spend any thought on this?<p>Edit: Oh, right, the readme answers this:<p>&gt; <i>Web pages could potentially be using the fragment to store parameters, e.g. <a href="http:&#x2F;&#x2F;example.com&#x2F;#name=test" rel="nofollow">http:&#x2F;&#x2F;example.com&#x2F;#name=test</a>. If sites are already using targetText in the URL fragment for their own purposes, this feature could break those sites.</i><p>&gt; <i>We expect this usage to be exceedingly rare. It&#x27;s an abuse of the purpose of URL fragments and page arguments are typically encoded using the &#x27;?&#x27; character (e.g. <a href="http:&#x2F;&#x2F;example.com?name=test" rel="nofollow">http:&#x2F;&#x2F;example.com?name=test</a>). Still, we may run an experiment to see if targetText is available enough to use as a reserved token.</i><p>We&#x27;ll just completely change the commonly understand processing model of fragment identifiers, but it&#x27;ll be fine since we don&#x27;t think anyone is using them anyway...<p>No further questions...