[fxtf-drafts] [filter-effects-1] Animation type, CORS fetch links broken (#329)

svgeesus has just created a new issue for https://github.com/w3c/fxtf-drafts:

== [filter-effects-1] Animation type, CORS fetch links broken ==
As I [mentioned in the transition request](https://github.com/w3c/transitions/issues/110#issuecomment-447482498) there were some broken links, which held up manual republication.

These fell into two groups:

1. Animation changes
2. CORS link

Animation types were linking to css transitions, which used to define them:

```
error Lines: 793, 802, 805, 808, 5571, 5607, 6660 https://www.w3.org/TR/css-transitions-1/
    Status: 200 OK

    Some of the links to this resource point to broken URI fragments (such as index.html#fragment). 
    Broken fragments:

        https://www.w3.org/TR/css-transitions-1/#animtype-shadow-list (line 808)
        https://www.w3.org/TR/css-transitions-1/#animtype-precentage (line 5607)
        https://www.w3.org/TR/css-transitions-1/#animtype-number (lines 802, 805, 5607)
        https://www.w3.org/TR/css-transitions-1/#animtype-color (lines 5571, 6660)
        https://www.w3.org/TR/css-transitions-1/#animtype-length (line 793)
```

These have moved to Web Animations, which defines [classes of animation types](https://drafts.csswg.org/web-animations-1/#animation-type). It seems that these are simplified; instead of 'animates as a color' we just say the computed value is animated. I think.

The CORS-enabled fetch has moved from the HTML5 spec to Fetch. I *think* this is the correct link

[CORS request](https://fetch.spec.whatwg.org/#cors-request)

Raising as an issue for discussion, because the link changes I put in to satisfy the pubrules link checker might not be the optimal ones (and the source .bs needs to be corrected so these broken links don't keep recurring).


Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/329 using your GitHub account

Received on Friday, 14 December 2018 22:22:26 UTC