<story><title>Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page</title><url>https://www.chromestory.com/2019/02/chrome-scroll-to-text/</url></story><parent_chain><item><author>ru999gol</author><text>I&amp;#x27;m so glad that google just sometimes ignores W3C&amp;#x27;s horrible  design-by-committe nonsense. Its the same reason XHTML failed.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    #selector(type=TextQuoteSelector,exact=foo)
&lt;/code&gt;&lt;/pre&gt;
vs.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    #targetText=foo
&lt;/code&gt;&lt;/pre&gt;
&amp;#x2F;edited to be a more fair comparison</text></item><item><author>csarven</author><text>I would like to urge the browser developers&amp;#x2F;makers to adopt existing proposals which came through open consensus which do precisely cover the same use cases (and more!)&lt;p&gt;W3C Reference Note on Selectors and States:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;selectors-states&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;selectors-states&amp;#x2F;&lt;/a&gt;&lt;p&gt;It is part of the suite of specs that came through the W3C Web Annotation Working Group:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;annotation&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;annotation&amp;#x2F;&lt;/a&gt;&lt;p&gt;More examples in W3C Note Embedding Web Annotations in HTML:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;annotation-html&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;annotation-html&amp;#x2F;&lt;/a&gt;&lt;p&gt;Different kinds of Web resources can combine multiple selectors and states. Here is a simple one using `TextQuoteSelector` handled by the &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;dokie.li&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;dokie.li&amp;#x2F;&lt;/a&gt; clientside application:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelector,prefix=ed%2C%20browser-based%20authoring%20and%20,exact=annotation,suffix=%20platform%20with%20built-in%20support%20)&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelecto...&lt;/a&gt;&lt;p&gt;A screenshot&amp;#x2F;how-to:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;csarven&amp;#x2F;status&amp;#x2F;981924087843950595&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;csarven&amp;#x2F;status&amp;#x2F;981924087843950595&lt;/a&gt;</text></item></parent_chain><comment><author>csarven</author><text>I urge you to dig a little deeper and see why things like `prefix`, `exact`, `suffix` exists in that particular example:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;selectors-states&amp;#x2F;#TextQuoteSelector_def&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;selectors-states&amp;#x2F;#TextQuoteSelector_de...&lt;/a&gt;&lt;p&gt;Please note that you&amp;#x27;ve actually changed the example!&lt;p&gt;If you just want to include `exact` or &amp;quot;targetText&amp;quot;, you can still do:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelector,prefix=,exact=annotation,suffix=)&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelecto...&lt;/a&gt;&lt;p&gt;or equivalent:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelector,exact=annotation)&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelecto...&lt;/a&gt;&lt;p&gt;but that selects all instances of the text &amp;quot;annotation&amp;quot; in the document. Which is precisely why we need `prefix` and `suffix` to be able to identify the actual selection that the user made.&lt;p&gt;So, here is the equivalent of your example:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelector,exact=browser-based%20authoring%20and%20annotation%20platform%20with%20built-in%20support)&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelecto...&lt;/a&gt;&lt;p&gt;I hope that clarifies.&lt;p&gt;This is just tip of the iceberg! Let&amp;#x27;s stick to fair comparison and consider extensibility.</text></comment>
<story><title>Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page</title><url>https://www.chromestory.com/2019/02/chrome-scroll-to-text/</url></story><parent_chain><item><author>ru999gol</author><text>I&amp;#x27;m so glad that google just sometimes ignores W3C&amp;#x27;s horrible  design-by-committe nonsense. Its the same reason XHTML failed.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    #selector(type=TextQuoteSelector,exact=foo)
&lt;/code&gt;&lt;/pre&gt;
vs.&lt;p&gt;&lt;pre&gt;&lt;code&gt;    #targetText=foo
&lt;/code&gt;&lt;/pre&gt;
&amp;#x2F;edited to be a more fair comparison</text></item><item><author>csarven</author><text>I would like to urge the browser developers&amp;#x2F;makers to adopt existing proposals which came through open consensus which do precisely cover the same use cases (and more!)&lt;p&gt;W3C Reference Note on Selectors and States:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;selectors-states&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;selectors-states&amp;#x2F;&lt;/a&gt;&lt;p&gt;It is part of the suite of specs that came through the W3C Web Annotation Working Group:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;annotation&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;annotation&amp;#x2F;&lt;/a&gt;&lt;p&gt;More examples in W3C Note Embedding Web Annotations in HTML:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;annotation-html&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.w3.org&amp;#x2F;TR&amp;#x2F;annotation-html&amp;#x2F;&lt;/a&gt;&lt;p&gt;Different kinds of Web resources can combine multiple selectors and states. Here is a simple one using `TextQuoteSelector` handled by the &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;dokie.li&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;dokie.li&amp;#x2F;&lt;/a&gt; clientside application:&lt;p&gt;&lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelector,prefix=ed%2C%20browser-based%20authoring%20and%20,exact=annotation,suffix=%20platform%20with%20built-in%20support%20)&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;csarven.ca&amp;#x2F;dokieli-rww#selector(type=TextQuoteSelecto...&lt;/a&gt;&lt;p&gt;A screenshot&amp;#x2F;how-to:
&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;csarven&amp;#x2F;status&amp;#x2F;981924087843950595&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;csarven&amp;#x2F;status&amp;#x2F;981924087843950595&lt;/a&gt;</text></item></parent_chain><comment><author>raimue</author><text>The W3C design seems to be extensible for future use cases with a consistent syntax while keeping everything under one keyword. Something like this could also be applied to other types of documents, not only to text. Let&amp;#x27;s say to quickly draw a highlight on an image or specify a page in a PDF document. While &amp;quot;#targetText=&amp;quot; is simple, it is not a generic solution.</text></comment>