You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User Reported:
"Documentation today says: 'The focusout event is sent to an element when it, or any element inside of it, loses focus. This is distinct from the blur event in that it supports detecting the loss of focus from parent elements'. This is confusing, because 'or any element inside of it' contradicts the subsequent text 'it supports detecting the loss of focus from parent elements'. To be consistent with the first text, the text should instead be: 'it supports detecting the loss of focus from child elements'.
Please either correct the text, or clarify the text such that:
when referring to parents, state parents of what element.
when referring to children, state children of what element."
Dev Summit Group Notes:
"'From 'parent' here was intended to mean 'bubbled up to the parent' and is pretty confusing. Should get a wording update."
The text was updated successfully, but these errors were encountered:
pobocks
added a commit
to pobocks/api.jquery.com
that referenced
this issue
Oct 16, 2012
Pertaining to entry http://api.jquery.com/focusout/
User Reported:
"Documentation today says:
'The focusout event is sent to an element when it, or any element inside of it, loses focus. This is distinct from the blur event in that it supports detecting the loss of focus from parent elements'. This is confusing, because 'or any element inside of it' contradicts the subsequent text 'it supports detecting the loss of focus from parent elements'. To be consistent with the first text, the text should instead be: 'it supports detecting the loss of focus from child elements'.
Please either correct the text, or clarify the text such that:
Dev Summit Group Notes:
"'From 'parent' here was intended to mean 'bubbled up to the parent' and is pretty confusing. Should get a wording update."
The text was updated successfully, but these errors were encountered: