[prev in list] [next in list] [prev in thread] [next in thread]
List: webkit-dev
Subject: Re: [webkit-dev] Feedback on Blink's text fragment directive proposal
From: Frédéric Wang <fwang () igalia ! com>
Date: 2019-12-10 16:59:11
Message-ID: c48a3bbe-f61a-1a29-7dc9-e63632e8d941 () igalia ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 02/12/2019 21:22, David Bokan wrote:
> Hello webkit-dev,
>
> I'd like to solicit feedback as well as an official position from
> Webkit on our proposal for the text fragment
> directive: https://github.com/WICG/ScrollToTextFragment.
>
> In summary: this is a feature that allows authors and users to craft
> URLs to pages and specify a snippet of text on the page as a
> subresource (visually highlighting it and scrolling it into view).
> Analogous to element-id based fragment anchors but for text.
>
> You can try this out today in Chrome Beta by
> enabling chrome://flags/#enable-text-fragment-anchor. Here's an
> example link:
>
> https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#:~:text=An%20optional%20fragment,element%20into%20view
>
> Relevant Links:
>
> <https://github.com/WICG/ScrollToTextFragment/blob/master/README.md>
> Explainer
> <https://github.com/WICG/ScrollToTextFragment/blob/master/README.md>
> Spec <https://wicg.github.io/ScrollToTextFragment/>
> TAG Review <https://github.com/w3ctag/design-reviews/issues/392>
> (Currently Suspended) Blink Intent Thread
> <https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/zlLSxQ9BA8Y/NLbg84m0EAAJ>
> Issue on Mozilla standards-positions
> <https://github.com/mozilla/standards-positions/issues/194>
>
> We've been using the GitHub repo for issue tracking but happy to take
> feedback (official or otherwise) in any form.
>
> Thank you!
> David
>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
Hi,
I think some of the webkit-dev members have already replied on the Blink
thread. Just to repeat here, I think the concerns Igalia had regarding
the lack of details to implement the algorithm have been addressed in
the latest versions of the spec. We haven't checked again if the WPT
coverage is good enough now though.
--
Frédéric Wang
[Attachment #5 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 02/12/2019 21:22, David Bokan wrote:<br>
<blockquote type="cite"
cite="mid:CANMmsAsYHfGqh5iHibuqMBusfgmb1WCgZnG1df_z45khf+qDGg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hello webkit-dev,
<div><br>
</div>
<div>I'd like to solicit feedback as well as an official
position from Webkit on our proposal for the text fragment
directive: <a
href="https://github.com/WICG/ScrollToTextFragment"
target="_blank" \
moz-do-not-send="true">https://github.com/WICG/ScrollToTextFragment</a>.</div> \
<div><br> </div>
<div>In summary: this is a feature that allows authors and users
to craft URLs to pages and specify a snippet of text on the
page as a subresource (visually highlighting it and scrolling
it into view). Analogous to element-id based fragment anchors
but for text.</div>
<div><br>
</div>
<div>You can try this out today in Chrome Beta by enabling <a
moz-do-not-send="true">chrome://flags/#enable-text-fragment-anchor.
Here's an example link:</a></div>
<div><br>
</div>
<div><a
href="https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#:~:text=An%20optional%20fragment,element%20into%20view"
moz-do-not-send="true">https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#:~:text=An%20optional%20fragment,element%20into%20view</a><br>
</div>
<div><br>
</div>
<div>Relevant Links:</div>
<div><a
href="https://github.com/WICG/ScrollToTextFragment/blob/master/README.md"
moz-do-not-send="true"><br>
</a></div>
<div><a
href="https://github.com/WICG/ScrollToTextFragment/blob/master/README.md"
moz-do-not-send="true">Explainer</a></div>
<div><a href="https://wicg.github.io/ScrollToTextFragment/"
moz-do-not-send="true">Spec</a></div>
<div><a
href="https://github.com/w3ctag/design-reviews/issues/392"
moz-do-not-send="true">TAG Review</a></div>
<div>(Currently Suspended) <a
href="https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/zlLSxQ9BA8Y/NLbg84m0EAAJ"
moz-do-not-send="true">Blink Intent Thread</a></div>
<div><a
href="https://github.com/mozilla/standards-positions/issues/194"
moz-do-not-send="true">Issue on Mozilla standards-positions</a></div>
<div><br>
</div>
<div>We've been using the GitHub repo for issue tracking but
happy to take feedback (official or otherwise) in any form.</div>
<div><br>
</div>
<div>Thank you!</div>
<div>David</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" \
wrap="">_______________________________________________ webkit-dev mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a> <a \
class="moz-txt-link-freetext" \
href="https://lists.webkit.org/mailman/listinfo/webkit-dev">https://lists.webkit.org/mailman/listinfo/webkit-dev</a>
</pre>
</blockquote>
<div class="moz-cite-prefix">Hi,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I think some of the webkit-dev members
have already replied on the Blink thread. Just to repeat here, I
think the concerns Igalia had regarding the lack of details to
implement the algorithm have been addressed in the latest versions
of the spec. We haven't checked again if the WPT coverage is good
enough now though.</div>
<pre class="moz-signature" cols="72">--
Frédéric Wang
</pre>
</body>
</html>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic