Re: bug component for HTML-AAM?

hi Jason, bugs from the old component that relate to the new can be moved
or cloned i guess.

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>


On 6 August 2014 08:46, jason@accessibleculture.org <
jason@accessibleculture.org> wrote:

>
> On 4/08/2014, at 11:42 pm, Paul Cotton <Paul.Cotton@microsoft.com> wrote:
>
> >> Some of the bugs under that component will still apply to the HTML-AAM,
> while those bugs that were specific to the old HTML-API-MAP document can
> presumably be closed?
> >
> > Why would the unresolved bugs on the old HTML-API-MAP document just be
> closed?  If the material they are pertinent has been removed or has been
> moved to the Core API mapping document then surely the bugs should somehow
> be transferred to the Core API mapping document.
>
> That’s consistent with what I meant: unresolved bugs on the old
> HTML-API-MAP component that apply to the HTML-AAM (or CORE-AAM or SVG-AAM
> or…) can remain in some form and be moved to whatever applicable component,
> while bugs that were specific to that old component, i.e. are no longer
> relevant to any document being worked on, can be closed.
>
> >
> >> What about renaming the current "HTML a11y APIs (editor: Steve
> Faulkner, Cynthia Shelly)" to "HTML Accessibility API Mappings"?
> >
> > I recommend that we create a new component and leave the old component
> as is.
>
> Fine by me. What’s the typical procedure for bug components associated
> with items no longer being worked on?
>
> Jason
>
> >
> > /paulc
> >
> > Paul Cotton, Microsoft Canada
> > 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> > Tel: (425) 705-9596 Fax: (425) 936-7329
> >
> >
> > -----Original Message-----
> > From: jason@accessibleculture.org [mailto:jason@accessibleculture.org]
> > Sent: Sunday, August 03, 2014 6:48 PM
> > To: Michael Cooper
> > Cc: PFWG; HTML Accessibility Task Force
> > Subject: bug component for HTML-AAM?
> >
> > Should there be a bug component under the "HTML WG" product in bugzilla
> for the HTML-AAM?
> >
> > What about renaming the current "HTML a11y APIs (editor: Steve Faulkner,
> Cynthia Shelly)" to "HTML Accessibility API Mappings"?
> >
> > Some of the bugs under that component will still apply to the HTML-AAM,
> while those bugs that were specific to the old HTML-API-MAP document can
> presumably be closed?
> >
> > Jason Kiss
> >
> >
> >
> >
> >
> >
>
>
>