27538 2014-12-08 17:45:15 +0000 [Custom]: Tone of note doesn't reflect severity 2015-07-06 08:03:52 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified All All RESOLVED MOVED P2 normal --- 14968 1 bugs faulkner.steve mike public-webapps public-webapps-bugzilla oldest_to_newest 116018 0 bugs 2014-12-08 17:45:15 +0000 "The addition of in line event handlers are for demonstration purposes only. The event handlers could be added by the lifecycle callbacks imperatively, or maybe even not used at all." As a lot of developers forget correct event handlers; I feel as if this note doesn't reflect the severity of the need for these event handlers. I suggest something like: "Developers **should** make sure event handlers are added for both keyboard and mouse users. The inline event handlers shown in this example are for demonstration purposes." 116280 1 faulkner.steve 2014-12-14 20:36:01 +0000 (In reply to Michiel Bijl from comment #0) > "The addition of in line event handlers are for demonstration purposes only. > The event handlers could be added by the lifecycle callbacks imperatively, > or maybe even not used at all." > > As a lot of developers forget correct event handlers; I feel as if this note > doesn't reflect the severity of the need for these event handlers. > > I suggest something like: > > "Developers **should** make sure event handlers are added for both keyboard > and mouse users. The inline event handlers shown in this example are for > demonstration purposes." I have edited the note: "The addition of in line event handlers are for demonstration purposes only. The event handlers could be added by the lifecycle callbacks imperatively, or maybe even not used at all. This example demonstrates one method for developers to ensure that a custom control is operable for keyboard users and meets the WCAG 2.0 criteria "All functionality of the content is operable through a keyboard interface"." 121631 2 hayato 2015-07-06 08:03:52 +0000 Moved to https://github.com/w3c/webcomponents/issues/171