-
Notifications
You must be signed in to change notification settings - Fork 312
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
Move service worker spec into w3c #881
Comments
F2F: Do this sooner rather than later |
F2F: We need to decide if we want the repo to redirect, or the pages. We should ask github if they can help us do both. |
F2F: we don't care too much where the project lives, we care way more about broken links |
Re "doing both", the proximate issue we're facing is that we don't know of any way (today) to redirect both project links and GH Pages URLs to the new location at the same time. It seems possible to do one or the other, but not both. See: https://github.com/blog/1508-repository-redirects-are-here |
IIRC you need to create a 'slightlyoff.github.io' repo in which you can create a ServiceWorker dir, then the tree to the document you want to redirect, finally a minimal document with some js to redirect fragments. |
Transferring the repo to <script>
var element = document.createElement('meta');
element.setAttribute('http-equiv', 'refresh');
element.setAttribute('content', '0; url=https://w3c.github.io/ServiceWorker/spec/service_worker/' + location.hash);
document.getElementsByTagName('head')[0].appendChild(element);
</script> |
The problem is that by recreating the original repo you lose redirects for things like issues. But I believe that what @ylafon suggested should work: put that redirect document in a "slightlyoff.github.io" repo as ServiceWorker/spec/service_worker/index.html. |
Btw, ping me when you plan to do this, as specific right are required for the move. |
Pre F2F notes: Alex says this can be done on Saturday. |
Is this still on track to be moved? |
@slightlyoff what's the status on this? |
Done. |
No description provided.
The text was updated successfully, but these errors were encountered: