[richfaces-planning-issues] [JBoss JIRA] (RFPL-2079) Component reference - rich:hotKey - small typos
Brian Leathem (JIRA)
jira-events at lists.jboss.org
Tue Jan 8 00:10:08 EST 2013
[ https://issues.jboss.org/browse/RFPL-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Leathem updated RFPL-2079:
--------------------------------
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
> Component reference - rich:hotKey - small typos
> -----------------------------------------------
>
> Key: RFPL-2079
> URL: https://issues.jboss.org/browse/RFPL-2079
> Project: RichFaces Planning
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.2.0.Final
> Environment: Component reference
> Reporter: Juraj Húska
> Priority: Trivial
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> I have found these small typos for _rich:hotKey in Component Reference_, which should be IMHO fixed:
> CURRENT: attach it with selector attribute to all the elements defined using this selector. This attribute uses syntax for CSS rule selector defined by W3C consortium with some jQuery extensions.
> MAYBE: *attach it to the specific elements by defining selector attribute*. This attribute uses syntax *of the CSS selectors* defined by W3C consortium with some jQuery extensions. *(e.g. which one ?)*
> CURRENT: The key attribute defines the hot key itself which is processed by the component.
> MAYBE: The key attribute defines the hot key *itself, which* is processed by the component.
> CURRENT: The preventDefault attribute specifies whenever hot key binding should prevent default browser-specific actions to be taken (e.g. Ctrl+A hot key selecting all available text, Ctrl+B opening bookmarks bar, etc.).
> MAYBE: The preventDefault attribute specifies *whether the* hot key binding should prevent default browser-specific actions to be taken (e.g. Ctrl+A hot key selecting all available text, Ctrl+B opening bookmarks bar, etc.).
> CURRENT: keydown (default event) is fired when hot key sequence is initiated (keys are down)
> MAYBE: keydown (default event) is fired when *the* hot key sequence is initiated (*the* keys are down)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-planning-issues
mailing list