Again, the use cases I am aware of are more like "link to a thing that doesn't have an anchor provided", not "highlight all the instances of a thing". If there are use cases motivating this, I'd really like to understand what they are.
-
-
Replying to @really_bz @david_bokan and
Or put another way, _why_ are we building find-in-page-via-URL if the problems we want to solve "just" need "indicate a spot on the page via URL"?
1 reply 1 retweet 4 likes -
Replying to @really_bz @bz_moz and
Ah, I think the misunderstanding is "match". In :~:text=foo&text=bar, we call both "foo" and "bar" the "match term". Both "foo" and "bar" be indicated but only the first occurrence of each (it differs from FIP in this way). Is there a section I could clear up?
2 replies 0 retweets 1 like -
Replying to @david_bokan @bz_moz and
Would you highlight both but only scroll to the first in this case?
1 reply 0 retweets 0 likes -
Replying to @othermaciej @bz_moz and
Correct, the first "match term" found on the page is the one that gets scrolled into view. Multiple terms are needed for cases like table cells, list items, discontiguous paragraphs, etc. Conceptually you want to highlight one thing but DOM shape might make that tricky.
1 reply 0 retweets 0 likes -
Replying to @david_bokan @othermaciej and
Why is this needed for table cells? Is there an explanation somewhere? Same thing for list items. Same thing for discontinuous paragraphs...
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz and
In the case of tables, you might want to highlight a column which won't match the DOM order of cells. Discontinuous text can be separated by an ad, you don't want to select the ad text in that case. We're prepping a doc to better document the cases we want to support.
1 reply 0 retweets 0 likes -
Replying to @david_bokan @othermaciej and
Users can't select a column (except in Firefox), last I checked, so can't generate a URL to select it to start with. Yes, a doc documenting the use cases would be very helpful here. I think it would avoid a lot of talking past each other. The use cases I want to support are:
2 replies 0 retweets 0 likes -
Replying to @really_bz @david_bokan and
1) Users being able to bookmark and share with others sub-page positions that the author did not create an anchor to. 2) User comments pointing to the specific part of an article they are responding to. Something like https://indieweb.org/marginalia (more coming)
@T1 reply 0 retweets 1 like -
Replying to @really_bz @david_bokan and
3) Like #2 but for other articles referencing a given one, hosted on other sites. Those are the main ones I can think of right now, but
@t may have more.1 reply 0 retweets 0 likes
In particular, from my point of view, this is not about a replacement for providing proper anchors in pages, but about enabling equivalent user-facing functionality even when pages fail to provide proper anchors. It's not 100% clear to me whether we even agree on that framing.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.