-
Notifications
You must be signed in to change notification settings - Fork 711
[multiple] some specs store their images at top level, rather than in a /images folder #7505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Specifically, the |
(I should probably do a check for local |
It looks like the following bikeshed-generated specs have images at toplevel:
And the following use an
(I ignored specs generated using the old preprocessor.) Edit: also the following houdini specs:
|
(I'm happy to make a PR to fix these, unless you're already doing it.) |
Not doing it, feel free to just push to main. ^_^ |
…ill automatically package. Fixes most of #7505.
Done. Now we just have the issue that perhaps css-easing-1 (and maybe other specs) should be republished. |
…ill automatically package. (Also move a few *out* of such directories, in the case of css-layout-api.) Fixes more of w3c/csswg-drafts#7505.
Turned dbaron's comment into a checklist, and republished css-easing-1. css-egg-1 should be scheduled for April 1st, but hopefully we can get the rest updated soon. :) |
Why is this still open, it looks like the commit from @dbaron fixed all affected specs |
I checked (and then marked as complete in the checklist above) all the specs that were not checked. There were no required changes. |
It appears that the images are all broken in the current TR draft of css-easing-1. I think it would be good to either (a) fix the images after the fact or (b) republish.
(I suspect this was the result of a mistake with echidna, given that it was published with echidna.)
The text was updated successfully, but these errors were encountered: