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

AxAPI completion #97

Closed
LJWatson opened this issue Jun 17, 2017 · 6 comments · Fixed by #245
Closed

AxAPI completion #97

LJWatson opened this issue Jun 17, 2017 · 6 comments · Fixed by #245
Assignees
Milestone

Comments

@LJWatson
Copy link
Contributor

In both the role, and the state and propertey tables, there are a number of ? placeholders in the AxAPI columns. These need to be updated to include actual data.

@LJWatson LJWatson added this to the WD for wide review milestone Jun 17, 2017
@jasonkiss jasonkiss added the AAM label Jan 9, 2018
@jasonkiss
Copy link
Contributor

jasonkiss commented Jan 22, 2018

Hi @cookiecrook. We're trying to get the HTML-AAM mostly completed for CR, and there are a number of gaps in the AX column that we need help with. Any chance you or someone you can suggest can take a quick stab at it?

The elements table is in good shape and, with the exception of mappings for meter which are pending the outcome of issue #2, there's just mappings for ruby related elements, as well as the u element. I imagine the latter should be "Not mapped" (as probably should the b, i, strong, and em elements, which are currently mapped to AXGroup)?

The AX column for the State and Property mappings has a greater number of gaps:

  • - contenteditable
  • - coords
  • - datetime
  • - dir
  • - draggable
  • - dropzone
  • - height
  • - high
  • - hreflang
  • - label
  • - list
  • - low
  • - maxlength
  • - multiple (on input)
  • - pattern
  • - reversed
  • - rows
  • - scope
  • - size
  • - span
  • - spellcheck
  • - src
  • - start
  • - step
  • - tabindex
  • - type
  • - usemap

@cookiecrook
Copy link
Collaborator

I'm not sure I understand the value of developing this table. It feels like an academic exercise that grossly oversimplifies implementation details (e.g. you can't fit the implementation description of contenteditable neatly into a single table cell). I'm also not sure who the audience for this is, or the value they're expected to gain from it.

@stevefaulkner
Copy link
Contributor

stevefaulkner commented Feb 23, 2018

@cookiecrook I for one find having some accurate (if incomplete) information available in my job, especially in cases where implementation divergence is evident, but if you don't find it worthwhile to provide the info I will take a stab at it providing what I can for the missing entries.

@LJWatson
Copy link
Contributor Author

LJWatson commented May 3, 2018

@cookiecrook can you explain a bit more? Is it that you think the information can be better presented in a different format, or that the mapping information is itself not worth documenting, or something else?

@stevefaulkner
Copy link
Contributor

@LJWatson have started adding missing info, am checking off as I go
fafa93e

stevefaulkner added a commit that referenced this issue May 30, 2018
draggable
- dropzone
- height
- high
- hreflang
- label
- list
- low
- maxlength
refer to #97
@scottaohara
Copy link
Member

scottaohara commented Oct 5, 2018

have not checked off items in the previous comment, but I have posted my branch which has updated the tables quite a bit.

remaining attributes to address in my branch are the following:

  • span
  • spellcheck
  • src
  • start
  • step
  • tabindex
  • type
  • usemap

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 a pull request may close this issue.

5 participants