Skip to content
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

SVG-AAM: Update Editor's Draft status & link #103

Merged
merged 1 commit into from
Nov 4, 2015

Conversation

AmeliaBR
Copy link
Contributor

@AmeliaBR AmeliaBR commented Nov 4, 2015

Referencing the RawGit URL as the Editor's Draft, since the GitHub pages version was not being updated. Also make sure it is marked as an Editor's Draft, not a working draft.

@halindrome
Copy link
Contributor

Yeah - the gh-pages drafts are not automatically updated. Michael was
going it manually from time to time if I remember correctly.

On Wed, Nov 4, 2015 at 10:38 AM, Amelia Bellamy-Royds <
notifications@github.com> wrote:

Referencing the RawGit URL as the Editor's Draft, since the GitHub pages
version was not being updated. Also make sure it is marked as an Editor's

Draft, not a working draft.

You can view, comment on, or merge this pull request online at:

#103
Commit Summary

  • SVG-AAM: Update Editor's Draft status & link

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#103.

Shane McCarron
halindrome@gmail.com

@klown
Copy link
Contributor

klown commented Nov 4, 2015

FWIW, I've been manually updating gh-pages with respect to the Core-AAM and Accname-AAM. But, it's a manual operation: generate a snapshot, and push that snapshot to gh-pages branch.

My impression is that the less dynamic snapshots on gh-pages are easier for screen reader users since there are far fewer changes to the DOM while the page is loading.

richschwer added a commit that referenced this pull request Nov 4, 2015
SVG-AAM: Update Editor's Draft status & link
@richschwer richschwer merged commit f3d55b9 into w3c:master Nov 4, 2015
@michael-n-cooper
Copy link
Member

We have been told there are problems referencing the rawgit URI as the
editors' draft. I believe it's a URI that is not intended to receive a
lot of traffic and should not be widely referenced. The solution is to
update the gh-pages version when you feel is needed. I was supposed to
do so on a weekly basis but that turns out to be a big task for all our
docs. I want to automate it but have run into a wall with the system and
don't know how to solve it; someday I still hope to.

So please revert the editors's draft URI to the github.io URI, and post
content to gh-pages as needed, or ping me to.

Michael

On 04/11/2015 11:38 AM, Amelia Bellamy-Royds wrote:

Referencing the RawGit URL as the Editor's Draft, since the GitHub
pages version was not being updated. Also make sure it is marked as an
Editor's Draft, not a working draft.


    You can view, comment on, or merge this pull request online at:

#103

    Commit Summary


Reply to this email directly or view it on GitHub
#103.

pkra pushed a commit that referenced this pull request May 20, 2024
closes #103

this role should be allowed on a section element.
this commit also solves for a duplicate “role=presentation” found in the allowed roles cell.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants