Contact emails
Explainer
None. Feature is already in spec.
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
Design doc/Spec
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement/relList
Summary
The HTMLAnchorElement.relList read-only property reflects the rel attribute. It is a live DOMTokenList containing the set of link types indicating the relationship between the resource represented by the <a> element and the current document.
Motivation
The motivation of implementing HTMLAnchorElement.relList property to improve interoperability and compatibility as per W3C spec and support to web developers who use AnchorElement relList property. Firefox and Safari are already supporting this feature.
Risks
Interoperability and Compatibility
This property is already implemented in Firefox and Safari so there no compatibility issues. Also, since this is a new API so this will not break any existing functionalities.
Edge: No signals
Firefox: Shipped
Safari: Shipped
Web developers: In favor of interoperability.
Ergonomics
This is part of W3C spec.
Activation
This is part of W3C spec so can be used by web developers directly.
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
wpt/html/dom/ and wpt/html/semantics/text-level-semantics/the-a-element/ are the impacted test suites.
https://wpt.fyi/html/dom/interfaces.html
Link to entry on the feature dashboard
https://www.chromestatus.com/features/5631885325631488
Requesting approval to ship?
Yes
Contact emails
Explainer
None. Feature is already in spec.
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
Design doc/Spec
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement/relList
Summary
The HTMLAnchorElement.relList read-only property reflects the rel attribute. It is a live DOMTokenList containing the set of link types indicating the relationship between the resource represented by the <a> element and the current document.
Motivation
The motivation of implementing HTMLAnchorElement.relList property to improve interoperability and compatibility as per W3C spec and support to web developers who use AnchorElement relList property. Firefox and Safari are already supporting this feature.
Risks
Interoperability and Compatibility
This property is already implemented in Firefox and Safari so there no compatibility issues. Also, since this is a new API so this will not break any existing functionalities.
Edge: No signals
Firefox: Shipped
Safari: Shipped
Web developers: In favor of interoperability.
Ergonomics
This is part of W3C spec.
Activation
This is part of W3C spec so can be used by web developers directly.
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
wpt/html/dom/ and wpt/html/semantics/text-level-semantics/the-a-element/ are the impacted test suites.
Link to entry on the feature dashboard
https://www.chromestatus.com/features/5631885325631488
Requesting approval to ship?
Yes
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f845a61a-af72-4c0e-8ea7-fef5cf521c4d%40chromium.org.
Edge 17 implements relList.
Thanks!
Todd
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEhCOf99cavRq5M_oYWO6ZETaHxrXLU6x7F5Cd1V8pJMxg%40mail.gmail.com.
On Thu, Jan 4, 2018 at 3:32 PM <bhagir...@samsung.com> wrote:Contact emails
Explainer
None. Feature is already in spec.
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
Design doc/Spec
https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-a-element
https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement/relList
Summary
The HTMLAnchorElement.relList read-only property reflects the rel attribute. It is a live DOMTokenList containing the set of link types indicating the relationship between the resource represented by the <a> element and the current document.
Motivation
The motivation of implementing HTMLAnchorElement.relList property to improve interoperability and compatibility as per W3C spec and support to web developers who use AnchorElement relList property. Firefox and Safari are already supporting this feature.
Risks
Interoperability and Compatibility
This property is already implemented in Firefox and Safari so there no compatibility issues. Also, since this is a new API so this will not break any existing functionalities.
Edge: No signals
Firefox: Shipped
Safari: Shipped
Web developers: In favor of interoperability.
Could you add links here?
Ergonomics
This is part of W3C spec.
Activation
This is part of W3C spec so can be used by web developers directly.
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
Is this feature fully tested by web-platform-tests?
wpt/html/dom/ and wpt/html/semantics/text-level-semantics/the-a-element/ are the impacted test suites.
Does the feature also have a test suite making sure it exposes the right values? If not, could you add one?Can you also make sure the values exposed in other browsers that ship the feature comply with the spec?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/46ecbbd5-84c7-4459-ae27-900f37c26a2c%40chromium.org.
On 1/5/18 2:09 AM, bhagir...@samsung.com wrote:
>> Can you also make sure the values exposed in other browsers that
>> ship the feature comply with the spec?
>
> As I checked, functional tests are not covered in web-platform-tests.
The problem is that the values exposed should depend on which features
the UA implements. It's not quite trivial to test this in an automated
fashion.
-Boris
P.S. The lack of relList on HTMLAnchorElement in Chrome has actually
been a serious problem for web developers, because it means they can't
feature-detect noopener support. So I am very happy this is finally
getting fixed.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1c8b9061-18a1-4f78-bf34-20b0bf7eca8b%40mit.edu.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEjiWMwVUu399kTjf9PQj15P421QV2dOx-W%2BrEUd0Vxrgw%40mail.gmail.com.