Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

chromestory.com

Post reply on HN
Print view View original

121–130 of 332 posts

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

#121

Post by dmurray »

gcb0 wrote: post #80

Real use case for this is so Google can poke into context for links shared via services they have no ownership. They got used to know exactly what people share and, much more importantly, what people click on email, thanks to gmail rewriting all links to a google track url (while misleading the user by a fake status text on mouse over). When they sum the info of 1. who send it, 2. who clicked on it, 3. what was the e…

> Or, we could just go with occam's razor and believe that a bunch of bored engineers at google decided to simply add a feature completely disconnected from any of their business plans

I understand the skepticism about Google's motivations but "making Chrome better and more feature rich so people will want to use it" is completely in line with Google's business plans.

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

#122

Post by sascha_sl »

xg15 wrote: post #109

Technical 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…

Hmm, who provided the first popular JS framework that used fragments for navigation again?

I think it was called "Angular".

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

#123

Post by leeoniya »

mstade wrote: post #77
leeoniya wrote: post #67

Earlier quoted context omitted.

> (Believe it or not, I still see new projects use this over the history API!) want to guess which one doesnt need JS, or server-side handling to work?

I think maybe you're misunderstanding what I meant by fragment based navigation – that's probably my fault. I refer to the shebang style fragments, that was used to implement deep linking in primarily JS driven sites. This of course watered down the use of fragments in pages, and nearly made them useless frankly. Ironically, the history API – which of course as you say requires JS to work – is what probably saved fra…

the issue is that your server now needs to somehow understand which part of the path is the "fragment" without any distinguishing characters by which to parse it out of the url.

if the server now sees deep urls like `/products/patagonia/parkas`, how does it know which part is the fragment? is it /parkas or /patagonia/parkas? what if you have urls that are not completely uniform? or have different uniformity at different prefixes?

the router needs to be more complex. but i agree that the history API has advantages over shebangs for deep app links.

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

#125

Post by sametmax »

sverhagen wrote: post #48
dannyr wrote: post #35

Earlier quoted context omitted.

I agree with you on Google's monopoly but imagine if every browser has to go through proposal process to release any feature? Everything will just stagnate. Browsers copy features from each other. If this is a useful feature, it would make its way to other browsers pretty soon.

It's not just a browser feature, now is it, it's an interoperability feature since you're supposed to share links (it's in the title). This means that the near-monopoly is going to drive people who receive the shared link to consider using the browser that supports this. That puts other browsers quite on the defense, does it not?

"Your link doesn't work with firefox" sounds indeed really bad.

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

#126

Post by Slartie »

sascha_sl wrote: post #124

Everyone in this thread needs to put their money where their mouth is and go back to Firefox if they're currently using Chrome.

Did exactly this, a few weeks ago. Was heavy Chrome user, now fully on Firefox (and Safari on mobile). I am so satisfied with this decision, and the transition was much easier than expected.

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

#128

Post by ollysb »

abalone wrote: 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.

Perhaps it could actually prefill the standard find dialogue and scroll to the first match, then you could easily see if there was more matches and jump to them.

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

#129

Post by kalmi10 »

xg15 wrote: post #117
SquareWheel wrote: post #100

Earlier quoted context omitted.

SPDY was donated to the IETF for adoption into the HTTP/2 standard. Other browser vendors only implemented it at that time. WebP is a file format and doesn't fall into the normal standardization process. Browsers implement support for new file formats at their own behest.

Yes. After SPDY had already been implemented and shipped in Chrome.

It's not like interoperability suffered because of that. HTTP fallback was always there.

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

#130

Post by otabdeveloper1 »

dannyr wrote: post #35
_bxg1 wrote: 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.

I agree with you on Google's monopoly but imagine if every browser has to go through proposal process to release any feature? Everything will just stagnate. Browsers copy features from each other. If this is a useful feature, it would make its way to other browsers pretty soon.

> Everything will just stagnate.

And that is bad exactly why?

Post reply on HN