Live data from Hacker News

Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

chromestory.com

21–30 of 332 posts

Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

#21
I'd like this for PDFs. Often I want to share a PDF opened at a specific text. You can create a pdf url which jumps to a certain page. You can even link to a search for a certain word (single word).

But I can't link to a search phrase in a PDF. For some reason, they implemented searching for single words, but not phrases.

Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

#22
post #9

Very significant limitation: it only links to the first instance of the target text. What is the expected behavior if you highlight a second instance of some target text and try to create a link to it? It’s bad that the spec doesn’t discuss it. I can see this happening with short selections, like linking to a single word. Seems like this could use more thought.

They could add and index too, but linking to a search phrase is already prone to breakage if the text changes, so there's not much point in complicating it.

Usually the same phrase is not repeated in the text if you select more than 1-2 words.

Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

#23
post #17
post #14

It seems like more and more, Google is leveraging their near-monopoly on web browsing to just skip the proposal process and do whatever they want without discussion.

in this case it looked OK > Though existing HTML support for id and name attributes specifies the target element directly in the fragment, most other mime types make use of this x=y pattern in the fragment, such as Media Fragments (e.g. #track=audio&t=10,20), PDF (e.g. #page=12) or CSV (e.g. #row=4). fragments is already there but most pages do not have a clickable ID attribute. If Chrome could automatically provide…

IE 5 was also welcomed with joy when it arrived.

Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

#24
post #17
post #14

It seems like more and more, Google is leveraging their near-monopoly on web browsing to just skip the proposal process and do whatever they want without discussion.

in this case it looked OK > Though existing HTML support for id and name attributes specifies the target element directly in the fragment, most other mime types make use of this x=y pattern in the fragment, such as Media Fragments (e.g. #track=audio&t=10,20), PDF (e.g. #page=12) or CSV (e.g. #row=4). fragments is already there but most pages do not have a clickable ID attribute. If Chrome could automatically provide…

> in this case it looked OK

That’s not really the point

Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

#29
post #13
post #9

Very significant limitation: it only links to the first instance of the target text. What is the expected behavior if you highlight a second instance of some target text and try to create a link to it? It’s bad that the spec doesn’t discuss it. I can see this happening with short selections, like linking to a single word. Seems like this could use more thought.

Doesn’t the spec specify, that the link points to the first instance of the selected text? Does that not accurately define what happens when you try to link to a latter instance: It links to the first one.

This isn't a question about where the browser will scroll. This is a question about what will the browser do if the user tries to create a link to something that can't be scrolled to.

Re: Chrome will Soon Let You Share Links to a Specific Word or Sentence on a Page

#30
post #13
post #9

Very significant limitation: it only links to the first instance of the target text. What is the expected behavior if you highlight a second instance of some target text and try to create a link to it? It’s bad that the spec doesn’t discuss it. I can see this happening with short selections, like linking to a single word. Seems like this could use more thought.

Doesn’t the spec specify, that the link points to the first instance of the selected text? Does that not accurately define what happens when you try to link to a latter instance: It links to the first one.

That's not great from a UX point of view - for most users, their experience with the feature will be trying to use it, selecting a phrase, and having it silently link to an entirely different area.
Post reply on HN