Earlier quoted context omitted.
Aren't url fragment originally used for page position already? Like url.com/#title would scroll to the page the div with id "title"? In that case I don't feel like using url fragment for a word position is so much breaking it, it keeps the use of url fragment for info about page position, right?
Yes but this is about namespacing/syntax and likelihood of clashes. Normally, url fragments were intended to be used by page authors , making clashes impossible (page author controls both page and anchor syntax). Google are breaking this contract, but argue that the fact that they're using parameter-style syntax should not clash with author usage, because using parameter-style syntax is "an abuse" of the feature.
Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
321–330 of 332 posts
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#322Technical question, apart from the (valid IMO) political arguments: Google's idea to implement this is to append the text fragment to the URL in a "#targetText" 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. In the blog post, there doesn't seem to be anything addressing this (or even just specifying how…
Feature author here. I'd like to first clarify that this is still in the super-early stage of development; none of this is shipped or finalized yet. The feature hasn't even requested approval to ship at which point these kinds of issues would be brought up. We take web-compat very seriously. If this breaks even a small percentage of pages, it won't ship. Part of the shipping process is ensuring we have at least a dra…
You can claim to have high standards, but Google is trying to dictate the future of the web.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#323Earlier quoted context omitted.
Actually, it seems like the you click on Google Search has the right href (which is what appears on the status text) but it also has a ping attribute to it for tracking. https://www.w3schools.com/tags/att_a_ping.asp
I'm surprised there is not a chrome extension to remove these.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#324Technical question, apart from the (valid IMO) political arguments: Google's idea to implement this is to append the text fragment to the URL in a "#targetText" 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. In the blog post, there doesn't seem to be anything addressing this (or even just specifying how…
Feature author here. I'd like to first clarify that this is still in the super-early stage of development; none of this is shipped or finalized yet. The feature hasn't even requested approval to ship at which point these kinds of issues would be brought up. We take web-compat very seriously. If this breaks even a small percentage of pages, it won't ship. Part of the shipping process is ensuring we have at least a dra…
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#325Earlier quoted context omitted.
Nobody cares, really, except for a percent fringe users of a percent of Google users. On a more general point, once again Google Search is provided to you for free. If you don't want to use it by their rules, you are entirely free to use Bing or Yahoo. Actually using the service regularly, because it is tailored to your workflow and provides value to you, while complaining that the tailored/value-adding part is drive…
I don't use Google, I use StartPage. I am plainly stating that I am surprised nobody made an extension to remove the ping= link attribute from all webpages, considering that the only reason it exists is to track user activity.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#326Earlier quoted context omitted.
It will. The specification process needs to be informed by implementation and experimentation. When implementing a feature we'll learn all sorts of things and hit bumps that will help guide the design. Once we have a working implementation, it helps to be able to use it to answer things like: - How does this perform on existing pages - How does this feel from a user perspective - How can I write pages that user this…
I feel like the actual, underlying issue worth bringing to the standards body is: how do we address arbitrary content on a web page, even when it moves around or changes over time? Aside from these neat Chrome links, this would enable some super interesting features, such as the ability to add persistent and shareable annotations to webpages.
Microsoft did this many moons ago. People ended up defacing web sites like the New York Times and spreading proto fake news.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#327I think I'll pass.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#328This feels just like when I discovered that one day Chrome just decided to use the canonical address of a page instead of the actual address, when sharing it, telling no one. These people are a plague on this world.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#329Maybe this is a step towards that goal.
Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page
#330Earlier quoted context omitted.
> new things that are constantly added By golly, that's the problem right there.
One thing I’ve discovered from learning and using Common Lisp seriously is that it’s really important for a system to be specified in a way that allows for extensions to the system to be implemented in terms of primitives the language provides (e.g. you want a new language construct, write a macro to transform your desired syntax into Common Lisp). In languages and systems that don’t have this feature, an implementat…
This is a bit of a misconception. One can still write Haskell98 whilst using a library that use a GHC-specific extension. The library doesn't (have to) force its consumers to use extensions too!