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

Removed references to 3.2.1 from F52. #175

Closed

Conversation

alastc
Copy link
Contributor

@alastc alastc commented Apr 7, 2016

Small changes to F52 to remove references to the AA level 3.2.1 SC.
Also, the reference to XHTML seems rather out-dated, is that ok to remove?

@jnurthen
Copy link
Member

jnurthen commented Apr 7, 2016

@alastc I don't think you should remove the example. I would have simply changed the word XHTML to JavaScript - as this is what the code looks like to me. Indeed I believe both examples are labelled incorrectly as HTML and XHTML when they should both be labelled as JavaScript. One simply shows using the old fashioned onload attribute whereas the 2nd shows using event listeners.

@alastc
Copy link
Contributor Author

alastc commented Apr 7, 2016

Are two examples needed? Perhaps it would be better to simply use the 'XHTML' one (labelled as JavaScript). The key feature is using the window load trigger, both do that and newer sounds better...

@jnurthen
Copy link
Member

jnurthen commented Apr 7, 2016

I agree with this thought. 2 examples complicates things.

On Thu, Apr 7, 2016 at 3:29 PM, Alastair Campbell notifications@github.com
wrote:

Are two examples needed? Perhaps it would be better to simply use the
'XHTML' one (labelled as JavaScript). The key feature is using the window
load trigger, both do that and newer sounds better...


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#175 (comment)

In the consistent behaviour receive focus (understanding) page.
@awkawk awkawk mentioned this pull request Apr 11, 2016
@awkawk
Copy link
Member

awkawk commented Jun 7, 2016

The group discussed on June 7 and was not able to reach consensus.

@alastc
Copy link
Contributor Author

alastc commented Jun 15, 2016

I take that means it is punted for now, is there anything I need to do to clean up, e.g. close or withdraw the request? (Not sure what the optiosn are, or what is appropriate.)

@awkawk
Copy link
Member

awkawk commented Jun 17, 2016

Closing without consensus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants